Subject: TeXhax Digest V89 #110 From: TeXhax Digest Errors-To: TeXhax-request@cs.washington.edu Maint-Path: TeXhax-request@cs.washington.edu To: TeXhax-Distribution-List:; Reply-To: TeXhax@cs.washington.edu TeXhax Digest Sunday, December 10, 1989 Volume 89 : Issue 110 Moderators: Tiina Modisett and Pierre MacKay %%% The TeXhax digest is brought to you as a service of the TeX Users Group %%% %%% in cooperation with the UnixTeX distribution service at the %%% %%% University of Washington %%% Today's Topics: lno3+ printer questions metafont for idiots Re: \font \newfont = \fontname \font scaled \magstep 1 LaTeX References as superscripts? (no []'s) LaTeX double page landscape mode style Re: TeXhax Digest V89 #104 TeX: a new bug bug or feature in \uppercase{\bf } ? How to integrate new fonts into TeXtures for the Mac? Re: TeXhax Digest V89 #102 (TeXsis) ----------------------------------------------------------------------------- Date: Tue, 28 Nov 89 17:52:01 EST From: "S. Holmes [Consulting Detective]" Subject: lno3+ printer questions Keywords: ln03, printer I have an ln03+ with no documentation that I can find. I also have a program called dvil3p which supposedly will drive the lno3+. For me, it prints a page and then gives a controller error on the printer panel. I would be interested in talking with anyone who has info about the use of this printer, other drivers, or the use of dvil3p, etc. Please email. Thanks, Steve Holmes purdue!sjh Systems Administrator sjh@math.purdue.edu Dept. of Mathematics (317) 494-6055 Purdue University W. Lafayette, Indiana 47907 ------------------------------------------------------------------------------- Date: Mon, 27 Nov 89 16:14:15 EST From: rrb@math.wayne.edu (Robert Bruner) Subject: metafont for idiots Keywords: METAFONT Don't be offended: I'm including myself in that group. Can anyone provide a 2 line summary of what to do to get pixel files in other magnifications from metafont? I have found enough time to get mf84 half way to running, but never seem to have the time to finish the job and create the magnifications we're missing. I suspect the task is trivial, and if it is, and someone could summarize what is to be done, maybe I'll finally create the pixel files we need and make all our users here happy. ---------------------------------------------------------------------------- Date: Tue, 28 NOV 89 11:35:57 BST From: CHAA006%vaxa.rhbnc.ac.uk@NSFnet-Relay.AC.UK Reply-To: Philip Taylor (RHBNC) Subject: Re: \font \newfont = \fontname \font scaled \magstep 1 Keywords: fonts Rama Porat asked >>> 1. How do I say a thing like >>> \font\anyname=\fontname\font scaled \magstep1 [without TeX concatenating the external name of the font and the "scaled" modifier]. The following should work, though there is probably a better way :- \def \scaled { scaled } \font \somefont = \fontname \font \scaled \magstep 1 Philip Taylor Royal Holloway and Bedford New College. -------------------------------------------------------------------------- Date: Mon, 27 Nov 89 23:38 EST From: "YATES, JOHN H." Subject: LaTeX References as superscripts? (no []'s) Keywords: LaTeX, superscripts I would like to modify the results of LaTeX 's Bibliographic \cite{key} (UNSRT) to produce the reference number as a superscript, without the [] surrounding it. The closest solution I have found is to define mycite as below to use in the running text (not, of course, tables, figures, etc.). \def\mycite#1{{\footnotesize{$^{^{\cite{#1}}}$}}} (doubly supered for the best position in appearance). Can someone show me a trivial solution to getting rid of the brackets around this superscript? It appears that it is built in the LaTeX executable and perhaps inaccessible other than by tweaking the LaTeX source? But perhaps it can be tricked or backspaced over or... ? I currently have it in a usable form, but would like perfection if possible. Please respond directly to me, I don't subscribe to this list. P.S. As far as getting rid of the brackets in the References, that was trivial. I just modified ARTICLE.STY (in a new document style name, of course), removing the appropriate [ and ] and replacing the right one with a period (.) . Thanks, John John H. Yates yates@a.chem.upenn.edu ----------------------------------------------------------------------------- Date: Mon, 27 Nov 89 13:10:58 EST From: ramsdell@linus.mitre.org Subject: LaTeX double page landscape mode style Keywords: LaTeX, landscape mode I am looking for LaTeX style files which produce well designed documents on a page of size of 5 1/2 by 8 1/2 inches. Such a page size would allow the printing of two pages on one 8 1/2 by 11 inch page in landscape mode, which could then be cut in half. The issue is not one of hacking TeX; included below is a simple plain TeX output routine that generates double page landscape mode documents. Nor is the issue hacking DVI files; there is a program called `dvidvi' that does that. The issue is the encoding of an artful design---something not within my expertise. John %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % Double page output routine places two text pages on one % 8 1/2 x 11 page printed in landscape mode. % John D. Ramsdell -- November 1989 -- The MITRE Corporation. % Places the right-hand page on the right side of the printed page. % The routines were modified from Knuth's double column output routines. \newdimen\fullhsize % You must set this to the entire width. % \fullhsize=\vsize % Start your document with something % \vsize=\hsize % like this. % \hsize=9.1cm % Width of a text page. \let\lr=R \newbox\recto % The right-hand page--the one to be read first. \output={\if R\lr \global\setbox\recto=\pagebox \global\let\lr=L \else \doubleformat \global\let\lr=R\fi \advancepageno \ifnum\outputpenalty>-20000 \else\dosupereject\fi } \def\doubleformat{\shipout\hbox to\fullhsize{\null \pagebox\hfil\vrule\hfil\box\recto}} \def\pagebox{\vbox{\makeheadline \leftline{\pagebody}\makefootline}} % Complete last page with doubleeject. \def\doubleeject{\supereject \if R\lr \else\null\vfill\eject\fi } --------------------------------------------------------------------------- Date: Mon, 27 Nov 89 10:44:53 EST From: beck@cs.cornell.edu (Micah Beck) Subject: Re: TeXhax Digest V89 #104 Keywords: pictures, graphics In article <34594@cornell.UUCP> Clement Pellerin writes: >Can someone comment on the relative merit of tpic, epic, eepic, pictex, >and fig, or give a pointer to where such a work can be found. >Are there others that I missed (that do not require postscript)? These topics are discussed at some length in the TransFig manual, available as Cornell Technical Report #89-967. A more recent version of the manual is distributed along with the TransFig software package. TransFig is avialable via anonymous FTP from svax.cs.cornell.edu in ~ftp/pub/fig/transfig.tar.Z, or by mail from the archive server at sun.soe.clarkson.edu. Micah Beck Cornell CS Dept. -------------------------------------------------------------------------- Date: 27 Nov 89 2305 PST From: Don Knuth Subject: TeX: a new bug Keywords: TeX, bug I just received a message from Rainer Sch\"opf and Frank Mittelbach in Gutenberg's city (Mainz) that they've done it again, found another subtle bug. This one is especially unique because it will not be detected in the TRIP test; it only occurs in the system-dependent code that figures out the "area" and "extension" part of a file name. As far as I know, the error occurs only when you try to combine \csname somehow with file name specification; for example, \input area:file.ext\csname xyz\endcsname will fail on many systems. (Reason: TeX may have to store the control sequence name xyz, while it's looking for the token following "ext". This moves things in the string pool; but the present TeX doesn't move the area and extension pointers, so they might point to garbage.) This bug will be corrected in version 2.993, but I decided to use TeXhax to let installers get a head start, since this bug affects nearly everybody's system-dependent code! The changes are simple--- so simple I haven't even felt the need to test them yet---but they should be made, and you can get a head start by putting them into your change files before you get a new TEX.WEB file. Here are the changes I'll be making to TEX.WEB (unless there's an error here, which cannot be:) %---- an excerpt from the next version of tex82.bug -------------------- 372. Bugfix 339 didn't go far enough (found by Sch\"opf and Mittelbach). @x module 516 [NOTE: THIS AFFECTS ALMOST ALL CHANGE FILES!] @ And here's the second. @^system dependencies@> @p function more_name(@!c:ASCII_code):boolean; begin if c=" " then more_name:=false else begin if (c=">")or(c=":") then begin area_delimiter:=pool_ptr; ext_delimiter:=0; end else if (c=".")and(ext_delimiter=0) then ext_delimiter:=pool_ptr; str_room(1); append_char(c); {contribute |c| to the current string} @y @ And here's the second. The string pool might change as the file name is being scanned, since a new \.{\\csname} might be entered; therefore we keep |area_delimiter| and |ext_delimiter| relative to the beginning of the current string, instead of assigning an absolute address like |pool_ptr| to them. @^system dependencies@> @p function more_name(@!c:ASCII_code):boolean; begin if c=" " then more_name:=false else begin str_room(1); append_char(c); {contribute |c| to the current string} if (c=">")or(c=":") then begin area_delimiter:=cur_length; ext_delimiter:=0; end else if (c=".")and(ext_delimiter=0) then ext_delimiter:=cur_length; @z @x module 517 [NOTE: THIS DOES TOO, AND SO DOES THE NEXT!] else begin cur_area:=str_ptr; incr(str_ptr); str_start[str_ptr]:=area_delimiter+1; @y else begin cur_area:=str_ptr; str_start[str_ptr+1]:=str_start[str_ptr]+area_delimiter; incr(str_ptr); @z @x ibid else begin cur_name:=str_ptr; incr(str_ptr); str_start[str_ptr]:=ext_delimiter; cur_ext:=make_string; @y else begin cur_name:=str_ptr; str_start[str_ptr+1]:=str_start[str_ptr]+ext_delimiter-area_delimiter-1; incr(str_ptr); cur_ext:=make_string; @z ------------------------------------------------------------------------ Date: 28 NOV 89 13:53:07 From: Z3000PA%AWITUW01.BITNET@UWAVM.ACS.WASHINGTON.EDU Subject: bug or feature in \uppercase{\bf } ? Keywords: bug, \uppercase If I write something like \rm a \uppercase{\bf b } c then I get the following: a is printed in lower case roman b is printed in upper case bold face c is not printed in lower case roman (as I would expect) but in lower case bold face! (This happened within LaTeX, but \uppercase seems to be a Plain TeX command.) Now, why does the closing bracket that ends the argument of \uppercase not end the scope of the \bf command? Is this a bug or a feature? --------------------------- (For me, anyway, it is a behaviour that contradicts what I am used to know about grouping rules, so even if it were a feature hidden in some manual, I would consider it a bad one.) Hubert Partl ---------------------------------------------------------------------------- Date: 27 Nov 89 13:18 GMT-0100 From: Thomas Tensi Subject: How to integrate new fonts into TeXtures for the Mac? Keywords: TeXtures, fonts, Mac Hello, I'd like to know if one can incorporate .tfm and .gf (or .pk) files into the TeXtures system on the Macintosh. Some people here would like to extend the standard font set by some own fonts done on a VAX. Does anyone know how to do that? Thanks a lot Thomas Tensi ---------------------------------------------------------------------------- Date: Tue, 28 Nov 89 11:45:34 -0600 From: myers@emx.utexas.edu (Eric Myers) Subject: Re: TeXhax Digest V89 #102 (TeXsis) Keywords: PHYZZX, TeXsis I note that you recently did a review of PHYZZX. I am one of the authors of another macro package called TeXsis which is similar but (we think, anyway) better. A description follows below. The sources are available in bundles for both VMS and Unix machines. Eric Myers "If God had intended for man to fly He would have given us the brains to build airplanes." Center for Relativity, Department of Physics, University of Texas at Austin myers@emx.utexas.edu | myers@UTAPHY.BITNET | (512)471-5426 TEXSIS(1) NAME TeXsis - TeX format for physics papers SYNOPSIS texsis [ filename ] DESCRIPTION TeXsis is a collection of TeX macros for typesetting physics documents such as papers and preprints, conference proceedings, books, theses, referee reports, letters, and memos. It has predefined layouts for all of these documents and supports a wide variety of type sizes. Texsis macros provide automatic numbering of equations, automatic numbering and formatting of references, double column formats, several special document layouts, and macros for making tables and figures, including tables with horizontal and verticl rules. TeXsis is an extension of "Plain" TeX, so anything you know how to do in plain TeX you can do in TeXsis. TeXsis macro instructions are simply abbreviations for often used combinations of control sequences used to typeset physics documents. For more information about plain TeX see the manual entry for "tex", or The TeXbook, by D.E. Knuth. TeXsis is stored as a pre-loaded format so that it loads quickly (see "preloaded formats" in The TeXbook ). To run TeXsis simply give the command texsis in place of the tex command, i.e. texsis [ myfile ] where myfile.tex is the name of a file containing TeX and/or TeXsis \controlsequences. TeXsis is initally in plain TeX mode, e.g. 10pt type and singlespaced, but the control sequence \texsis selects 12pt type, doublespaced, and enables other useful features. Alternatively, \paper turns on these features and sets things up to typeset a paper, \thesis does the same for typesetting a thesis, etc... \letter is used to produce a letter using the macros listed in the back of The TeXbook, and \memo gives a setup for producing memoranda. As with plain TeX, output from TeXsis is to the "device independent" file myfile.dvi. To print this file use the lpr (1) command with the option "-d". A manual which describes all of the TeXsis macro instructions is available. It is written in TeXsis, so it serves as its own example of how to write a document with TeXsis. Page 1 (printed 11/2/89) FILES /usr/lib/tex/texsis/TXS*.tex TeXsis source code. /usr/lib/tex/macros/texsis.fmt TeXsis pre-loaded format. /usr/lib/tex/texsis/TXS*.doc TeXsis manual source (written in TeXsis). /usr/lib/tex/texsis/TXSsite.tex Local site customization instructions. /usr/lib/tex/texsis/TXSpatch.tex Run time patch file (like a system TeXsis.rc file). TXSmods.tex Run time init file (read from current directory or the search path in TEXINPUTS). SEE ALSO tex(1), lpr(1) Donald E. Knuth, The TeXbook AUTHORS Eric Myers Center for Relativity, Department of Physics Univerity of Texas Austin, TX 78705 USA and Frank E. Paige, Physics Department, Brookhaven National Laboratory, Upton, NY 11973 USA. BUGS Having the manual written in TeXsis can cause problems, because you have to know how to run TeXsis to print a copy of the manual. The standard distribution of the source now includes a file called Install.tex which runs under Plain TeX and prints out the installation instructions. Please report bugs to: myers%buphy@bu-it.bu.edu, or myers@buphyc.bitnet Page 2 (printed 11/2/89) ------------------------------------------------------------------------------- %%% The TeXhax digest is brought to you as a service of the TeX Users Group %%% in cooperation with the UnixTeX distribution service at the %%% University of Washington %%% %%% Concerning subscriptions, address changes, unsubscribing: %%% BITNET: send a one-line mail message to LISTSERV@xxx %%% where xxx is the nearest geographical site in the %%% tree shown below %%% SUBSCRIBE TEX-L % to subscribe %%% or UNSUBSCRIBE TEX-L %%% Here is the BITNET re-distribution tree as shown in a recent %%% REVIEW (The geography is guessed at from the subscription list) %%% %%% CLVM TAMVM1 FINHUTC %%% | | (Finland, UK, Scand, CERN) %%% | | | %%% TeXhax ----> UWAVM ----- MARIST ----- EB0UB011 ----- BNANDP11 %%% | (France,Italy,Spain) (Belgium) %%% | | %%% UBVM HEARN --- DEARN %%% (Netherlands) (Germany) %%% %%% Internet: send a similar one line mail message to %%% TeXhax-request@cs.washington.edu %%% Please be sure you send a valid internet address!! %%% in the form name@domain or name%routing@domain %%% and use the style of the Bitnet one-line message, so that %%% we can find your subscription request easily. %%% %%% JANET users may choose to use %%% texhax-request@uk.ac.nsf %%% %%% All submissions to: TeXhax@cs.washington.edu %%% %%% Back issues available for FTPing as: %%% machine: directory: filename: %%% JUNE.CS.WASHINGTON.EDU TeXhax/TeXhaxyy.nn %%% yy = last two digits of current year %%% nn = issue number %%% %%% For further information about TeX Users Group services and publications %%% contact Karen at KLB@SEED.AMS.COM or write to TUG at %%% TeX Users Group %%% P.O. Box 9506 %%% Providence, R.I. 02940-9506 %%% Telephone (401) 751-7760 %%% %%% Current versions of the software now in general distribution: %%% TeX 2.992 metafont 1.8 %%% plain.tex 2.94 plain.mf 1.7 %%% LaTeX 2.09 ( 5/24/89) cmbase.mf see cm85.bug %%% SliTeX 2.09 gftodvi 3.0 %%% tangle 4.0 gftopk 2.0 %%% weave 4.0 gftype 3.0 %%% dvitype 2.9 pktype 2.2 %%% pltotf 3.0 pktogf 1.0 %%% tftopl 3.0 mft 1.1 %%% BibTeX 0.99c %%% AmSTeX 1.1d %%%\bye %%% End of TeXhax Digest ************************** -------