TeXhax@Score.Stanford.EDU (TeXhax Digest) (06/30/88)
TeXhax Digest Thursday, June 30, 1988 Volume 88 : Issue 60
Moderator: Malcolm Brown
Today's Topics:
TeX on APOLLO Workstations
Vertical spacing in tables
Reading files from VMS sub-directories in LaTeX
Installing TeX on a SUN 3
Standardizing on PostScript TFMs
tolling the bell on theses double spacing
BitStream fonts on LN03
re: dvi2ps : how can I get a better version??
Honorary Degree for Donald Knuth
Page numbers in LaTeX
TeX hyphenation tables
DVI -> QMS/Talaris
Re: usage of Personal TeX Inc/Bitstream fonts
re: Directory pointers?
----------------------------------------------------------------------
Date: Fri, 17 Jun 88 16:47:56 pdt
From: Leonard Zubkoff <edsel!lnz@labrea.stanford.edu>
Subject: TeX on APOLLO Workstations
From time to time, various people have asked about the availability of TeX
software on Apollo Workstations. I'm happy to report that TeX and MetaFont are
indeed available and perform quite nicely on Apollos. In addition, I'd like to
announce the availability of a DVI previewer for Apollos.
To build TeX and MetaFont for the Apollo, you'll need a copy of the UNIX TeX
Tape from the University of Washington, together with a recent version of
WEB2C. When you create your "site.h" for WEB2C, you can "#define REGFIX". If
you run only 68020-based Apollos, as we do, I recommend you use the "-O -M3000"
switches to the C compiler; otherwise, just use "-O". If you need to build a
giant TeX (based on the comments in BIGTEX), you should compile it without
"-O".
The WEB2C version of TeX appears to be about 1.5 times faster than the old
Pascal-compiled TeX we had been using on the Apollo. TeX and MetaFont pass the
TRIP and TRAP tests respectively.
For the record, the particular versions of software I'm using are:
Operating System: Domain/OS SR9.7 and BSD4.2 Domain/IX SR9.5
C Compiler: Version 4.89
UNIX TeX Tape: Version of 16 February 1988
WEB2C: Version 2.15
DVIAPOLLO is a DVI previewer that uses the Domain Graphics Primitives (GPR) and
Apollo font files; it is based on a DVI previewer for the Sun and X that Tim
Freeman of CMU provided. Included with DVIAPOLLO is a program to convert TeX
PXL118 files into the form needed for use with DVIAPOLLO.
Pierre MacKay has kindly allowed me make "dviapollo.tar.Z" available for public
access from the "pub" directory on host JUNE.CS.WASHINGTON.EDU; it may be
retrieved from there by anonymous FTP.
Enjoy!
Leonard N. Zubkoff
LUCID, Incorporated
edsel!lnz@labrea.stanford.edu
------------------------------
Date: Sat, 18 Jun 88 10:29:33 EDT
From: "David F. Rogers" <dfr@USNA.MIL>
Subject: Vertical spacing in tables
G'day,
A quick, nonelegant fix to Brian Holmes' question about vertical spacing in
tables is given below as a small revision of his source. Basically all that
was necessay was to add \smallskip's before and after the existing \hrule in
the \noalign. The height of the \vrules still needs to be adjusted and the
template modified to give some space between the \vrule and the first letter
of the table entry.
%Date: Fri, 10 Jun 88 16:03:54 EDT
%From: Brian_Holmes%Wayne-MTS@um.cc.umich.edu
%Subject: \baselineskip command in \halign
%
%How can you expand the width of rows in \halign mode?
%I know about \strut but is there some way I can give a point
%size width of the row? \baselineskip appears not to work in
%\halign mode. Here is the source in question. Notice how the
%the HELLO's have a larger vertical space between them. How can
%I do this inside the \halign?
%--------------------------CUT-----------------------------------
\baselineskip=20pt{
\halign to 6.5in{\vrule#\hfill\tabskip=1em plus4em&\vrule#\hfill&
\vrule#\hfill&\vrule#\hfill&\vrule#\hfil&
\vrule#\hfill&#\vrule\tabskip=0pt\cr
\bf{NAME}&\bf{PHONE}&\bf{ADDRESS}&\bf{MTS ID}&\bf{CMS ID}&
\bf{DELIVERY}\cr \noalign{\par\smallskip\hrule\smallskip}
Adair, Joan&75636&113 IBM& &*ADAIR&F& \cr\noalign{\smallskip\hrule\smallskip}
Adams, Larry&74776&282 MEZZ&LDA&*LADAMS&T& \cr\noalign{\smallskip\hrule\smallskip}
Ader, Jim&70631&SCIL 59&UC29&*JADER&H& \cr\noalign{\smallskip\hrule}
}
\smallskip
Hello\par
Hello}
\vfil\eject
\bye
%---------------------------CUT---------------------------------
%Brian Holmes
%Wayne State University
%BITNET : BHOLMES@WAYNEST1
%INTERNET : Brian_Holmes%WU@UM.CC.UMICH.EDU
Professor David F. Rogers
Aerospace Engineering Department
U.S. Naval Academy
Annapolis, MD 21402
USA
Tel: 301-267-3283/4/5
ARPANET: dfr@usna.mil
UUCP: ~uunet!usna!dfr
------------------------------
Date: Sun, 19 Jun 88 15:18:46 PDT
From: KARNEY%PPC.MFENET@NMFECC.ARPA
Subject: Reading files from VMS sub-directories in LaTeX
BED_GDG@SHSU.BITNET wants to modify the directories LaTeX look in when
inputing a file. Here are two solutions:
(I) Our setup for LaTeX/TeX under VMS includes
$ temp = f$trnlnm("sys$login") - "]" + ".tex]"
$ if f$trnlnm("tex$lib").eqs."" then define/nolog tex$lib 'temp'
$ define/nolog tex$inputs tex$lib,tex$plain,tex$latex,-
tex$amstex,tex$doc
I.e., tex$inputs is a search list, with the user's [.tex] subdirectory
searched first. Of course the user is at liberty to redefine tex$lib, even
to make it a search list.
(II) The Kellerman and Smith version of TeX for VMS allows you to say
$ latex/input=(a:[b],c:[d]) foo
which effectively adds a:[b] and c:[d] to the end of the tex$inputs search
list. This method was needed because the Kellerman and Smith version of
TeX didn't (doesn't?) allow tex$inputs to be a search list.
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: Mon, 20 Jun 88 10:22:17 +0100
From: prlb2!uiag!colijn@uunet.UU.NET (Luc Colijn)
Subject: Installing TeX on a SUN 3
Hello,
Do you have experience with installing tex on a SUN-III (Berkeley 4.2) ?
I tried it, but I have problems with the undump-facility. The program
says : "Core file didn't come from this a.out".
If you know any solution, I'd be most gratefull.
Luc Colijn.
..!{uunet,mcvax}!prlb2!uiag!colijn
------------------------------
Date: Mon, 20 Jun 88 10:56:22 CDT
From: Don Hosek <U33297%UICVM.BITNET@Forsythe.Stanford.EDU>
Subject: Standardizing on PostScript TFMs
Before we declare Elwell's TFMs the definitive TFMs, perhaps we should
also come up with new names for them as well. While many good operating
systems allow fairly long names for files, others (in particular, CMS,
MVS, and MS-DOS) restrict file names to eight characters in length. VMS
also has a length restriction, although it isn't as drastic. I propose
that if we're going to declare these TFMs standard, we also come up with
names that will be unique to 8 characters for these files as well.
Following the model of the cm fonts, I suggest that the family name take
up the first 1-3 characters of the file name (hlv for helvetica, csb for
century schoolbook, tm for times modern, etc.) then 1-4 characters for
the style (r for roman, sy for symbol, i or ti for italic, sl for slanted,
n for narrow, etc.) finally followed by the type size (in the case of
fonts such as PostScript fonts which are merely scaled, and do not have
disticntive design sizes, this may be omitted). Thus, TimesItalicUnslanted
becomes tmu; and so forth.
-dh
------------------------------
From: Gordon Howell <mcvax!hci.hw.ac.uk!gordon@uunet.UU.NET>
Date: Mon, 20 Jun 88 15:51:41 BST
Subject: tolling the bell on theses double spacing
[Apologies to moderator: "The tale", as Tolkien said, "grew in the
telling." All noise until the last paragraph...]
One of the weapons in the arsenal of any bureaucracy will always be
the "standards" under which the member plebes of that bureaucracy must
live. As a typically static, self-perpetuating system, channels of
communication through the bureaucratic body must follow codified and
proven paths; not unlike (sometimes annoying, but always "necessary")
syntactic and stylistic conventions in a programming language.
These were my thoughts as I instructed Yet Another Graduate Student
--- who has just spent several frustrating but rewarding weeks
beautifully typsetting his erudite commentary on some obscure aspect
of computer science --- in the fine art of Document Demolition.
Unfortunately, concilitory as they were, my objective observations
were insufficient to vent off my usual steam on this issue... [so I am
trying you...]
I get a perverse pleasure from hearing that plaintive cry "How do I
double space my thesis?" and always answer (most innocently) "Why
would you want to do that?!" This gives me one of my great joys in
life --- standing on a soapbox --- in this case railing on about the
injustice of a computer science department which first teaches
students how to typeset [then I re-teach a few lucky ones LaTeX], then
charges for laserwriter usage by the page, then anachronistically
insists on double-spaced theses.
Properly chastised, the student retreats from my assault armed only
with \baselineskip and the hope that he'll never have to deal with
this (or me) again.
Enough? Rather than spend time playing with our fancy software toys
:-) let's try our hands at some *real* social change.
I have a dream that someday, from some obscure midwestern college, a
PhD thesis I receive on the "Ionization Decay Rates of FORTRAN Code"
will *not* be sent in University Standard Double Length.
I have a dream that someday, from the heights of decwrl, Leslie
Lamport will answer for the *last* time the eternal question.
I have a dream that someday, when I get off my butt, my *own* PhD
thesis will be of publishable quality (from a typsetting standpoint
that is!).
I invite Mr. Lamport (clearly a man after my own heart) to post a
short letter to the net, encased in proper LaTeX commands and gilded
and framed with credentials (footnoted with a permission to reproduce
and sufficient legal caveats) that I can use as support in an attack
on my own local organization on this issue. Together, we can start a
massive grassroots movement to forever eradicate the spectre of
Document Demolition.
[wow! Am I off the air yet...?]
Gordon Howell gordon@hci.hw.ac.uk
Scottish Centre for Human Computer Interaction
Edinburgh, Scotland
------------------------------
Date: Tue, 21 Jun 88 01:19 GMT
From: Peter Flynn UCC <CBTS8001%IRUCCVAX.UCC.IE@Forsythe.Stanford.EDU>
Subject: BitStream fonts on LN03
Enter your message below. Press CTRL/Z when complete, or CTRL/C to quit:
We have been experimenting here with BitStream and other fonts for the HPLJ2.
Having converted them on a PC into .tfm and .pk files, the obvious course
was to kermit them to the VAX and try there. Yeuccccccccccccch. Someone told
me that the dots on an LN03 were oval, not circular, as with other lasers
(or was it the other way round, I forget), but the results I wouldn't give
to a dog. My advice is, forget the LN03, get a HPLJ2 and a good driver.
Incidentally, we have a langerload of public domain fonts for the HPLJ2
which I have been sent from various BBs in the US, courtesy of the good
offices of David Holmes <holmesd@union>. I am in the process of
converting them to .tfm and .pk files and will make these available in
due course, probably September. The only problem (BitStream and PD) is
that the characters are strictly ASCII decimal 33 thru 126, no accents,
greek, nothing else. Now, if someone would offer to edit the files and
add the rest...
...Peter Flynn
------------------------------
Subject: re: dvi2ps : how can I get a better version??
Date: Wed, 22 Jun 88 08:43:47 -0700
From: kelem@aerospace.aero.org
> I am running on a Sun3/50 and I wish to print dvi files on an
>apple LaserWriterIINT. I am aware of the dvi2ps driver on the Unix
>TeX distribution; however, I would like to know if there are more
>up-to-date versions available. In order of importance, the features
>I am looding for are the following.
> 1. Use of pk rather than pxl fonts in order to save disk space.
> 2. Support for a reasonably flexible \special command for the
> inclusion of postscript diagrams.
> 3. Support for other drawing facilities.
>I cannot ftp. Please indicate indicate some other means of aquiring
>the software such as tape. Also indicate the cost if appropriate.
>Send replies either to TeXhax or to me directly.
We've got a version of dvi2ps that is based on the one from Washington.
It has the following features:
1. pk fonts
2. \special for including postscript files (with tranlation and scaling)
3. supports tpic drawings (not the Arbortext version) (thus fig and pic
drawings can be used)
4. odd/even page selection for double-sided printing
5. postscript fonts (not tested yet---wait till end of week)
6. multiple font directories through TEXFONTS environment variable
7. theoretically macintosh drawings can be included, but we have not been
able to test this.
Steve Kelem
The Aerospace Corporation
ddn: kelem@aerospace.aero.org
usenet: ...!trwrb!aero!kelem
------------------------------
Date: Wed, 22 Jun 88 22:59:40 BST
From: stoy%prg.oxford.ac.uk@NSS.Cs.Ucl.AC.UK
Subject: Honorary Degree for Donald Knuth
Readers may perhaps be interested in seeing the citation for Donald
Knuth, who received an honorary degree of Doctor of Science on 22 June
1988 from Oxford University.
PRESENTATION BY THE PUBLIC ORATOR
=================================
ILLVSTRISSIME ATQVE HONARATISSIME DOMINE CANCELLARIE,
VOSQVE EGREGII PROCVRATORES:
De machinis computatricibus quibus studiorum causa utimur saepissime et in
officinis et inter vina disputamus academici. {\it nota magis nulli domus est
sua\/} quam nobis apparatus illi molliores, ut vocantur, quos in machinis
illis dirigendis adhibemus,
visceribus mandata extrinsecus insinuantes.
Levia quidem sunt haec colloquia, \begingreek qelid'onwn \endgreek tantum
\begingreek mouse~ia\endgreek. subest tamen scientia subtilissima computandi
qua imbuti mandata illa docte machinis iniungimus, ut ordine praescripto data
digerant. `scientiam' dixi, `artem' tamen hic mavult appellare. artem enim
exercentis est eleganter rationem ingeniosam computandi excogitare ex qua non
solum artifex ipse sed etiam qui existimatores accuratius intuentur magna
concitatione mentis commoventur, magnam capiunt voluptatem.
Facultati igitur Artium debet hic quem produco adscribi, quamvis ad gradum
Doctoris in Scientia admittatur. quin etiam \begingreek fil'ologon\endgreek
debemus salutare qui de linguis quibus viri docti mandata exprimunt luculenter
scripsit nec non de verborum computatoriorum explicatione. etenim opus magnum
comparat, voluminibus iam tribus vulgatis, cui titulus est {\it Ars machinis
computatricibus mandata iniungendi}. quibus in libris genera omnia mandatorum
percensuit atque quo modo celerrime machina iussa quaelibet exsequatur
praescripsit. momentum ita ingens dedit scientiae toti computandi.
Partes vero nonnullas scientiae illius primus hic invenit. nam hoc primo
monente collegaque adiuvante didicerunt machinae quo modo formulam quamque
mathematicam optime resolvant atque vertant. mathematicorum etiam in
penetralia ingressus est, rationem numerandi occultam licet in libro
\begingreek >ezwterik~w| \endgreek perscrutatus qui multum de dialogis
Platonis vel Georgi Berkeley refert. quam lepide puellam istam iuvenemque
depinxit de legibus mathematicis rebusque infinitis colloquentes! mysteria
sunt haec studia quae summa reverentia intueor, \begingreek pr'oswjen
\endgreek tamen \begingreek >aspazomai\endgreek.
Multa etiam arti typographicae contulit. rationem enim librorum
mathematicorum machinis computatricibus faciendorum cui nomen est \begingreek
teq \endgreek inventam retexit: o \begingreek t'eqnhn \endgreek egregiam!
In civitate California educatus Professor est in Universitatis praeclara
Stanfordensi. fidem Lutheranam profitetur, organum pneumaticum feriatus
modulatur. elegantiam summam in libris scribendis praestat nec non
diligentiam, quippe qui historicorum modo rerum origines soleat attente
inquirere. nonne hic aptus est qui origines rerum antiquas indaget cui nomen
est antiquum regis nostri modestissimi?
Magnopere vero decet hoc anno quo scholares primi Oxonienses qui mathematicam
scientiamque simul computatoriam feliciter excoluerunt ad gradum admittentur
computatorum hunc maximum honorari.
Praesento vobis Donaldum Ervin Knuth, ut admittatur honoris causa ad gradum
Doctoris in Scientia.
ADMISSION BY THE CHANCELLOR
===========================
Computandi magister eminentissime, qui in arte numerandi mathematicos multa
docuisti, ceteris beneficia innumerabilia contulisti, ego auctoritate mea et
totius Universitatis admitto te ad gradum Doctoris in Scientia honoris causa.
[For any who may prefer it I append a translation...
PRESENTATION BY THE PUBLIC ORATOR TO THE CHANCELLOR AND PROCTORS
================================================================
There is much academic talk in our laboratories and Senior Common Rooms about
the computers we use for research. As Juvenal put it, {\it nobody knows his
own house better\/} than we know the software we use to programme these
machines,
Inserting orders in their entrails from without.
Such conversations are only gossip, mere swallows twittering in a concert
hall. But they have as their foundation the elaborate science of computation
which we must master to programme our computers correctly. I said a `science'
of computation, but our honorand would rather call it an art. For it is
characteristic of an art to work out elegantly an ingenious program which
inspires a pleasurable intellectual excitement in the programmer himself and
in the critics who review his work.
%%% Sorry, but the rest of the translation appears to have been munged
%%% at the hands of some unkind mailer. Anyone care to submit a complete
%%% translation? Malcolm
------------------------------
Date: Thu, 23 Jun 88 13:23 PST
From: <MIKE%UCDHEP.BITNET@Forsythe.Stanford.EDU> (Mike Hannon; UCD Physics; [916]-752-4966)
Subject: Page numbers in LaTeX
For reasons which I don't understand, the department for which I work prints
manuals with two different page numbers on each page, one number at the
top and the other at the bottom of the page.
The number at the bottom is a chapter-relative number. E.g., if the content
of the chapter is indicated by the word FOO, then the bottom page numbers
are FOO-1, FOO-2, FOO-3, etc. The number at the top is the usual, absolute
page number, which is continuous across chapters. I.e., if the FOO chapter
begins on the 29th page of the manual, then pages FOO-1, FOO-2, etc., are
also numbered 29, 30, etc.
I can find no way in LaTeX to get both page numbers simultaneously.
The \pagestyle command seems to give the LaTeX user control over one or
the other of these page numbers, but not both at once.
Can anyone suggest a solution? Thanks.
- Mike Hannon
MIKE@UCDHEP (Bitnet)
UCDHEP::MIKE (HEPnet)
916-752-4966 (Telephone)
------------------------------
Date: Thu, 23 Jun 88 15:29:51 PDT
From: suruagy@CS.UCLA.EDU (Jose A.S Monteiro)
Subject: TeX hyphenation tables
Hi,
I'm a graduate student at UCLA and I'm interested in the hyphenation
tables for foreign languages like: italian, portuguese, spanish and
french.
Any pointers would be much appreciated.
If the files are accessible via anonymous ftp that would be great.
Thanks in Advance,
Jose A. S. Monteiro
suruagy@cs.ucla.edu
------------------------------
Date: Fri, 24 Jun 88 09:17:35 pdt
From: mcdonald@loki-gw.hac.com (louis mcdonald)
Subject: DVI -> QMS/Talaris
Anyone know of a good DVI -> QMS/Talaris program that uses
PK files? I am NOT happy with the one provided by Talaris.
Louis McDonald
mcdonald%loki@hac2arpa.hac.com
------------------------------
Date: Wed Jun 22 19:20:28 MET 1988
From: XITIJSCH%DDATHD21.BITNET@Forsythe.Stanford.EDU
Subject: Re: usage of Personal TeX Inc/Bitstream fonts
In TeXhax #56 Gavin Burnage supplies
> Dominik Wujastyk, in his article on fonts TEXFONT.MEMO, dicusses the
> Personal TeX Inc. `Font Interface Package', an MS DOS program which
> converts BITSTREAM fonts into .PXL and .PK files. He says:
>
> > Users of operating systems other than DOS can presumably
> > use the Bitstream .PXL or .PK fonts once generated on a
> > PC/AT, just by uploading them with, say, Kermit.
>
> My question is: has anyone tried this procedure for a set-up similar to
> ours, namely TeX version 2.0 using microVAX II + LNO3 ? What were the
> problems, and was the result worthwhile ?
The usage of Bitstream fonts depends on your driver.
I.e., they are not correct PK or PXL fonts. The following
head of a PKtype of a Bitstream font at {\bf 360 dpi} shows this:
> This is PKtype, Version 2.1 (THD/ITI MUNIX Changes)
> Input file: bs0003
> 'PXTOPK 2.2 output'
> Design size = 10485760
> Checksum = 0
> Resolution: horizontal = 217637 vertical = 217637 (240 dpi)
> 36: Flag byte = 192 Character = 0 Packet length = 77
> Dynamic packing variable = 12
> TFM width = 524288 dx = 1114112
> Height = 42 Width = 21 X-offset = -2 Y-offset = 36
> (7)7(12)11(9)13(7)15(6)5(5)5(5)5(7)5(4)4(8)5(4)4(9)4(4)4(17)5
A resolution of 240 dpi is inserted in the fonts, resulting
in incorrect pixel widths (i.e., the dx values are wrong).
According to D. Knuth, every driver {\it must} use the
pixel widths and must adjust differences to the tfm width
like it is done in DVItype (with max_drift). But this still
results in characters which are positioned incorrectly.
An error description was sent to Personal TeX in autumn 1987
(c/o the german pc-TeX distributor) but no answer has been
received until March. I don't know if an answer arrived
since March.
But some drivers use only the tfm width (please note, that
there {\it are} differences between the tfm and the pixel
widths even in the cm fonts -- and they are desired!) and are
therefore able to print almost good looking documents
with these damaged fonts.
I regard this as an ironical situation: you can use the
fonts better if your driver is worse.
Escpecially the usage on VMS can pose an other problem with
your driver: the length of the PK files are not a multiple
of 512 Bytes, but most VMS drivers want font files in the fixed
file format with a record length of 512. Commonly used
transfer programs, like kermit or ftp, pad with NullBytes.
If your driver doesn't allow them, you have to change the
Nullbytes into bytes with the value 246 (a pk_no_op).
Hope, this helps you.
Joachim
TH Darmstadt
Institut f\"ur Theoretische Informatik
Joachim Schrod
Alexanderstr. 24 Bitnet: XITIJSCH@DDATHD21
(Please try again if I don't answer ---
D-6100 Darmstadt our Bitnet connection is very instable...)
West Germany
------------------------------
Date: Fri, 24 Jun 88 15:57 EST
From: "Jerry Leichter (LEICHTER-JERRY@CS.YALE.EDU)"
Subject: re: Directory pointers?
George Greenwade asks how to have LaTeX under VMS search, say, a local
directory and then the system directory for options files.
This requires no changes at all to LaTeX (or TeX): They use the logical
TEX$INPUTS to locate style files. VMS allows a logical to translate to
a search list. You create one with the ASSIGN (or DEFINE) DCL commands;
for example:
$ ASSIGN DISK1:[GDG.INPUTS],SYS$SYSDISK:[TEX.INPUTS] TEX$INPUTS
will cause an attempt to open TEX$INPUTS:OPTION.STY to look first for
DISK1:[GDG.INPUTS]OPTION.STY, then if that file doesn't exist for
SYS$SYSDISK:[TEX.INPUTS]OPTIONS.STY. You can have as many elements in
the search list as you like. TeX and LaTeX will neither know nor care that
there are search lists out there - the searching is carried out by the VMS
file system.
You can, of course, do the same for other logicals (such as TEX$FORMATS or
TEX$FONTS).
If you come from the TOPS-20 world, beware of one "gotcha'": On TOPS-20,
and assignment like:
$ ASSIGN A,B A
has the effect of appending B to A's previous translation. On VMS, it just
causes a loop when A is used. You'll need to substitute the actual system
definition of TEX$INPUTS where I had "SYS$SYSDISK:[TEX.INPUTS]" in the
assignment above.
Finally, if you want to include "the current directory" in a search list at
some point, use SYS$DISK:[].
-- Jerry
------------------------------
%%%
%%% Concerning subscriptions, address changes, unsubscribing:
%%% BITNET: send a one-line mail message to LISTSERV@TAMVM1.BITNET:
%%% SUBSCRIBE TEX-L <your name> % to subscribe
%%%
%%% All others: send mail to
%%% texhax-request@score.stanford.edu
%%% please send a valid arpanet address!!
%%%
%%%
%%% All submissions to: texhax@score.stanford.edu
%%%
%%% Back issues available for FTPing as:
%%% machine: directory: filename:
%%% [SCORE.STANFORD.EDU]<TEX.TEXHAX>TEXHAXnn.yy
%%% nn = issue number
%%% yy = last two digits of current year
%%%\bye
%%%
------------------------------
End of TeXhax Digest
**************************
-------