TeXhax@cs.washington.edu (TeXhax Digest) (02/05/89)
TeXhax Digest Thursday, January 19, 1989 Volume 89 : Issue 6
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:
Official TeX changes--where are they recorded?
Page numbering oddity in LaTeX
Correction to texpictex.tex
Difficulty with \ref in nested enumerate in LaTeX
Fixing \documentstyle[10pt]{article}
Verbatim style with tabbing
Including PostScript (TM) files with \special
Printing with Epson LQ-series printers
The New LaTeX manual
Suggestions for the new LaTeX Manual
Raw TeX: staticisation of fonts
Latest version of letter.sty
--------------------------------------------------------------------------
Date: Wed, 11 Jan 89 12:56:49 EST
From: Jim Walker <N410109%UNIVSCVM.BITNET@Forsythe.Stanford.EDU>
Subject: Official TeX changes--where are they recorded?
Keywords: TeX
When officially approved changes to TeX are published, are they
supposed to be inserted in TEX.WEB or in TEX.CH?
I would appreciate it if someone would reply to me individually, because
BITnet distribution of TeXhax does not seem to be working now.
James W. Walker, Department of Mathematics,
University of South Carolina, Columbia SC 29208
BITnet: N410109@univscvm
----------------------------------------------------------------------------
Date: Wed, 11 Jan 89 11:54:15 -0500 (EST)
From: Douglas Bradley Meade <dm2w+@andrew.cmu.edu>
Subject: Page numbering oddity in LaTeX
Keywords: Page numbering, LaTeX
I have experienced some unusual behavior when I add a table of contents entry
for a bibliography. The page number in the toc listing is one less than the
actual first page of the bibliography. Here is the relevant code:
\documentstyle{report}
.
.
.
\begin{document}
.
.
.
\tableofcontents
\mainbody
\input{chap1.tex}
.
.
.
\bibliographystyle{siam}
\addcontentsline{toc}{chapter}{Bibliography}
\bibliography{thesis}
\end{document}
If I put the \addcontentsline after the \bibliography the same result is
produced.
When I change all of the \input to \include the correct page number is
produced.
This leads me to believe that there are some unusual page breaks in the file.
Has anybody else experienced this phenomenon? If so, what is a *good*
solution.
(By good I mean a solution that will work with both \input and \include. I am
trying to follow the guidelines in the LaTeX book for the usage of \input and
\include in a large document.)
Thanks in advance,
Doug Meade
dm2w@andrew.cmu.edu
------------------------------------------------------------------------------
Date: Wed, 11 Jan 89 17:02:52 CST
From: grunwald%guitar.cs.uiuc.edu@a.cs.uiuc.edu (Dirk Grunwald)
Subject: Correction to texpictex.tex
Keywords: texpictex.tex
The following is a replacement for the routine ``\!texpicline'' in the
macro set I submitted earlier titled ``texpictex.tex''.
Basically, you'd only notice this if you drew pictures where you play
with ``\setcoordinatesystem'', as my office-mate does.
Dirk Grunwald
Univ. of Illinois
grunwald@m.cs.uiuc.edu
Office: 72 DCL (217) 333-1925
\def\!texpicline{%
\advance\!xS by -\!xorigin
\advance\!xE by -\!xorigin
\advance\!yS by -\!yorigin
\advance\!yE by -\!yorigin
\!maptpus{\!xS}{\!countC} \!maptpus{\!yS}{\!countD} \!countD=-\!countD%
\special{pa \the\!countC \space \the\!countD}%
\!maptpus{\!xE}{\!countC} \!maptpus{\!yE}{\!countD} \!countD=-\!countD%
\special{pa \the\!countC \space \the\!countD}\special{fp}%
\ignorespaces}
------------------------------------------------------------------------------
Date: Thu, 12 Jan 89 10:59:03 +1000
From: munnari!goanna.oz.au!isaac@uunet.UU.NET (Isaac Balbin)
Subject: Difficulty with \ref in nested enumerate in LaTeX
Keywords: LaTeX, \ref, enumerate
I feel sure that someone has needed this and solved the problem.
I tried to \ref a \item which was inside an enumerate which was
inside another enumerate. The item number actually was printed as
(iii) inside (outer) item 1.
When I referred to the item, and the \label was just after the \item,
I used the normal \ref procedure but the output was
... by condition 1iii
Close, but not quite what I had in mind. Is there a way to get the
required result
... by condition 1 (iii)
A two way hierarchy of \ref's such that if I put a \ref on the
first \item this would get 1, and if I put a \ref on the inner item
this would get iii (and not 1iii) would appear to be the way to go.
A good idea? is there another solution, or have I made a mistake somewhere.
Isaac Balbin,
Department of Computer Science, ACSNET: isaac@goanna.oz
Royal Melbourne Institute of Technology, JANET: isaac%goanna.oz.au@uk.ac.ukc
GPO BOX 2476 V, ARPA: isaac%goanna.oz.au@uunet.uu.net
Melbourne, 3001, CSNET: isaac%goanna.oz.au@australia
AUSTRALIA UUCP: ...!uunet!goanna.oz.au!isaac
Phone: +61 3 660 2803 BITNET: isaac%goanna.oz.au@relay.cs.net
Fax : +61 3 663 2764 EARN: isaac%goanna.oz.au@uk.ac.rl.earn
-------------------------------------------------------------------------------
Date: Wed, 11 Jan 89 10:59:07 PST
From: KARNEY%PPC.MFENET@NMFECC.ARPA
Subject: Fixing \documentstyle[10pt]{article}
Keywords: TeX
In the past 3 years, I have been asked by several users why
\documentstyle[10pt]{article}
doesn't work. Since I consider this construction to be eminently
reasonable, I had no very good answer.
Here's a way of making this work which doesn't involve altering any of
LaTeX's style files: Create an empty file named 10pt.sty, and place it in
the tex$inputs directory (or wherever LaTeX looks to find the standard .sty
files).
Charles Karney
Plasma Physics Laboratory Phone: +1 609 243 2607
Princeton University MFEnet: Karney@PPC.MFEnet
PO Box 451 ARPAnet: Karney%PPC.MFEnet@NMFECC.ARPA
Princeton, NJ 08543-0451 Bitnet: Karney%PPC.MFEnet@ANLVMS.Bitnet
------------------------------------------------------------------------------
Date: Tue, 10 Jan 89 17:08:44 PST
From: fine%fine.DEC@decwrl.dec.com (Michael Fine)
Subject: Verbatim style with tabbing
Keywords: Tabs
In TeXHaX 88-111, Francois-Michel Lang asks for a modified verbatim
environment that recognizes tab characters as tabs instead of spaces.
Below is a style that does so. No warranty is expressed or implied.
Michael Fine
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% Verbatim With Tabbing and Page Breaks
%
% Written by:
% Michael Fine
% Distributed Systems Architecture.
% September 1987
%
%
% This environment is similar to the LaTeX verbatim environment but it
% interpretes tab characters as usually expected. It has the
% additional feature that a CTL-L in the verbatim environment invokes
% the LaTeX macro \newpage (thereby giving you some control over page
% breaks).
%
% There is also a command \inputverbatim which can be used to specify
% a file to be input and typeset in the verbatim environment.
%
% This does not and should be made to work correctly for verbatim* as
% well. Also, it should probably use a different name.
%
% Usage:
%
% \setlength{\tabwidth} % or
% \settowidth{\tabwidth}{text}
% % default is width of 8 characters of \normalsize\tt
%
% Then:
% \begin{verbatim}
% Verbatim text set in \tt font with ^L for page ejects
% and ^I for tabs
% \end{verbatim}
%
% or:
% \inputverbatim{filename} % input a file of text
%
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% A version message
%
\typeout{Tabbing Verbatim Style <September 29, 1987>}
\newlength{\tabwidth}
\settowidth{\tabwidth}{\normalsize\tt mmmmmmmm}
% default is 8 characters of \tt font in \normalsize
\begingroup
\catcode`\^^I=\active\def^^L{}
\gdef\@newverbatim{\@verbatim
\def\par{\egroup\@@par\noindent
\@tempdima 0pt\hbox\bgroup{}}\obeylines
\let\ignorespaces\relax % for \@gobblecr
\catcode`\^^I\active
\def^^I{\egroup\setbox\@tempboxa\lastbox\@tempdimb \wd\@tempboxa
\box\@tempboxa
\advance\@tempdima by \@tempdimb \computeskip\penalty10000
\hskip\@tempdimb\advance\@tempdima by \@tempdimb
\hbox\bgroup{}}\def^^L{\egroup\setbox\@tempboxa\lastbox
\@tempdimb\wd\@tempboxa
\ifdim\@tempdimb=0pt\else\box\@tempboxa\fi
{\let\par\@@par\newpage}\noindent\hbox\bgroup\@gobblecr}\relax
\def\computeskip{\@tempcnta 0\@tempdimb 0pt\loop
\ifdim \@tempdimb<\@tempdima
\advance\@tempdimb by \tabwidth \advance \@tempcnta1 \repeat
\ifdim\@tempdima=\@tempdimb \advance\@tempcnta1\fi
\@tempdimb\@tempcnta \tabwidth \advance \@tempdimb
by -\@tempdima}}
\gdef\verbatim{\@newverbatim\frenchspacing\@vobeyspaces
\@xverbatim\noindent\hbox\bgroup\@gobblecr}
\gdef\endverbatim{\egroup\setbox\@tempboxa\lastbox
\@tempdimb\wd\@tempboxa
\ifdim\@tempdimb=0pt\else\box\@tempboxa\fi
\let\par\@@par\endtrivlist}
%
% Now we define \inputverbatim
%
% This is similar to \verbatim but does not need \@xverbatim trickery
% to delimit the begining and end of the verbatim text.
\gdef\inputverbatim#1{{\@newverbatim\frenchspacing\@vobeyspaces
\noindent\hbox\bgroup\input{#1}\endverbatim}}
\endgroup
-----------------------------------------------------------------------------
Date: Tue, 10 Jan 89 17:42 EST
From: Henning Schulzrinne <HGSCHULZ@cs.umass.EDU>
Subject: Including PostScript (TM) files with \special
Keywords: PostScript, \special, dvi2ps
I am trying to include PostScript graphics files generated by a variety
of sources (e.g., "S", the AT&T data manipulation language, MacDraw,
AutoCAD, ...) into a TeX document, using \special. We use DVIALW,
version 2.07c as our DVI-to-PS converter and print on an LPS40. Judging
from the postscript file, the graphics file does get included in its
entirety. I also took care of all the BoundingBox and ": 0 0 0 0"
problems (I think). Still, I get absolutely NOTHING (besides the flag
pages) out of the printer, not even a blank sheet.
Is there something else I could try using this DVI filter? Are there
any DVI-to-PS versions out there which are slightly more forgiving?
I would appreciate hearing about any experiences in that area.
Henning Schulzrinne
U. of Massachusetts, Amherst
CSNET: HGSCHULZ@CS.UMASS.EDU
BITNET: HGSCHULZ@UMAECS
------------------------------------------------------------------------
Date: 10 Jan 89 13:27:00 CST
From: "DAVE CARGO" <dscargo@cim-vax.honeywell.com>
Subject: Printing with Epson LQ-series printers
Keywords: printer, dviware, fonts, METAFONT
Are there DVI printer drivers for the Epson LQ series printers? The new
LQ-500 costs about $330-$370 on the street. It's got 24-pin print
capability. That would be wasted using the FX-compatible printing modes.
The 24-pin print moves should be much faster than the 8 pin print modes.
The question then arises: What representations of the fonts are required?
Would I need MF to create appropriate fonts.?
------------------------------------------------------------------------
Date: Thu, 12 Jan 89 21:03:08 EST
From: toms@ncifcrf.gov
Subject: The New LaTeX manual
Keywords: LaTeX manual
The following is a letter I sent to Leslie Lamport. I thought it might
be helpful to have discussion on it in this group.
Dear Leslie:
I understand you are or are considering a second version of LaTeX. Bravo!
There is one thing that remains totally obscure to me from the current
manual and this is the business about robustness, fragility and
moving arguments. I've read the definitions and they seem all circular
and refer to each other. I don't know what causes the problem, how
to recognize it if it comes up. Maybe it has and I never recognized it.
To make sure, I just scanned over all the references in the Index
on fragile command, pages 24,27,34,151 and 119. All the terms are defined
in terms of the other terms! THIS IS FRUSTRATING!!!
A few paragraphs that REALLY say what's going on would be of great help!
Also, it turns out that I write a LOT of letters which have references in
them. So do other scientists. Since the letter environment does not support
this, I have made up my own format. Please make it possible to have
references in letters in the next version!
Finally, controls for the form of a reference in the text would
be quite useful, to avoid this proliferation of styles. (I now know how
to program the format of the references, and I'm happy with that solution.)
A simple switch would be useful: bracked, parenthesis, superscript for
the reference. Also, getting rid of the word REFERENCES is a pain;
this should be a switch. Finally, something within LaTeX must decide
to put spaces between the references, I couldn't locate it (since I
don't know TeX code) and to make my Nucleic Acids Research reference list
work out properly I had to neutralize the blank lines with:
\vspace{-\baselineskip}\vspace{4pt}
in the bbl file. That doesn't seem to be quite right, but it works
pretty well. Sure is an ugly solution. The point is that the
bbl should have COMPLETE control over the format of the references!!
Sincerely yours,
Tom Schnesder
National Cancer Institute
Laboratory of Mathematical Biology
Frederick, Maryland
toms@ncifcrf.gov
--------------------------------------------------------------------------
Date: Wed, 11 JAN 89 11:52:11 GMT
From: RM028A%cranfield.ac.uk@NSS.Cs.Ucl.AC.UK
Subject: Suggestions for the new LaTeX Manual
Keywords: LaTeX manual
In TeXhax V88 #110, Hubert Partl (Z3000PA%AWITUW01.BITNET) writes regarding
Leslie Lamport's request (in TeXhax V88 #104) for suggestions as to format
of a new LaTeX manual:--
>>I would like to give a few comments to your plan of a new LaTeX Manual.
>>First of all, I like the present manual very much, indeed, -- far more
>>than the TeXbook -- and I consider it an ideal guide for AUTHORS.
>>However, I sometimes miss information needed by LAYOUT DESIGNERS.
I wholeheartedly concur with those sentiments!
>>Therefore, I suggest that you split the manual into 2 parts or perhaps
>>2 separate volumes: one for authors, and the second one for layout
>>designers.
>>
>>The AUTHORS' Manual should be just like the present manual (perhaps
>>without the chapter `Designing it Yourself').
That seems reasonable, although there should still be *some* of the
`Designing it Yourself' chapter in the author's section --- after all many
users might only purchase that volume (unless the publisher ``bundles'' the
two together).
>>For the LAYOUT DESIGNERS' Manual, I suggest the following contents:
>>
>> - description of the LaTeX commands and layout parameters for
>> `designing it yourself'
>>
>> - description of the files LATEX.TEX, ARTICLE.DOC, and ART10.DOC,
>> perhaps similar to the description of PLAIN.TEX in appendix B of
>> the TeXbook, or at least printing the comments that appear in those
>> files
I feel that we also need descriptions of LPLAIN.TEX and LFONTS.TEX.
Regarding documentation of macros, and particularly those which are as
complex as the majority of the afore-mentioned files, could I suggest that
the expositionary style of Frank Mittelbach's article (TUGboat V9 #3) should
be adopted by ALL authors, it would be particularly useful for LATEX.TEX's,
etc.
>>
>> - hints on how to define new layouts. This should include:
>> - technical questions (style files, style option files, \ds@foo, etc.)
>> - layout design decisions (e.g. why there is no \parindent after
>> section headings, and how \textwidth, \textheight, \baselineskip etc.
>> are related to each other and to the font size, etc. etc.)
>> - LaTeX internal conventions (\makeatletter, \leftmargini, \@listi,
>> \linewidth, etc.)
>>
>> - some examples, e.g.:
>> - how to change `Chapter' and `Figure' and `Table of Contents' etc.
>> and \today to the corresponding spanish words
>> - how to define a `myfootings' page style
>> - how to adjust the page layout for larger or smaller or taller
>> paper sheets
>> and some more.
If LATEX.TEX (and the rest) were described in Mittelbach's style (we need a
catchy title for his `macro-WEB'), with copious examples in the narrative,
this could be achieved.
>>I hope that my ideas may be useful. If you don't find the time to write
>>the second part, perhaps someone else might step in? (Therefore, I am
>>publishing this letter via TEXHAX, too.)
That seems a good idea too --- however, I'm afraid that I'm NOT
volunteering!!
I am copying this to TeXhax, since I feel that there should be a lively
correspondence regarding this issue. I (like Partl) am a confirmed LaTeX
devotee, and get very annoyed by the `real typesetters don't use LaTeX'
mentality of the PLAINers (perhaps that should be planers; after all they
display a `flat-earther' attitude). TeXhax and TUGboat are always bulging
at the seams with floods of hackery to achieve objects which can be reached
by LaTeX in a few lines, and the latter moreover has the advantage that
authors can be forced to follow good style conventions. My reaction to the
usual challenge of ``but how on earth can you do ... in LaTeX'' is normally
that no sane person should attempt to do something so visually offensive!
The use of PLAIN TeX should be *banned*, apart from its utility to process
the output of WEAVE; there, that should provoke some debate!
Brian HAMILTON KELLY
-----------------------------------------------------------------------------
| Snail Mail: | Telephone: Swindon (0793) 785252 |
| School of Electrical | International: +44-793-785252 |
| Engineering & Science | |
| Royal Military College of Science | e-mail: |
| Shrivenham, SWINDON | Janet: rmcs-tex@uk.ac.cranfield.cdvc |
| SN6 8LA | |
| United Kingdom | |
-----------------------------------------------------------------------------
Date: 10-JAN-1989 16:38:22 GMT
From: Philip Taylor (RHBNC) <P.Taylor%vaxb.rhbnc.ac.uk@NSS.Cs.Ucl.AC.UK>
Subject: Raw TeX: staticisation of fonts
Keywords: TeX, fonts
Exactly {\it when\/} does the staticisation of fonts take place ? The
\TeX book on page 153 explains that in an example such as
$ \textfont0 = \tenrm 9 \textfont0 = \Helvetica 9 $
both "9"s will be set in font \Helvetica, since \textfont0 is \Helvetica at the
end of the formula. However, \Helvetica is a font-selector, not a font name,
and a further level of dereferencing/staticisation is required before the actual
font can be determined.
Let me explain the problem: I have a preamble which defines (among others)
fonts \tenrm and \sevenrm as being "psmtimr" and "psmtimr at 7pt" respectively;
"psmtimr" is a PostScript Times-Roman font. My normal running text, (which is
explicitly preceded by a \rm) is set in "psmtimr" as I expected, but a fraction
(${1 \over 6}$) is set in "cmr7". This is true for both ArborText's $\mu$ \TeX
V2.93 and for Wayne Sullivan's SB(08)TeX, V2.93. The only way around this
problem is to repeat, as part of the preamble, the section of Plain.TeX which
says "\scriptfont0 = \sevenrm", {\it after\/} the font definition which says
"\font \sevenrm = psmtimr at 7pt",
This is distinctly counter-intuitive, and I am almost prepared to
suggest, wrong, particularly as chasing back through the definitions
using \message {\the \scriptfont0 \meaning \sevenrm} shews exactly the
same situation obtaining before and after the assignment to
\scriptfont0.
Here is a simple test program, the resulting log file, and the output from
DVITYPE; the actual glyphs set are from "cmr7" for the left fraction, and from
"psmtimr at 7 pt" for the right.
** Phil.
\def \debug {\message {\the \scriptfont0 \meaning \sevenrm}}
\font \tenrm = psmtimr
\font \sevenrm = psmtimr at 7 pt
\rm
Left part
\debug
${1 \over 6}$
\scriptfont0 = \sevenrm
\debug
${1 \over 6}$
right part
\end
This is TeX, TeXpress Version 2.93 (preloaded format=plain 88.12.21) 10 JAN 1989 16:23
**test
(c:\typeset\linotron\test.tex \sevenrm select font psmtimr at 7.0pt
\sevenrm select font psmtimr at 7.0pt [1]
Output written on c:\typeset\linotron\test.dvi (1 page, 1024 bytes).
This is DVItype, PC-DOS Version 2.8
Options selected:
Starting page = *
Maximum number of pages = 1000000
Output level = 3 (the works)
Resolution = 300.00 pixels per inch
numerator/denominator=25400000/473628672
magnification=1000; 0.00006334 pixels per DVI unit
' TeX output 1989.01.10:1623'
Postamble starts at byte 302.
maxv=43725786, maxh=30785863, maxstackdepth=6, totalpages=1
Font 51: psmtimr---loaded at size 458752 DVI units
(this font is magnified 70%)
Font 50: psmtimr---loaded at size 655360 DVI units
Font 3: cmr7---loaded at size 458752 DVI units
42: beginning of page 1
87: push
level 0:(h=0,v=0,w=0,x=0,y=0,z=0,hh=0,vv=0)
88: down3 -917504 v:=0-917504=-917504, vv:=-58
92: pop
level 0:(h=0,v=0,w=0,x=0,y=0,z=0,hh=0,vv=0)
93: down4 42152922 v:=0+42152922=42152922, vv:=2670
98: push
level 0:(h=0,v=42152922,w=0,x=0,y=0,z=0,hh=0,vv=2670)
99: down4 -41497562 v:=42152922-41497562=655360, vv:=42
104: push
level 1:(h=0,v=655360,w=0,x=0,y=0,z=0,hh=0,vv=42)
105: right3 1310720 h:=0+1310720=1310720, hh:=83
[ ]
109: fntdef1 50: psmtimr
132: fntnum50 current font is psmtimr
133: setchar76 h:=1310720+400425=1711145, hh:=108
134: setchar101 h:=1711145+290980=2002125, hh:=126
135: setchar102 h:=2002125+218235=2220360, hh:=140
136: setchar116 h:=2220360+182190=2402550, hh:=152
137: w3 218431 h:=2402550+218431=2620981, hh:=166
141: setchar112 h:=2620981+327680=2948661, hh:=187
142: setchar97 h:=2948661+290980=3239641, hh:=205
143: setchar114 h:=3239641+218235=3457876, hh:=219
144: setchar116 h:=3457876+182190=3640066, hh:=231
[Left part]
145: push
level 2:(h=3640066,v=655360,w=218431,x=0,y=0,z=0,hh=231,vv=42)
146: push
level 3:(h=3640066,v=655360,w=218431,x=0,y=0,z=0,hh=231,vv=42)
147: push
level 4:(h=3640066,v=655360,w=218431,x=0,y=0,z=0,hh=231,vv=42)
148: down3 -258036 v:=655360-258036=397324, vv:=26
152: push
level 5:(h=3640066,v=397324,w=218431,x=0,y=0,z=0,hh=231,vv=26)
153: right3 297074 h:=3640066+297074=3937140, hh:=249
[ ]
157: fntdef1 3: cmr7
177: fntnum3 current font is cmr7
178: setchar49 h:=3937140+261235=4198375, hh:=266
[1]
179: pop
level 5:(h=3640066,v=397324,w=218431,x=0,y=0,z=0,hh=231,vv=26)
180: right3 297074 h:=3640066+297074=3937140, hh:=249
[ ]
184: down3 107302 v:=397324+107302=504626, vv:=33
188: putrule height 26213, width 261235 (2x17 pixels)
197: down3 376728 v:=504626+376728=881354, vv:=57
201: push
level 5:(h=3937140,v=881354,w=218431,x=0,y=0,z=0,hh=249,vv=57)
202: setchar54 h:=3937140+261235=4198375, hh:=266
[6]
203: pop
level 5:(h=3937140,v=881354,w=218431,x=0,y=0,z=0,hh=249,vv=57)
204: pop
level 4:(h=3640066,v=655360,w=218431,x=0,y=0,z=0,hh=231,vv=42)
205: pop
level 3:(h=3640066,v=655360,w=218431,x=0,y=0,z=0,hh=231,vv=42)
206: pop
level 2:(h=3640066,v=655360,w=218431,x=0,y=0,z=0,hh=231,vv=42)
207: push
level 2:(h=3640066,v=655360,w=218431,x=0,y=0,z=0,hh=231,vv=42)
208: push
level 3:(h=3640066,v=655360,w=218431,x=0,y=0,z=0,hh=231,vv=42)
209: push
level 4:(h=3640066,v=655360,w=218431,x=0,y=0,z=0,hh=231,vv=42)
210: down3 -258036 v:=655360-258036=397324, vv:=26
214: push
level 5:(h=3640066,v=397324,w=218431,x=0,y=0,z=0,hh=231,vv=26)
215: right3 934026 h:=3640066+934026=4574092, hh:=290
[ ]
219: fntdef1 51: psmtimr
242: fntnum51 current font is psmtimr
243: setchar49 h:=4574092+229376=4803468, hh:=305
[1]
244: pop
level 5:(h=3640066,v=397324,w=218431,x=0,y=0,z=0,hh=231,vv=26)
245: right3 934026 h:=3640066+934026=4574092, hh:=290
[ ]
249: down3 107302 v:=397324+107302=504626, vv:=33
253: putrule height 26213, width 229376 (2x15 pixels)
262: down3 376728 v:=504626+376728=881354, vv:=57
266: push
level 5:(h=4574092,v=881354,w=218431,x=0,y=0,z=0,hh=290,vv=57)
267: setchar54 h:=4574092+229376=4803468, hh:=305
[6]
268: pop
level 5:(h=4574092,v=881354,w=218431,x=0,y=0,z=0,hh=290,vv=57)
269: pop
level 4:(h=3640066,v=655360,w=218431,x=0,y=0,z=0,hh=231,vv=42)
270: pop
level 3:(h=3640066,v=655360,w=218431,x=0,y=0,z=0,hh=231,vv=42)
271: pop
level 2:(h=3640066,v=655360,w=218431,x=0,y=0,z=0,hh=231,vv=42)
272: right3 1460476 h:=3640066+1460476=5100542, hh:=323
[ ]
276: fntnum50 current font is psmtimr
277: setchar114 h:=5100542+218235=5318777, hh:=337
278: setchar105 h:=5318777+182190=5500967, hh:=349
279: setchar103 h:=5500967+327680=5828647, hh:=370
280: setchar104 h:=5828647+327680=6156327, hh:=391
281: setchar116 h:=6156327+182190=6338517, hh:=403
282: w0 218431 h:=6338517+218431=6556948, hh:=415
283: setchar112 h:=6556948+327680=6884628, hh:=436
284: setchar97 h:=6884628+290980=7175608, hh:=454
285: setchar114 h:=7175608+218235=7393843, hh:=468
286: setchar116 h:=7393843+182190=7576033, hh:=480
[right part]
287: pop
level 1:(h=0,v=655360,w=0,x=0,y=0,z=0,hh=0,vv=42)
288: pop
level 0:(h=0,v=42152922,w=0,x=0,y=0,z=0,hh=0,vv=2670)
289: down3 1572864 v:=42152922+1572864=43725786, vv:=2770
293: push
level 0:(h=0,v=43725786,w=0,x=0,y=0,z=0,hh=0,vv=2770)
294: right4 15229440 h:=0+15229440=15229440, hh:=965
299: setchar49 h:=15229440+327680=15557120, hh:=986
[ 1]
300: pop
level 0:(h=0,v=43725786,w=0,x=0,y=0,z=0,hh=0,vv=2770)
301: eop
----------------------------------------------------------------------------
Date: Mon, 9 Jan 89 17:14:59 EST
From: mroth@afit-ab.arpa (Mark A. Roth)
Subject: Latest version of letter.sty
Keywords: LaTeX
I have a version of letter.sty dated 21 July 1985. This is
incompatible with the 1987 and beyond versions of latex.tex. The
specific problem is the new definition of \parbox which now sets
\parskip to 0. This in turn affects \closing. I have fixed it myself
but would appreciate it if someone could send me the official changed
version of letter.sty.
Mark Roth
mroth@afit.af.mil
---------------------------------------------------------------------------
%%% 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@UWAVM.ACS.WASHINGTON.EDU
%%% SUBSCRIBE TEXHAX <your name> % to subscribe
%%% or UNSUBSCRIBE TEXHAX <your name>
%%%
%%% All others: 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.
%%%
%%% 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.93 metafont 1.5
%%% plain.tex 2.92 plain.mf 1.0
%%% LaTeX 2.09 ( 4/26/88) cmbase.mf see cm85.bug
%%% SliTeX 2.09 gftodvi 1.7
%%% tangle 2.8 gftopk 1.4
%%% weave 2.9 gftype 2.2
%%% dvitype 2.9 pktype 2.2
%%% pltotf 2.3 pktogf 1.0
%%% tftopl 2.5 mft 0.3
%%% BibTeX 0.99c dvipage 3.0
%%%\bye
%%%
End of TeXhax Digest
**************************
-------