summaryrefslogtreecommitdiff
path: root/info/digests/texhax/93/texhax.11
diff options
context:
space:
mode:
Diffstat (limited to 'info/digests/texhax/93/texhax.11')
-rw-r--r--info/digests/texhax/93/texhax.11635
1 files changed, 635 insertions, 0 deletions
diff --git a/info/digests/texhax/93/texhax.11 b/info/digests/texhax/93/texhax.11
new file mode 100644
index 0000000000..447f8d48b4
--- /dev/null
+++ b/info/digests/texhax/93/texhax.11
@@ -0,0 +1,635 @@
+TeXhax Digest Friday, 2 Jul 1993 Volume 93 : Issue 011
+
+% The TeXhax Digest is brought to you as a service of the TeX Users Group %
+% and UK TeX Users Group in cooperation with the UK TeX Archive group %
+
+Today's Topics:
+ METAFONT memory usage - position dependency
+ New ftp procedures for VM/CMS TeX
+ Why \markboth{}{} used in standard LaTeX report style?
+ QED command
+ BIBTeX
+ psnfss smallcaps problem
+ Free tex and latex
+ LaTeX3 public documents available
+
+
+Administrivia:
+ Moderators: David Osborne and Peter Abbott
+ Contributions: TeXhax@tex.ac.uk
+ Administration, subscription and unsubscription requests:
+ TeXhax-request@tex.ac.uk
+
+----------------------------------------------------------------------
+
+Date: Wed, 16 Jun 1993 13:19:11 -0700
+From: "Rex H. Shudde" <0024P@NAVPGS.EARN>
+Subject: METAFONT memory usage - position dependency
+
+Recently I ran into a curious Metafont situation. I had created a
+series of 36 characters (all 40 pt in height) using the emTeX version
+of Metafont (Version 2.0 [3a]). I then changed the size to 60 pt to
+create a larger set, but got the dreaded, "METAFONT capacity exceeded,
+sorry [main memory size=65531]," error message while the 29th
+character was being generated.
+
+The program is set up so that each symbol is in a separate file which
+starts with a <beginchar(...);> statement and ends with an <endchar;>
+statement. A driver program sets up initial housekeeping and then
+inputs each of the symbol files in turn. What I did next was add a
+<showstats;> statement between each of the input statements, go back
+to the 40 pt size, and rerun the program to generate the log file to
+see which of the characters was chewing up memory and then try to
+clean those particular files. I did what I thought was a pretty good
+cleanup job, and then regenerated the characters again. To my dismay,
+the new log file was identical to the old file---all of my cleanup had
+done nothing!
+
+The next thing I thought of was to generate the offending characters
+before any of the other characters with the hope that I might find
+something that they had in common (or lacked in common). After
+rerunning, I discovered from the log file that I had gained a little
+memory. That is, after the 36th symbol was generated I had a little
+bit more memory "untouched" than in the previous run. I repeated this
+process several times, moving the input of files that seemed to cause
+increased memory usage up to the top. Curiously enough, some of the
+files that previously caused increased memory usage no longer did.
+After about five such iterations it appeared that I had gained enough
+memory to be able to generate the characters at 60 pt, and it turned
+out that this was true. All 36 characters were created at 60 pt
+without a hitch.
+
+Sorry that this has been so long winded, but my primary question is,
+"why is total memory requirement of Metafont dependent upon the order
+in which the characters are generated?" Also, why isn't the memory
+between the <beginchar(...);> and <endchar;> reallocated to the memory
+pool since, presumably, once you've generated a character you're
+through with that section of code? (Or maybe there is a way to return
+the memory to the unused memory pool that I'm not aware of.) Finally,
+is there some better parameter to dump to the log file (incidently,
+the "string usage" readout that comes with <showstats;> was identical
+on all runs) than <showstats;>? Any and all comments will be much
+appreciated.
+
+R. H. Shudde
+Bitnet: 0024p@navpgs
+Internet: 0024p@vm1.cc.nps.navy.mil
+
+------------------------------
+
+Date: Wed, 16 Jun 1993 17:13:39 -0700
+From: Dean Guenther <GUENTHER@TIGGER.CSC.WSU.EDU>
+Subject: New ftp procedures for VM/CMS TeX
+
+There are now new procedures to ftp VM/CMS TeX and utilities. You now log into
+the anonymous account as follows:
+
+
+ FTP wsuvm1.csc.wsu.edu
+ logon anonymous
+ cd tex.191
+
+Dean Guenther Internet: guenther@tigger.csc.wsu.edu
+Washington State University Bitnet: guenther@cougar
+Pullman, WA. 99164-1220 AT&T: 509 335-0433
+ fax: 509 335-0540
+
+------------------------------
+
+Date: Sun, 20 Jun 1993 20:07:27 -0700
+From: "Ethan V. Munson" <munson@acacia.CS.Berkeley.EDU>
+Subject: Why \markboth{}{} used in standard LaTeX report style?
+
+I'm the current maintainer of the ucthesis style (for University of
+California dissertations), which is based closely on the standard
+LaTeX report style. I asked this question of the comp.text.tex USENET
+newsgroup but got no reply. So, I'm now trying TeXhax.
+
+One user of the ucthesis style wanted to put the text "Draft" on every
+page and tried to use the \markboth command to do so. It didn't work
+because the definition for \part invokes
+
+ \markboth{}{}
+
+which overrode the user's \markboth. Is there an important reason why
+the report style does this? It seems to me that the user is trying to
+do something very reasonable and I don't see why it shouldn't be
+possible. So, I'm sorely tempted to remove the \markboth from the
+definition of \part in the ucthesis style.
+
+Thanks for your help,
+
+Ethan Munson
+munson@cs.berkeley.edu
+
+------------------------------
+
+Date: Wed, 23 Jun 1993 09:36:44 -0000
+From: Martin Ward <Martin.Ward@durham.ac.uk>
+Subject: QED command
+
+I recently decided I wanted a marker to denote the end of a proof.
+Digging around in my style file archive I came up with a macro by
+Paul Vojta (vojta@guinness.ias.edu) (vintage May 1990), based on
+p. 106 of the TeXbook. I have modified this to work in three different
+situations in LaTeX:
+ (1) At the end of a text paragraph
+ (2) Inside the LaTeX displayed equation brackets \[...\]
+ (3) After the last equation in a LaTeX eqnarray (just before the
+ \end{eqnarray} command).
+
+Below is an example file illustrating the three cases.
+
+Comments, criticism, bugs, fixes etc. are welcome.
+
+ Martin.
+
+JANET: Martin.Ward@uk.ac.durham Internet (eg US): Martin.Ward@durham.ac.uk
+or if that fails: Martin.Ward%uk.ac.durham@nsfnet-relay.ac.uk
+or even: Martin.Ward%DURHAM.AC.UK@CUNYVM.CUNY.EDU
+BITNET: Martin.Ward%durham.ac.uk@UKACRL UUCP:...!uknet!durham!Martin.Ward
+
+%%%%%%%%%%%%%%%%%%%% CUT HERE %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%% qed.sty: a LaTeX style for putting a symbol to mark the end of a proof.
+%% Copyright 1993 Martin Ward
+%% Email: Martin.Ward@durham.ac.uk
+%% or: Martin.Ward%DURHAM.AC.UK@CUNYVM.CUNY.EDU
+%%
+%% This program is free software; you can redistribute it and/or modify
+%% it under the terms of the GNU General Public License as published by
+%% the Free Software Foundation; either version 2 of the License, or
+%% (at your option) any later version.
+%%
+%% This style file defines a command \qed which displays a "QED symbol"
+%% (by default, a black rectangle) at the right margin.
+%% It is designed to be placed at the end of a mathematical proof.
+%% It works in three different situations:
+%% (1) At the end of a text paragraph
+%% (2) Inside the LaTeX displayed equation brackets \[...\]
+%% (3) After the last equation in a LaTeX eqnarray (just before the
+%% \end{eqnarray} command).
+%%
+%% In cases (1) and (3), no extra vertical space should appear.
+%% In case (2) the vertical space after the equation is removed and
+%% a new paragraph started (does anyone have a fix for this?)
+%% Note: it doesn't work inside \begin{equation}...\end{equation}.
+%%
+%% If \[ \matrix ... \endmatrix \qed \] doesn't work, then try
+%% \[ \qed \matrix ... \endmatrix \] The latter approach will always work,
+%% although it is more wasteful of processing time.
+%%
+\def\qedsymbol{\vrule width.6em height.5em depth.1em\relax}
+\def\qed{\ifx\\\@eqncr\let\next\eqnarrayqed\else
+ \ifmmode\let\next\eqnqed\else
+ \let\next\textqed\fi\fi\next}
+\def\eqnqed#1\]{\belowdisplayskip\z@\belowdisplayshortskip\z@
+ \postdisplaypenalty\@M\relax#1
+ \]\par{\lineskip\z@\baselineskip\z@\vbox to\z@{\vss\noindent\textqed}}}
+\def\textqed{{\unskip\nobreak\hfil\penalty50\hskip2em\null\nobreak\hfil
+ \qedsymbol\parfillskip\z@\finalhyphendemerits0\par}}
+\def\eqnarrayqed{\\\noalign{\vspace{-\jot}%
+ {\lineskip\z@\baselineskip\z@%
+ \vbox to\z@{\vss\noindent\textqed}}%
+ \vspace{-\baselineskip}}}
+\endinput
+%%%%%%%%%%%%%%%%%%%% CUT HERE TOO %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\documentstyle[qed]{article}
+
+\begin{document}
+
+Some well-known facts:
+\begin{eqnarray*}
+1+1 &=& 2 \\
+2+2 &=& 4
+\qed
+\end{eqnarray*}
+This is a paragraph of text. This is a paragraph of text. This is a paragraph
+of text. This is a paragraph of text. This is a paragraph of text. This is a
+paragraph of text.
+This is an equation:
+\[
+1+1=2\qed
+\]
+This is a paragraph of text. This is a paragraph of text. This is a paragraph
+of text. This is a paragraph of text. This is a paragraph of text. This is a
+paragraph of text.
+\qed
+This is a paragraph of text. This is a paragraph of text. This is a paragraph
+of text. This is a paragraph of text. This is a paragraph of text. This is a
+paragraph of text.
+
+\end{document}
+
+------------------------------
+
+Date: Wed, 23 Jun 1993 12:36:08 +0200
+From: sven@ling.gu.se (Sven Stroemqvist)
+Subject: BIBTeX
+
+Hi,
+is there a BIBTeX macro for the kind of
+style sheet Lawrence Erlbaum Publ. requires?
+Would anybody know?
+regards,
+Sven Stromqvist
+Dept of linguistics
+Univ of Goteborg, Sweden
+sven@ling.gu.se
+
+------------------------------
+
+Date: Wed, 23 Jun 1993 14:54:35 -0700
+From: pss@maxwell.esd.ray.com (Peter Simon x3726)
+Subject: psnfss smallcaps problem
+
+Greetings, TeXnicians!
+
+I recently obtained the psnfss macros from ftp.shsu.edu and
+am experiencing a problem with Small Caps versions of the
+Postscript fonts:
+After running psnfss.tex through LaTeX, I submitted the
+resulting psnfss.dvi file to dvips, which complained that
+font pplrc was missing. I checked, and both pplrc.tfm and
+pplrc.vf were included in the distribution and correctly
+installed. It seems that the problem is that there
+is no entry for pplrc in the psfonts.map file which
+is consulted by dvips for mapping short TeX names
+to actual Postscript names. Looking further,
+I found that there were {\em no} entries describing
+any Small Caps versions of fonts. A bit more
+investigation revealed to me that this is probably
+because distinct Small Caps versions of fonts do not exist---
+they are created from other typefaces by performing
+Postscript tricks with scaling.
+
+I don't know how to perform such a trick. Could someone
+please tell me how, or better yet, send me the
+entries from your psfonts.map file which describe the
+Small Caps fonts, along with any Postscript code which
+they invoke? (I presume the latter is to be placed
+in the file texps.pro?)
+
+Thanks,
+
+Peter S. Simon
+Raytheon ESD, Dept 9282
+6380 Hollister Ave.
+Goleta, CA 93117, USA
+
+pss@coulomb.esd.ray.com
+
+------------------------------
+
+Date: Wed, 30 Jun 1993 20:09:13 +0000
+From: mfchen@eagle.fsl.noaa.gov (MFChen)
+Subject: Free tex and latex
+
+Where I can get free and easy-to-installed tex and latex?
+
+- -Nick
+
+------------------------------
+
+Date: Wed, 16 Jun 1993 18:21:52 -0600
+From: "George D. Greenwade" <bed_gdg@SHSU.edu>
+Subject: LaTeX3 public documents available
+
+***Documents related to the LaTeX3 project***
+
+This collection of documents will contain papers from the core project
+team and from other volunteers. Some will be progress reports, others
+will be outlines of work which needs to be done and, as the project
+develops, there will be definitive papers describing aspects of the
+new system.
+
+All these documents are being made public to encourage you to find out
+more about the project and to foster constructive comments and further
+ideas. One of the files, LTX3PUB.BIB, contains a BibTeX-style list of
+all the public LaTeX3 documents in the collection. Each file also has
+a header containing bibliographic information.
+
+In addition to these documents, the collection will also contain style
+files: some of these are needed only for particular documents as they
+enable the author to describe a particular subject; but some will be
+main styles and style options for whole classes of documents in the
+collection. At present there is just one of these: L3MS001.STY (MS =
+main style). This is the main style of all the documents currently in
+the collection. It is an adaptation of the standard ARTICLE.STY; it
+produces a cover sheet and running heads/foots using information
+extracted from the file header.
+
+At present, in addition to l3ms001.sty, the following files are available:
+====================================================================
+ filename = "l3d001.tex",
+ archived = "*Niord.SHSU.edu:[FILESERV.LTX3PUB]",
+ author = "Frank Mittelbach and Chris Rowley",
+ doc-group = "Project core team",
+ title = "The {\LaTeX3} Project",
+ version = "1.02",
+ date = "02 April 1993",
+ time = "22:47:45 GMT",
+ status = "public, official",
+ abstract = "This is a brief sketch of the \LaTeX3
+ Project: background, history, principles,
+ aims and functionality.
+
+ The new version of \LaTeX{} is, like the
+ current version, a freely available system
+ for automated processing of structured
+ documents, formatting them to the highest
+ typographic standards by use of the \TeX{}
+ typesetting software.
+
+ Although its uses include a very large
+ range of published documents, the
+ importance of its unsurpassed ability to
+ format mathematical formulas will not be
+ forgotten in producing the new version.
+
+ It is being produced by an international
+ group of volunteers under the technical
+ direction of Frank Mittelbach.",
+ note = "submitted to the Euromath bulletin",
+====================================================================
+ filename = "l3d003.tex",
+ archived = "*Niord.SHSU.edu:[FILESERV.LTX3PUB]",
+ author = "Frank Mittelbach and Chris Rowley",
+ doc-group = "Project core team",
+ title = "{\LaTeX3} Projektwoche in Mainz",
+ version = "1.02",
+ date = "02 April 1993",
+ time = "22:47:23 GMT",
+ status = "public, official",
+====================================================================
+ filename = "l3d004.txt",
+ archived = "*Niord.SHSU.edu:[FILESERV.LTX3PUB]",
+ author = "Frank Mittelbach and Chris Rowley",
+ doc-group = "Project core team",
+ title = "The {\LaTeX3} Project; Report 1991--92",
+ version = "1.00",
+ date = "01 April 1993",
+ time = "13:37:20 GMT",
+ status = "public, official",
+ abstract = "This report describes the current
+ activities of the \LaTeX3 project.
+ After a short project overview, the
+ major events of 1991 and 1992 are
+ described. Finally the project plan for
+ 1993 is presented.
+ ",
+ project-address = "LaTeX3 Project \\
+ c/o Dr. Chris Rowley \\
+ The Open University \\
+ Parsifal College \\
+ Finchley Road \\
+ London NW3 7BG, England, UK",
+ project-tel = "+44 71 794 0575",
+ project-FAX = "+44 71 433 6196",
+ project-email = "LTX3-Mgr@SHSU.edu",
+ copyright = "Copyright (C) 1993 LaTeX3 Project
+ and Frank Mittelbach and Chris Rowley.
+ All rights reserved.
+
+ Permission is granted to make and distribute
+ verbatim copies of this publication or of
+ coherent parts from this publication provided
+ this copyright notice and this permission
+ notice are preserved on all copies.
+
+ Permission is granted to copy and distribute
+ translations of this publication or of
+ individual items from this publication into
+ another language provided that the translation
+ is approved by the original copyright holders.
+
+ No other permissions to copy or distribute this
+ publication in any form are granted and in
+ particular no permission to copy parts of it
+ in such a way as to materially change its
+ meaning.",
+ generalinfo = "To subscribe to the LaTeX3 discussion list:
+
+ Send mail to
+
+ listserv@vm.urz.uni-heidelberg.de
+
+ with the following line as the body of the
+ message (substituting your own name):
+
+ subscribe LaTeX-L First-name Surname
+
+ to find out about volunteer work,
+ look at the document in the file
+ VOL-TASK.TEX, which can be obtained
+ electronically."
+====================================================================
+ filename = "vt02d01.tex",
+ archived = "*Niord.SHSU.edu:[FILESERV.LTX3PUB]",
+ author = "Daniel Flipo",
+ doc-group = "Volunteer Task VT02",
+ title = "Validation of {\LaTeX}~2.09
+ as part of the {\LaTeX3} project",
+ version = "1.02",
+ date = "25 March 1993",
+ time = "17:21:04 MET",
+ status = "public, contributed",
+ author-email = "flipo@alea.citilille.fr",
+ author-address = "Daniel Flipo, UFR de Math\'ematiques B\^at M2,
+ Universit\'e des Sciences et Technologies
+ F-59655 Villeneuve d'Ascq Cedex",
+ abstract = "This is both a call for volunteers to help
+ us in validating \LaTeX~2.09 (one of the
+ tasks of the \LaTeX3 project), and a brief
+ explanation of the kind of work to be done
+ in this area. ",
+ keywords = "Validation, LaTeX",
+====================================================================
+ filename = "vt05d01.tex",
+ archived = "*Niord.SHSU.edu:[FILESERV.LTX3PUB]",
+ author = "Ed Sznyter",
+ doc-group = "Volunteer task VT05",
+ title = "Research on Syntax for Tables",
+ version = "1.02",
+ date = "02 April 1993",
+ time = "22:48:49 GMT",
+ status = "public, contributed",
+ author-email = "ews@babel.babel.com",
+ abstract = "This is a preliminary overview of the direction
+ for further research on tables. Much research
+ remains to be done; in particular, the
+ bibliography needs to be expanded, especially
+ to include input from graphic designers and
+ SGML users.
+
+ Commonly requested features are listed, but
+ more are needed. Because of limitations in
+ \TeX\ and the small systems it must run on,
+ many capabilities necessary for high-quality
+ typesetting are unmanageable or must be
+ relegated to optional substyles. Nonetheless,
+ this list should include even functions we can
+ not implement, if only to document the reasons.",
+ keywords = "Tables.Syntax",
+====================================================================
+ filename = "vt11d01.tex",
+ archived = "*Niord.SHSU.edu:[FILESERV.LTX3PUB]",
+ author = "Mike Piff",
+ doc-group = "Volunteer task VT11",
+ title = "Backus-Naur form in {\LaTeX3}",
+ version = "1.03",
+ date = "02 April 1993",
+ time = "22:49:47 GMT",
+ status = "public, contributed.",
+ author-email = "M.Piff@sheffield.ac.uk",
+ author-address = "Department of Pure Mathematics \\
+ University of Sheffield \\
+ Hicks Building \\
+ Hounsfield Road \\
+ SHEFFIELD S3 7RH \\
+ England",
+====================================================================
+ filename = "vt16d01.tex",
+ archived = "*Niord.SHSU.edu:[FILESERV.LTX3PUB]",
+ author = "Rolf Lindgren",
+ doc-group = "Volunteer task VT16",
+ title = "Preliminary report on {\LaTeX} style
+ options to be converted to {\LaTeX3}",
+ version = "1.02",
+ date = "02 April 1993",
+ time = "22:53:48 GMT",
+ status = "Public, contributed.",
+ author-email = "rolfl@ulrik.uio.no",
+====================================================================
+ filename = "bnf.sty",
+ version = "1.05",
+ date = "09 Feb 1993",
+ time = "15:16:48 BST",
+ author = "Mike Piff",
+ address = "Dr M. J. Piff
+ University of Sheffield
+ Department of Pure Mathematics
+ Hicks Building
+ Hounsfield Road
+ SHEFFIELD S3 7RH
+ England",
+ codetable = "ISO/ASCII",
+ telephone = "+44 742 824431",
+ email = "M.Piff@shef.ac.uk (Janet)",
+ keywords = "Backus,Naur,syntax,grammar",
+ supported = "yes",
+ docstring = "A style option to LaTeX for producing
+ Backus-Naur Form syntax notation.",
+====================================================================
+ filename = "vol-task.tex",
+ version = "6.2a",
+ date = "30 April 1993",
+ time = "13:42:19.55 CDT",
+ list-manager = "George D. Greenwade",
+ address = "Department of Economics and Business Analysis
+ College of Business Administration
+ P. O. Box 2118
+ Sam Houston State University
+ Huntsville, Texas, USA 77341-2118",
+ email = "bed_gdg@SHSU.edu (Internet)
+ BED_GDG@SHSU (BITNET)
+ SHSU::BED_GDG (THENET)",
+ telephone = "(409) 294-1266",
+ FAX = "(409) 294-3712",
+ supported = "yes",
+ archived = "*Niord.SHSU.edu:[FILESERV.VOL-TASK],
+ pip.SHSU.edu:/vol-task.tex",
+ keywords = "LaTeX3, LaTeX, volunteer task list",
+ codetable = "ISO/ASCII",
+ docstring = "This is general volunteer task list in the
+ development of LaTeX3. There are many tasks
+ needing to be done in support of the LaTeX3
+ project which can be worked on concurrently with
+ the development of the LaTeX3 kernel.
+ Furthermore, some tasks require special expertise
+ not found among the core programming team.
+ Initial research, analysis, and work on these
+ tasks by volunteers can greatly speed up the
+ process of integrating a number of desirable
+ features into LaTeX3.
+
+ If you are interested in working on a particular
+ task, the first step is to contact the volunteer
+ list manager, noted above, for details. He will
+ either immediately designate you as the `task
+ coordinator' for that task, and assist you in
+ getting answers to any initial questions you may
+ have, or if someone else is already serving as the
+ task coordinator for that task, you will be put in
+ touch with that person, who will discuss with you
+ the current status of the work and ways in which
+ you might contribute."
+====================================================================
+As noted, each of these files is available for anonymous ftp retrieval from
+Niord.SHSU.edu (192.92.115.8) in the directory [FILESERV.LTX3PUB].
+Additionally, to retrieve the files via e-mail, include:
+ SENDME LTX3PUB.filename_extension
+in the body of a mail message to FILESERV@SHSU.BITNET (FILESERV@SHSU.edu).
+For example, to retrieve the file vt16d01.tex, include:
+ SENDME LTX3PUB.VT16D01_TEX
+in your mail to FILESERV. The command:
+ SENDME LTX3PUB
+will send all files with a one line request.
+
+Finally, these files are available for retrieval or perusal on the Gopher
+Server based on Niord.SHSU.edu (port 70) in either:
+ LaTeX3 Working Documents/
+or
+ TeX-related Materials/
+ LaTeX3 Working Documents/
+
+The file VOL-TASK.TEX also resides in these directories and may be
+retrieved in a parallel manner.
+
+As a side and quasi-related note, if you have a Gopher client and are into
+TeX and its relatives, you really ought to look at the:
+ TeX-related Materials/
+on Niord's server.
+
+Regards, George
+
+George D. Greenwade, Ph.D. Bitnet: BED_GDG@SHSU
+Department of Economics and Business Analysis THEnet: SHSU::BED_GDG
+College of Business Administration Voice: (409) 294-1266
+P. O. Box 2118 FAX: (409) 294-3612
+Sam Houston State University Internet: bed_gdg@SHSU.edu
+Huntsville, TX 77341 bed_gdg%SHSU.decnet@relay.the.net
+
+------------------------------
+
+Further information about the TeXhax Digest, the TeX
+Users Group, and the latest software versions is available
+in every tenth issue of the TeXhax Digest.
+
+Please send contributions to: TeXhax@tex.ac.uk
+
+Administration, subscription and unsubscription requests:
+ On Internet:
+ send a one line mail message to TeXhax-request@tex.ac.uk
+ SUBSCRIBE TEX-L <your real name>
+ UNSUBSCRIBE TEX-L
+ On BITNET:
+ send a similar one-line mail message to LISTSERV@xxx
+ On JANET:
+ send a similar one line mail message to TeXhax-request@uk.ac.tex
+
+Back issues of the digest are available for anonymous ftp from
+the UK TeX Archive, tex.ac.uk (134.151.40.18)
+ in [tex-archive.digests.texhax.YY]texhax.NN
+and ftp.tex.ac.uk (134.151.44.19)
+ in /pub/archive/digests/texhax/YY/texhax.NN
+where YY = last two digits of year, NN = issue number
+
+ftp.tex.ac.uk is also mirrored to pip.shsu.edu (192.92.115.10) and
+ftp.uni-stuttgart.de (129.69.1.12) as part of the Comprehensive TeX
+Archive Network, and may give better response for subscribers in the
+USA and Europe, respectively.
+
+\bye
+
+End of TeXhax Digest [Volume 93 Issue 11]
+*****************************************