TeXhax@cs.washington.edu (TeXhax Digest) (05/15/89)
TeXhax Digest Thursday, April 27, 1989 Volume 89 : Issue 40
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:
Wanted: Material for (La)TeX courses
Re: LaTeX: Problem with \figure/\ref
Re: Graphics in TeX (TeXhax Digest V89 #23)
TeX and Graphics
Re: parshape with last line centred
Re: Latex Form Letter
Re: LaTeX fonts at 118dpi
Chinese and Korean coding schemes
What do you mean "french" spacing?
Re: Dec's macro package...
Re: TeXhax Digest V89 #23 (IBM 3812)
---------------------------------------------------------------------
Date: Sat, 22 Apr 89 10:09 GMT
From: Nico Poppelier <POPPELIER%HUTRUU51.BITNET@UWAVM.ACS.WASHINGTON.EDU>
Subject: Wanted: Material for (La)TeX courses
Keywords: LaTeX, TeX
In the end of June this year the Dutch TeX users group will organize
its first (mini) conference. Part of the program will consists of
courses in LaTeX (introduction), LaTeX document styles, and METAFONT.
Since there have been many similar courses at both international and
European TeX meetings it would be a case of re-inventing the wheel if
people here would develop their teaching material from scratch.
Would it be possible to receive material from people involved in
similar courses, let's say in the US, Canada, the UK, Germany
- 1. in English
- 2. TeX `coded'
that we can use for our conference this summer?
Nico Poppelier
University of Utrecht
The Netherlands
-------------------------------------------------------------------------------
Date: Sat, 22 Apr 89 15:36:32 +0200
From: mcvax!iesd!fischer@uunet.UU.NET (Lars P. Fischer)
Subject: Re: LaTeX: Problem with \figure/\ref
Keywords: LaTeX, \figure/\ref
>\begin{figure}[h]
>\label{fig1}
>\vspace{1in} %picture
>\caption{First}
>\end{figure}
The figure number of a figure environment is generated by the
*caption* command. This means that a label command should always
*follow* a caption command, eg.
\begin{figure}[h]
\vspace{1in} %picture
\caption{First}
\label{fig1}
\end{figure}
Hope this helps (no, it's not very obvious, or logical....).
/Lars
Copyright 1989 Lars Fischer; you can redistribute only if your recipients can.
Lars Fischer, fischer@iesd.dk, {...}!mcvax!iesd!fischer
"I could have done it in a much more complicated
way", said the Red Queen, immensely proud.
-- Lewis Carrol, Alice in Wonderland
----------------------------------------------------------------------------
Date: Fri, 21 Apr 89 21:46:36 -0700
From: lgy@blake.acs.washington.edu (Laurence Yaffe)
Subject: Re: Graphics in TeX (TeXhax Digest V89 #23)
Keywords: TeX, graphics
While Don Hosek's comment:
>Ideally, complicated graphics should be handled outside of TeX and
>included as whole images.
is clearly correct for truly compicated graphics, I think it would be highly
desirable if standard dvi drivers would recognize \specials for accurate
straight line drawing (with arbitrary endpoints).
Dvi drivers with this capability allow one, for example, to prepare
high quality graphs using TeX to produce everything (axes, tick marks,
axis labels, ...) except drawing the lines connecting actual data points.
This is best done by using a \special to pass the dvi driver a list
of coordinate pairs.
Such an approach can have the advantages of (1) drawing simple graphics
with maximal resolution, (2) efficiently passing large numbers of coordinates
to the driver (which is neccesary for smooth curves), and (3) storing both
the textual and graphical information in a single file. The last point
may not seem important until you've prepared a paper with a very large
number of figures. If the data for each figure is effeciently stored
within the .dvi file itself (instead of in hundreds of separate files)
"sending" the paper to a remote printer, or a remote coauthor is enormously
simplified.
Special graphics fonts, which can only draw lines at certain angles,
are totally inadequate. Similarly, schemes which force TeX to process
each and every pixel in a straignt line (and hence consume memory within
TeX) are inadequate for accurate, smooth curves, where you may need to
pass many thousand coordinate pairs to the driver.
Laurence Yaffe
Laurence G. Yaffe Internet: lgy@newton.phys.washington.edu
Department of Physics, FM-15 Bitnet: yaffe@phast.bitnet
University of Washington
Seattle WA 98195
----------------------------------------------------------------------------
Date: Fri, 21 Apr 89 19:22:45 edt
From: andrews%cpwscb@clipr.PSC.EDU (Phil)
Subject: TeX and Graphics
Keywords: Tex, graphics
There have been numerous proposals lately about graphics in TeX. I
think most of them miss the point in that the greatest need is for the
capability of importing, in a device independent manner, the output
from various graphics packages. If you are only interested in allowing
TeX devotees to create their own pretty pictures then almost any system
will do, but if you want to play with the big boys then you have to use
their ball.
The only format with any widespread acceptance is the CGM format, an
ISO and ANSI standard that is steamrolling over any opposition, backed
by the CALS and TOP/MAP organisations. At the Pittsburgh Supercomputing
Center we have standardised our two-dimensional graphics on CGM files,
which are being produced by all of our graphics packages including
DISSPLA, NCAR, DI-3000 and Movie-BYU. I wrote our official CGM
translator, GPLOT, which handles the files from all of these packages
in either binary or clear text format. While I was writing this system
I integrated in an old DVI processor I wrote called GTEX so that they
used common device drivers. The upshot of this is that any graphics
page produced at PSC can be included in any TeX output to almost any
output device we support via a \special command. To keep things simple
for the users an identical interface is used at command level or inside
the \special command. E.g., (under UNIX) the command might be
gplot -dps -p3 example.cgm example.ps
to make PostScript output from page 3 of the example.cgm file.
\special{gplot -p3 -x3.5 -y3.5 example.cgm}
inside of a TeX file would tell GTEX to grab page 3 of the example.cgm
file, scale it to fit a 3.5 by 3.5 inch square and set the origin at
the point from which the \special was called.
GPLOT and GTEX are in C and run under VMS, UNIX, ULTRIX and UNICOS, we
are presently supporting X11, PostScript, QUIC (QMS), SCGI (SUN), GKS,
UIS (DEC), Peritek frame buffer, CGM Binary and CGM Clear Text output,
although some of them (X) are moving targets and are still being
debugged.
I'm not convinced that my interface is the best possible, but I do
believe that the only practical method of interaction with graphics
packages is via the CGM standard. For simple stuff a Clear Text cgm
file can be written by hand.
There is one need not covered by this; the sometimes necessity of
interfacing graphical specifics to the position of TeX elements, e.g.,
a line joining two TeX boxes. This could be handled by almost any system;
for convenience I have left a \special interface to allow the user to
call any CGM element (e.g., polylines, polygons, etc.), but if the TeX
community could come up with device-independent standard I would support
it. It is often easier to use something already in existence (like CGM)
so that you don't waste time over what should or shouldn't suffice and
reduce TeX and Graphics to Mark Twain's weather.
Phil Andrews, andrews@b.psc.edu, andrews%cpwscb@clipr.psc.edu
------------------------------------------------------------------------------
Date: Sun, 23 Apr 89 14:50:20 EDT
From: Steve_Tinney@um.cc.umich.edu
Subject: Re: parshape with last line centred
Keywords: TeX, paragraph
% Nico (Poppelier%Hutruu51.Bitnet@Cunyvm.Cuny.Edu) asks how to get
% the `funny paragraph shape':
%
% aaaaaaaaaabbbbbbbbbbcccccccccc
% ddddddddddeeeeeeeeeeffffffffff
% ______ggggggggghhhhhhhh.______
%
% where underscores stand for whitespace. The following, which I
% simply adapted from the macros on p392 of the TeXbook, appears to do
% the trick (real users might want to alias the silly name!)
%-------------------------------------------------------------------
%
% strategy: 1) gather para into \vbox
% 2) break open vbox, and trim off last \hbox (= last line)
% 3) insert glue to compensate for \parfillskip
% 4) put back last line
% 5) insert the para for real
\def\parwithlastlinecentred#1\par{
\setbox0=\vbox{\noindent#1\endgraf}% set para
\setbox0=\vbox{% everything happens inside here
\unvbox0 \setbox0=\lastbox % move last line to box0
\hskip0pt plus1fil % now compensate for the \parfillskip
\unhcopy0 % put last line back
}% end of enclosing box0
\box0\endgraf % do the insertion
}
% here's a demonstration...
\hsize=3in
\parwithlastlinecentred
aaa bbb ccc ddd eee fff ggg hhh iii jjj kkk lll mmm
nnn ooo ppp qqq rrr sss ttt uuu vvv www xxx yyy zzz
aaa bbb ccc ddd eee fff ggg hhh iii jjj kkk lll mmm
nnn ooo ppp qqq rrr sss ttt uuu vvv www xxx yyy zzz
aaa bbb ccc ddd eee fff ggg hhh iii jjj kkk lll mmm
nnn ooo ppp qqq rrr sss ttt uuu vvv www xxx yyy zzz
aaa bbb ccc ddd eee fff ggg hhh iii jjj kkk lll mmm
nnn ooo ppp qqq rrr sss ttt uuu vvv www xxx yyy zzz
\bye
Steve Tinney@um.cc.umich.edu
------------------------------------------------------------------------
Date: Sun, 23 Apr 89 14:58:29 pdt
From: merrell@wallaby.mrc.uidaho.edu
Subject: Re: Latex Form Letter
Keywords: LaTeX, letter
Larry Atkinson <lpa@cs.odu.edu> writes:
>
> I would appreciate information on producing form letters with
> multiple addresses. Thanks ahead of time.
> Larry Atkinson
>
Following is a bit of latex code I recently found for doing just what you
are seeking. You have variables for the opening address and the opening of
the letter.
Have fun.
Randy Merrell
Microelectronics Research Center "Rejoice in the Lord always;
College of Engineering again I say, rejoice!"
University of Idaho -- Phil. 4:4
Moscow, ID 83843
UUCP: ucdavis!egg-id!ui3!rmerrell
BITNET: rmerrell@groucho.mrc.uidaho.edu
%% [merge.sty]
%%
%% MERGE -- A Form Letter Option to the LaTeX Letter Style
%%
%% by
%%
%% Graeme McKinstry
%% Computing Services Centre
%% University of Otago
%% P O Box 56
%% Dunedin, New Zealand
%%
%% graeme%otago.ac.nz@relay.cs.net
%%
%% A version of these macros appeared in TUGboat 8 #1, April 1987.
%%
%% Merge is a substyle [option] under the Latex style 'Letter' which
%% merges a standard letter with a separate file containing addresses
%% and opening lines. Merge will read {address}{opening} pairs from a
%% specified file and merge them with a form letter by producing a separate
%% letter environment (containing unique "\begin{letter}{address}" and
%% "\opening{opening}" commands) for each pair.
%%
%% Detailed instructions for preparation of the form letter and the
%% separate address file appear below, after the macros.
%%
%%
%% 27 July 1988
%% Special Thanks go to B. Beeton (BNB@SEED.AMS.COM) for
%% -- supplying the raw TeX and documentation from the TUGBoat article;
%% -- adding some documentation;
%% -- and for placing this file in the <tex.tugboat> archives at score.
%%
%% 28 July 1988
%% C. Roberson (csrobe@icase.[arpa|edu], csrobe@[wm]cs.wm.edu)
%% -- some additional documentation (mostly cleanup for .sty file);
%% -- changed ID message to a form more similar to LaTeX's;
%% -- changed "Could not open file" to "Could not open address file"
%% so user would better understand for which filename TeX
%% was prompting with the string "\@mergefile=";
%% -- tested merge.sty; It works! Thanks, Graeme!
%% -- submitted file to /public/latex-style archives @ cs.rochester.edu.
%%
%% 6 September 1988
%% G. McKinstry
%% -- enhanced the macros to handle running headlines properly;
%% -- fixed some other problems from the original version not addressed
%% fully by C. Roberson;
%% -- submitted new file to the latex-style archives.
%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% csr - changed next line to conform more to LaTeX greeting.
\typeout{Letter Sub-Style 'Merge'. Release 6 October 1986 by Graeme McKinstry}
%% The basic algorithm is:
%% 1. Open the address file.
%% 2. Read the addresses file getting the address and opening line.
%% 3. Process the contents of the MERGE environment and store it
%% in a box (\@store). This is the standard part of the letter.
%% 4. Produce the start of the letter (your address (including date),
%% their address, and the opening line).
%% 5. Make a copy of the standard letter (\@store) and unbox this copy.
%% 6. Repeat steps 2, 4, and 5 (not 3) until there are no more addresses.
\newbox\@store
\long\def\@contents{\global\setbox\@store=\vbox\bgroup} % store the contents
\long\def\@endcontents{\egroup} % of the letter
\def\@sendaddress{test}
\def\@openingtext{test}
\newif\if@firsttime % For storing the standard letter
\@firsttimetrue % the first time through.
\newread\@addrfile % allocate an input stream
\def\@openfile{\openin\@addrfile=\@mergefile % open the address file
\ifeof\@addrfile % i.e., didn't open successfully
\loop
\immediate\write16{Could not open address file \@mergefile}
\closein\@addrfile % close the input stream
\read16 to \@mergefile % get another file name
\openin\@addrfile=\@mergefile % open up input stream
\ifeof\@addrfile
\repeat % repeat until successfully opened
\fi}
% The merge environment (used as the \begin{merge}. The argument (#1) is
% the name of the file containing the addresses (a default of .tex extension)
% This file is opened (\@openfile), read (\@readfile), and then the box
% containing the contents of the standard letter is started (\@contents).
\def\merge#1{\def\@mergefile{#1 }\@openfile
\@readfile
\@contents}
% Read address file getting the address and opening line. If this is the
% first through then there is no reason to call \endmerge as this will
% be called later on (when \end{merge} is used).
\def\@getopeningline{\global\read\@addrfile
to\@openingtext} % get the opening line
\def\@readfile{\global\read\@addrfile to\@sendaddress % get the address
\ifeof\@addrfile
\let\next=\relax
\else
\@getopeningline
\if@firsttime
\let\next=\relax
\else
\let\next=\endmerge
\fi
\fi\next}
\newbox\@letterbox % For copy of \@store (the box containing the standard
% letter.
\def\endmerge{\if@firsttime\@endcontents\global\@firsttimefalse\fi %
% end contents if it is the first time
\bgroup\let\oldletter=\letter
\def\letter##1\@relax{\oldletter{##1}} % redefines letter
\expandafter\letter\@sendaddress\@relax % need to expand \@sendaddress
\opening{\@openingtext\vskip2\parskip}
\setbox\@letterbox=\copy\@store % copy the contents of the letter
\unvbox\@letterbox
\endletter\egroup
\ifeof\@addrfile
\message{End of file}
\let\next=\relax
\else
\let\next=\@readfile % loop round yet again
\fi\next}
\endinput
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%% A letter, say LETTER.TEX, would be set up as follows:
%% \documentstyle[merge]{letter}
%%
%% \address{...} % your address
%% \signature{...} % your signature
%%
%% \begin{document}
%% \begin{merge}{myaddresses} % MYADDRESSES.TEX contains addresses+openings
%%
%% With regard to .... % letter starts
%%
%% \closing{...} % closing
%% \ps{...} % \ps, \encl, \cc, etc.
%%
%% \end{merge}
%% \end{document}
%% The address file, MYADDRESSES.TEX, would contain:
%% {Computing Services Centre, \\ % first address
%% University of Otago, \\
%% Dunedin, \\
%% New Zealand}
%% {Dear Graeme,} % \opening for first address
%% {Charles S. Roberson\\ % next address
%% Dept. of Computer Science\\
%% College of William and Mary\\
%% Williamsburg, VA 23185}
%% {Dear Chip,} % next \opening
%% .... % etc.
%% NOTES:
%% Braces are matched, except that if the input is only one line then it
%% is not necessary to contain it within braces.
%% It is important to leave NO BLANK LINES at the end of the address file.
%% Be sure to supply the "\\" for breaking the addresses. -csr
%% [merge.sty]
---------------------------------------------------------------------------
Date: 21-APR-1989 18:16:34 GMT
From: P_TAYLOR%KIRK.ASTON.AC.UK@UWAVM.ACS.WASHINGTON.EDU
Subject: Re: LaTeX fonts at 118dpi
Keywords: LaTeX, fonts
Forgive a non-LaTeX person for possibly trying to teach his grandmother to suck
eggs, but surely Sebastian Rahtz, in suggesting that a full set of LaTeX fonts
at 118dpi comprises, for \magstep0,
>>> NOMAG = lasy10.118gf lasy5.118gf lasy6.118gf lasy7.118gf lasy8.118gf \
>>> lasy9.118gf lasyb10.118gf lcircle10.118gf lcirclew10.118gf \
>>> line10.118gf linew10.118gf
is making a gross over-simplification ? Doesn't LaTeX also require cmr, cmbx,
cmti, etc., etc., etc. ?
Philip Taylor
Royal Holloway and Bedford New College.
-------------------------------------------------------------------------------
Date: Sat, 22 Apr 1989 21:07:17 CDT
From: Don Hosek <U33297%UICVM.UIC.EDU@UWAVM.ACS.WASHINGTON.EDU>
Subject: Chinese and Korean coding schemes
Keywords: Chinese, Korean, fonts
Can anybody supply me with code tables for the Chinese and Korean national
character sets?
Thanks in advance
dh
Don Hosek Internet: U33297@UICVM.UIC.EDU
3916 Elmwood Bitnet: U33297@UICVM.BITNET
Stickney, IL 60402 DHOSEK@YMIR.BITNET
Work: 312-996-2981 UUNet: dhosek@jarthur.claremont.edu
JANET: U33297%UICVM.UIC.EDU@UK.AC.EARN-RELAY
-------------------------------------------------------------------------
Date: Fri, 21 Apr 89 10:39:36 MET
From: Victor Eijkhout <U641000%HNYKUN11.BITNET@Forsythe.Stanford.EDU>
Subject: What do you mean "french" spacing?
Keywords: TeX
This has been puzzling me for a while...
When I first read the TeXbook, I was impressed by the trickery
that put double space after a period, even when that period
was hidden inside brackets. Then, I realised that the result
was undesirable: a period carries its own space, and the extra
space breaks the evenness of the paragraph that TeX achieves so
admirably by its line breaking algorithm.
Let me quote two sources that agree with me.
In a paragraph entitled "don't impose typewriter habits",
Rubinstein (Digital Typography, Addison-Wesley 1988) writes
Do not double space or add extra space after periods or other
punctuation. The usual typesetting practice is to use the
same spacing as between words, although there are differences of
opinion [...]. However, putting two space characters in the text
may add far too much space, and the period itself creates some
extra visual space because of its size and position.
Adding space after punctuation encourages the formation of rivers
of white within the text.
For a statement from the non-digital world consult the "Hart's rules
for compositors and readers at the Oxford University Press"
(39th edition, the first was printed before America was discovered:-)
The space of the line should be used after all points
in normal text. A special direction, `Close, with extra space
after sentence full points', will be given for works which require
an extra space after sentence full points (e.g. some bibliographies,
dictionaries, and Classical texts).
So, why did Knuth so emphatically put the 'nonfrenchspacing' in TeX
as the default? (Maybe the rumour is true that he wrote TeX to
typeset 'the art of computer programming', which no doubt he
intended to be a Classical text. :-)
Victor Eijkhout Department of Mathematics
University of Nijmegen
Toernooiveld 5
"Far out in the uncharted 6525 ED Nijmegen, the Netherlands
backwaters of the unfash-
ionable end of the 080-613169
western spiral arm
of the galaxy" u641000@HNYKUN11.BITNET
%%% Moderators' note: North American (also British Isles?) conventions
%%% for typesetting are rather different from continental European
%%% styles. The double-word-space after sentence end in anything but
%%% typewriter monospace fonts is an abomination, but a slight increase
%%% in space following punctuation marks is the general practice in
%%% much, and I believe in most, North American typesetting. The way
%%% it is set up in TeX makes it possible to adjust the effect precisely,
%%% and to make it essentially dependent on the average length of
%%% interword space in the line. The effect can be as gross or as delicate
%%% as you wish to make it, and can be adjusted individually for each
%%% of the many possible marks of punctuation. In setting Italian, French
%%% or Dutch a North American is well advised to defer to the established
%%% habits for that language but, for English at least, there is some
%%% argument in favor of the increased readability that results when
%%% the natural breath-pauses in the language are made slightly more evident.
------------------------------------------------------------------------
Date: Fri, 21 Apr 89 20:38 O
From: <SXOINAS%GRCRVAX1.BITNET@UWAVM.ACS.WASHINGTON.EDU>
Subject: Re: Dec's macro package...
Keywords: TeX, macros
Hi from Crete.
During the last week we were trying to write a small manual.
It just came to our mind that Dec's manuals are written on TeX.
Does anybody know if Dec's macros can be found somewhere or are
used only from Dec and are not public domain?
Thanks for your time.
Bye.
Giannis.
----------------------------------------------------------------------
Date: Fri, 21 Apr 89 15:45:07 PLT
From: Dean Guenther <GUENTHER%WSUVM1.BITNET@UWAVM.ACS.WASHINGTON.EDU>
Subject: Re: TeXhax Digest V89 #23 (IBM 3812)
Keywords: IBM 3812
> find later backissues? Or better yet, where I may obtain the mode
> settings for the 3812?
The settings are found in Doug Henderson's mode_def settings column
in the TUGboat. The specifics are:
mode_def ibm_a = % ibm mode: for the IBM3812
proofing:=0; % no, we're not making proofs
fontmaking:=1; % yes, we are making a font
tracingtitles:=0; % no, don't show titles in the log
pixels_per_inch:=240;
blacker:=.4; % (this value is conjectural)
fillin:=-.2; % (ditto)
o_correction:=.4; % (ditto)
enddef;
-- Dean Guenther
-------------------------------------------------------------------------------
%%% 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 <your name> % to subscribe
%%% or UNSUBSCRIBE TEX-L <your name>
%%% 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.
%%%
%%% 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.95 (2.98 coming) metafont 1.7
%%% plain.tex 2.94 plain.mf 1.7
%%% LaTeX 2.09 ( 8/10/88) cmbase.mf see cm85.bug
%%% SliTeX 2.09 gftodvi 1.7
%%% tangle 2.9 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
%%% AmSTeX 1.1d
%%%\bye
%%%
End of TeXhax Digest
**************************
-------