summaryrefslogtreecommitdiff
path: root/info/digests/texline/no13
diff options
context:
space:
mode:
Diffstat (limited to 'info/digests/texline/no13')
-rw-r--r--info/digests/texline/no13/1361
-rw-r--r--info/digests/texline/no13/13b30
-rw-r--r--info/digests/texline/no13/amiga46
-rw-r--r--info/digests/texline/no13/angus.tex473
-rw-r--r--info/digests/texline/no13/another80
-rw-r--r--info/digests/texline/no13/bcs-future29
-rw-r--r--info/digests/texline/no13/betsy47
-rw-r--r--info/digests/texline/no13/book-reviews303
-rw-r--r--info/digests/texline/no13/cheltenham81
-rw-r--r--info/digests/texline/no13/courses172
-rw-r--r--info/digests/texline/no13/dedham61
-rw-r--r--info/digests/texline/no13/didot63
-rw-r--r--info/digests/texline/no13/dtp89
-rw-r--r--info/digests/texline/no13/ep9278
-rw-r--r--info/digests/texline/no13/good_guys_plus57
-rw-r--r--info/digests/texline/no13/gut138
-rw-r--r--info/digests/texline/no13/lamstex80
-rw-r--r--info/digests/texline/no13/matter331
-rw-r--r--info/digests/texline/no13/newtwo-column166
-rw-r--r--info/digests/texline/no13/obit99
-rw-r--r--info/digests/texline/no13/playpen169
-rw-r--r--info/digests/texline/no13/rhead.txt859
-rw-r--r--info/digests/texline/no13/sgml18
-rw-r--r--info/digests/texline/no13/spivak185
-rw-r--r--info/digests/texline/no13/texline.head115
-rw-r--r--info/digests/texline/no13/texline.tex234
-rw-r--r--info/digests/texline/no13/toc63
-rw-r--r--info/digests/texline/no13/uktexug54
-rw-r--r--info/digests/texline/no13/unicode62
-rw-r--r--info/digests/texline/no13/vegas50
-rw-r--r--info/digests/texline/no13/verbar.tex33
31 files changed, 4326 insertions, 0 deletions
diff --git a/info/digests/texline/no13/13 b/info/digests/texline/no13/13
new file mode 100644
index 0000000000..8906caefe7
--- /dev/null
+++ b/info/digests/texline/no13/13
@@ -0,0 +1,61 @@
+\input texline
+\voffset-0.5in
+%\def\firstpage#1{\bgroup\advance\vsize by0.5in\voffset-0.5in
+%\bigcolheight=\vsize
+%\advance\bigcolheight by\bigcolheight
+%\advance\bigcolheight by 10pt
+%\pageheight=\vsize
+\input texline.head
+
+\begindoublecolumns
+\input spivak
+\bar\input playpen
+\bar\input unicode
+\bar\input bcs-future
+\bar\input sgml
+\bar\input cheltenham
+\bar\input matter
+\bar\input book-reviews
+\bar\input betsy
+\bar\input rhead.txt
+%\bar
+%\scaledpicture 31.6pc by 19.7pc (lamb scaled 450)
+\bar\input ep92
+\vfill\eject
+\bar\input dtp
+\bar\input courses
+\bar\input gut
+\bar\input amiga
+\bar\input didot
+\enddoublecolumns
+\bye
+
+book review: tex for the impatient
+book review: sue brooks
+schrod's TeX system
+michael's
+explanation?
+editorial?
+\vfill
+\centerline{%
+\scaledpicture 14.3pc by 11.1pc (leo scaled 1200)}
+\eject
+
+\scaledpicture 31.6pc by 19.7pc (lamb scaled 500)
+\scaledpicture 31.6pc by 19.7pc (lamb scaled 600)
+\scaledpicture 31.6pc by 19.7pc (lamb scaled 700)
+\line{\hfil\scaledpicture 17.9pc by 19pc (t scaled
+800)\hfil}
+\scaledpicture 31.6pc by 19.7pc (lamb scaled 500)
+
+
+\scaledpicture 17.5pc by 17.6pc (e scaled 800)
+
+\scaledpicture 14.3pc by 11.1pc (leo scaled 1200)
+
+\scaledpicture 17.6pc by 17.8pc (x scaled 800)
+
+\enddoublecolumns
+
+\centerline{\scaledpicture 46.7pc by 46.5pc (leonardo
+scaled 400)}
diff --git a/info/digests/texline/no13/13b b/info/digests/texline/no13/13b
new file mode 100644
index 0000000000..e47930e703
--- /dev/null
+++ b/info/digests/texline/no13/13b
@@ -0,0 +1,30 @@
+\input texline
+\voffset-0.5in
+%\def\firstpage#1{\bgroup\advance\vsize by0.5in\voffset-0.5in
+%\bigcolheight=\vsize
+%\advance\bigcolheight by\bigcolheight
+%\advance\bigcolheight by 10pt
+%\pageheight=\vsize
+%\input texline.head
+\pageno=25
+\begindoublecolumns
+\bar\input lamstex
+\bar
+\scaledpicture 31.6pc by 19.7pc (lamb scaled 450)
+\bar\input angus
+\bar\input vegas
+\bar\input another
+\bar\input uktexug
+\bar\input dedham
+\bar\input good_guys_plus
+\bar\input toc
+\enddoublecolumns
+\vfill\eject
+
+\input obit
+\vskip0pt plus1filll
+\noindent \sf This edition of {\sl\TeXline} was made
+possible by funding from \TeX cel AS, Gaustadall\'een~21,
+0371~Oslo~3, Norway, suppliers of the Publisher in Europe.
+Thanks Bruce.
+ \end
diff --git a/info/digests/texline/no13/amiga b/info/digests/texline/no13/amiga
new file mode 100644
index 0000000000..c058c1eeaa
--- /dev/null
+++ b/info/digests/texline/no13/amiga
@@ -0,0 +1,46 @@
+\title{Industrial Light and Magic}
+\vskip-3pt
+\centerline{\sl based on a press release}
+\noindent
+Amiga\TeX{} has a long history of firsts. Available since mid-1986,
+\TeX{} on the Commodore Amiga, written by Tom Rokicki, was the first to use
+scalable font technology to provide the best possible output on any printer. It
+was the first typesetting program to allow interprocess communication with other
+applications through ARexx. And now, Amiga\TeX{} is the first publishing
+program on the Amiga to support fully arbitrary \PS\ fonts and graphics
+on-screen.
+
+Amiga\TeX{} users can choose from thousands of \PS\ Type~3 and hinted Type~1
+fonts. The fonts can be scaled, slanted, and stretched. \PS\ fonts will be
+rendered automatically for screen display or any printer as needed. \PS\
+graphics from a wide variety of sources -- including virtually all structured
+drawing packages on the Amiga and other machines -- can be easily scaled and
+integrated into Amiga\TeX{} documents. The graphics will appear on the screen
+exactly as they will on a printer, within the limits of the screen resolution.
+
+Widely recognized as the best \TeX{} implementation available for any
+computer, Amiga\TeX{} is fully compatible with the latest \TeX{} 3.1 and \MF{}
+2.7 standards, and fully supports virtual fonts in the previewer and all device
+drivers. The multitasking and interprocess communication capabilities of the
+Amiga provide concurrent formatting, printing,
+previewing, and editing, and all such communication can be controlled through
+ARexx.
+
+Amiga\TeX{} is a comprehensive typesetting system. Primary strengths of the
+software include equations and tables, long documents (there is no limit on
+document length except for the size of your hard disk), and the highest quality
+typesetting.
+
+
+The retail price of the new 3.1a release is \quid140.00, claimed to be lower
+than the cost of direct import. A free functional demonstration disk is
+available on written (not telephone!) request. For more information contact
+the exclusive UK and Eire distributors
+
+{\obeylines
+Industrial Might and Logic
+58 Cobden Road
+Brighton BN2 2TJ}
+
+\noindent
+or call Paul Ockenden on (0273) 621393.\noauthor
diff --git a/info/digests/texline/no13/angus.tex b/info/digests/texline/no13/angus.tex
new file mode 100644
index 0000000000..2eafe236ac
--- /dev/null
+++ b/info/digests/texline/no13/angus.tex
@@ -0,0 +1,473 @@
+
+\begingroup\let\ref\relax
+
+\let\bfsl\sl%\newcommand{\bfsl}{\series{bx}\sl}
+\def\ritem[#1]{\par\hangindent\parindent{\noindent\bf #1}\enspace}
+\def\SliTeXb{{\bf S{\scb LI}\TeX}}
+
+\title{A Script for building true-sized fonts}
+This article is about creating John~Sauter's reworking of the Computer Modern
+fonts (see `How well do you know your CM fonts?' by Sebastian Rahtz,
+in \TeXline~9). We have been using Sauter's CM fonts in the Computer Science
+Department at Edinburgh University for over a year now, mainly in conjunction
+with \LaTeX{} (built on top of \TeX~2.97, and latterly \TeX~2.991 and
+\TeX~3.0).
+
+The process of getting \LaTeX{} to work with Sauter's fonts was
+rather tedious, involving editing {\tt lfonts.tex}, using \MF{} to create
+{\tt gf} (Generic Font) format and {\tfm} (\TeX{} Font Metric) files,
+converting the {\tt gf} files to the {\pk} (Packed Font) format used by our
+printer driver, and building new format files for \LaTeX{} on each
+architecture which we support (with the latest version of the {\tt web2c}
+system for building \TeX, format files which do not contain |glue_ratio|
+quantities may be shared across architectures; this includes plain \TeX\ and
+\LaTeX\ formats. This article will concentrate on a {\unix} shell script to
+assist with the second and third steps outlined above, but first I~will
+present some background.
+
+\section{Background}
+I~decided to update our installation to \TeX~3, and aquire a
+more recent version of \LaTeX{} than the one we were using. After a little bit
+of investigation, I also decided to install Mittelbach and Sch\"opf's new font
+selection scheme for \LaTeX{} (see Tugboat~10 no.1). This new scheme
+provides a more flexible interface to fonts, allowing users to alter the {\em
+family\/}, {\em series\/}, {\em shape\/}, and {\em size} of fonts
+independently. Thus typing |\sl| while boldface is selected will choose
+a{\bfsl slanted boldface\/} font if possible. There are also advantages in font
+management, making it far easier to install new fonts (especially fonts which
+are used in math mode), or change regular \LaTeX{} fonts for other fonts.
+
+The Computer Science Department at Edinburgh has a large number
+of theoreticians, who like to use as many wierd symbols as they can, so I~took
+advantage of the new font selection scheme to install the AMS
+(American Mathematical Society) math symbol fonts {\tt msxm} and {\tt msym} as
+new math alphabets (I~have recently updated these to the new {\tt
+msam} and {\tt msbm} fonts). The size of symbols is set by the normal
+\LaTeX{} size-changing commands.
+
+The department runs a network consisting of mainly Sun~3 and Sun~4
+workstations, with a few other machines (Hewlett-Packard workstations and DEC
+{\sc mips} workstations) connected. There are currently seven remotely
+accessable laser printers, most of which are 300\,\dpi, one of which is
+400\,\dpi, and another which is switchable between 300 and 400\,\dpi. This
+requires maintaining two complete sets of fonts, taking twice the disc space.
+We also keep fonts at magnification 700 ($0.7$ normal size) for printing
+two-up. We wanted a usable number of fonts without being constrained too
+much, and without taking too much disc space.
+
+\section{Font Requirements}
+The new \LaTeX{} font selection scheme makes it much easier to access
+fonts, so I~also decided to re-examine the fonts available, and build a
+new set of fonts for use with it. I~categorised the Computer Modern
+and other fonts which we have available into four groups:
+
+\ritem[Text fonts] These are fonts which would probably be used in normal text.
+\ritem[Math fonts] These are fonts which are normally accessed within math
+mode.
+\ritem[Special fonts] These fonts are usually explicitly loaded, and are not
+required in a large range of sizes.
+\ritem[\SliTeXb{} fonts] These are the extra fonts required to run \SliTeX{}
+with true-sized fonts.
+
+\noindent
+Table~1 shows the sizes chosen for the first group of
+fonts. Note that the fonts {\tt cmr}, {\tt cmss} and {\tt cmtt}
+appear in all sizes from 5 to 25 points; these fonts correspond to the normal
+series and shape of the font families defined by Mittelbach and Sch\"opf. When
+a family\slash series\slash shape\slash size combination cannot be found, the
+medium series and normal series and shape is substituted instead. The fonts
+{\tt cmbx} and {\tt cmti} also appear in the full range of point sizes
+because of their use in chapter and section headings. The sizes of the other
+text fonts corresponds to the range |\footnotesize| in \LaTeX's 10~point
+styles to |\Large| in 12~point styles. I~felt that this would be a large
+enough range to satisfy most users, without taking up too much disc space.
+
+\topinsert
+\hsize6.5in
+\raggedright\parindent0pt
+
+\setbox0\vtop{%
+\halign{\vtop{\hsize1.5in\strut#\strut}&\vtop{\hsize1.5in\strut#\strut}\cr
+\multispan2{\hfill\bf\strut Table 1: Sizes of `Text' fonts available\hfill}\cr
+\noalign{\smallskip}
+\noalign{\hrule}
+Font & Sizes available\cr
+\noalign{\hrule}
+cmbx, cmr, cmss, cmti, cmtt & 5, 6, 7, 8, 9, 10, 11, 12, 14, 17, 20, 25\cr
+\noalign{\hrule}
+cmb, cmbxsl, cmbxti, cmcsc, cmitt, cmsl, cmssbx,
+cmssdc, cmssi, cmtcsc, cmu, cmvtt & 8, 9, 10, 11, 12, 14, 17\cr
+\noalign{\hrule}
+}}
+
+\setbox1\vtop{%
+\halign{\vtop{\hsize1.5in\strut#\strut}&\vtop{\hsize1.5in\strut#\strut}\cr
+\multispan2{\hfill\bf\strut Table 2: Sizes of `Math' fonts available\hfill}\cr
+\noalign{\smallskip}
+\noalign{\hrule}
+Font & Sizes available\cr
+\noalign{\hrule}
+cmmi, cmsy, lasy & 5, 6, 7, 8, 9, 10, 11, 12, 14, 17, 20, 25\cr
+\noalign{\hrule}
+cmbsy, cmmib, lasyb & 5, 6, 7, 8, 9, 10, 11, 12, 14, 17\cr
+\noalign{\hrule}
+}}
+
+\line{\box0\hfill\box1}\bigskip
+\hrule height1pt depth1pt
+\bigskip
+\endinsert
+
+
+Table~2 gives the sizes in which the fonts used in math mode
+were made available. These fonts will probably be used in sub-scripts,
+super-scripts, and sub-sub-~(super-super)~scripts, so the sizes down to
+|\scriptscriptsize| in 10~point styles were built.
+
+
+
+
+\setbox0\vbox{\raggedright\parindent0pt
+\halign{\vbox{\hsize1.5in\strut#\strut}&\vtop{\hsize1.5in\strut#\strut}\cr
+\noalign{\hrule}
+Font & Sizes available\cr
+\noalign{\hrule}
+cmdunh, cmex cmff, cmfi, cmph, cmphi, cmtex,
+lcircle, lcirclew, line, linew, logo, logobf, logosl, manfnt & 10\cr
+\noalign{\hrule}
+cmfib, cmssq, cmssqi & 8, 10\cr
+\noalign{\hrule}
+cminch & 72.27\cr
+\noalign{\hrule}
+\noalign{\smallskip}
+\multispan2{\hfill\bf\strut Table 3: Sizes of `Special' fonts available\hfill}\cr
+}}
+
+Table~3 shows the sizes at which the special fonts were
+built. These fonts include some which are required for \LaTeX{} (for example,
+{\tt cmex}, {\tt lcircle}, and {\tt line}), some interesting variants on
+Computer Modern, and a few miscellaneous fonts.
+\smallskip
+\line{\box0}
+\bigskip
+\section{The {\ttit make\_font} script}
+The |make_font| script described here was written for the C-shell. It is
+used in conjunction with John Sauter's parameterised Computer Modern fonts,
+available from the Aston archive in the directory
+|[tex-archive.fonts.sauter]|. It is loosely based on several of
+the shell scripts in that directory, but I~believe it is easier to use.
+|make_font| creates a single font at several sizes, converts
+the resulting {\tt gf} files to {\tt pk} files, and moves them to an
+appropriate directory. The font organisation which we use in the
+department keeps all of the fonts for each resolution in a directory called
+{\tt /usr/local/share/tex/fonts/pk/}{\it device}{\tt/dpi}{\it res}, where {\it
+device\/} is the device for which the fonts are to be used, and {\it res\/} is
+the resolution of the fonts, in dots per inch. The fonts in these directories
+are named {\it font}{\tt.pk}; the resolution is not part of the font
+name. Only {\tt pk} fonts are used in the department. The {\tt make\_font}
+script was written for this convention, but could easily be converted to other
+conventions. Errors are logged on the standard output stream.
+
+\setbox1\vtop{\raggedright\parindent0pt
+\halign{\strut#\hfil &\hfil#\,\dpi\hfil&\quad\hfil#\quad&\hfil#\quad\cr
+Device &\omit\hfil Resolution\hfil &\omit\quad\hfil
+Magnification\hfil&\omit\hfil Size Kbytes\cr \noalign{\hrule}
+Agfa&400&1000&2863\cr
+Agfa&280&700&1990\cr
+Canon&300&1000&2310\cr
+Canon&210&700&1567\cr
+\noalign{\hrule}
+\noalign{\smallskip}
+\multispan4{\hfill\bf\strut Table 4: Directory sizes
+for true-sized fonts\hfill}\cr}}
+
+
+To build a true sized font, we create a driver file which sets the
+design size of the font to be created, and then inputs Sauter's parameterised
+version of the font (from the file {\tt build\_}{\it font}{\tt.mf}).
+A typical invocation of |make_font| would be:
+
+{\let\tt\smalltt\baselineskip9pt
+\begintt
+make_font lw canon 1000 cmb 8 9 10 11 12 14 17
+\endtt
+}
+
+This command would build the font {\tt cmb} in sizes 8--17 points.
+|make_font| should be run from the directory which contains the
+parameterised {\tt mf} files.
+
+The first three parameters required by |make_font| are the name of the
+\MF{} |mode_def| to be used when building the font, the name of the
+{\em device\/} sub-directory to place the {\tt pk} files in, and the
+magnification of the font.
+An optional switch can be used to set the command name under which \MF{}
+is invoked.
+
+{\let\tt\smalltt\baselineskip9pt\parindent0pt
+\begintt
+#|iteight beginning of script|tt
+#! /bin/csh -f
+# Make a font, at the specified sizes.
+# make_font mode pkdir mag font size...
+
+# MF name parameter;
+# assume cmbase preloaded otherwise.
+if ($#argv != 0 && $argv[1] =~ -*) then
+ set meta=`echo $argv[1] | cut -c2-`; shift
+else
+ set meta=cmmf
+endif
+
+if ($#argv == 0) then
+ echo "No mode name"; exit 1
+else
+ set mode=$1; shift
+endif
+
+if ($#argv == 0) then
+ echo "No pk directory"; exit 1
+else
+ set pkdir=./pk/$1; shift
+endif
+\endtt
+\begintt
+if ($#argv == 0) then
+ echo "No magnification"; exit 1
+else
+ set mag="$1"; shift
+endif
+if ($#argv == 0) then
+ echo "No font"; exit 1
+else
+ set font=$1; shift
+endif
+\endtt
+}
+
+
+
+Note that the magnification can also be given in terms of {\it magsteps\/}.
+The command to build {\tt cmr} in 10-point, magnified $1.2$ times would be:
+
+{\let\tt\smalltt\baselineskip9pt
+\begintt
+make_font lw canon "magstep1*1000" cmr 10
+\endtt
+}
+
+The names of the directories in which the {\tt tfm} files and \MF{} driver
+files go are then set up, and directories created if necessary. The name of
+the default \MF{} inputs directory (the last line of this next section) may
+need changing:
+
+%script
+{\let\tt\smalltt\baselineskip9pt\parindent0pt
+\begintt
+#|iteight continuation of script|tt
+# directories for created font files
+set tfmdir=./tfm
+set mfdir=./mf
+set gftopk=gftopk
+
+if (! -d $pkdir) mkdir $pkdir
+if (! -d $tfmdir) mkdir $tfmdir
+if (! -d $mfdir) mkdir $mfdir
+
+# Include the standard Computer Modern files,
+# like roman.mf, romanu.mf, etc.
+setenv MFINPUTS \
+ .:${mfdir}:/usr/local/share/tex/fonts/mf
+\endtt
+}
+
+The next parameter required by the script is the name of the font to
+be created. This is followed by a list of sizes in which the font is to
+be built. The script iterates over the sizes available, creating driver files
+if there is a parameterised version of the font available. If there is not a
+parameterised version of the font available, the script assumes that the font
+is available anyway, and that the name of the file in which it is found is the
+name of the font and the size concatenated together. There is one special
+case to worry about though; some fonts do not have size information in their
+names (for example {\tt manfnt} or {\tt cminch}); these fonts can be built by
+putting a single empty string instead of the list of sizes. For example:
+
+{\let\tt\smalltt\baselineskip9pt
+\begintt
+make_font lw canon 1000 cminch ""
+\endtt
+}
+
+This command will build the font {\tt cminch}, if the driver file
+{\tt cminch.mf} exists in any of the \MF{} input directories.
+
+%script
+{\let\tt\smalltt\baselineskip9pt\parindent0pt
+\begintt
+#|iteight continuation of script|tt
+echo "Creating $font $argv @ mag $mag"
+
+# iterate over sizes
+while ($#argv > 0)
+ set size=$argv[1]; shift argv
+ set file=$font$size
+ set mffile=$mfdir/$file.mf
+\endtt
+\begintt
+ # build mf file if build procedure present
+ # otherwise assume mf file is already built
+ if (! -e $mffile && -f "build_$font.mf") then
+ echo "...creating $mffile"
+ echo "% $size-point $font." > $mffile
+ echo "design_size := $size;" >> $mffile
+ echo "input build_$font;" >> $mffile
+ endif
+\endtt
+}
+
+|make_font| then calls \MF{}, sets the mode and magnification, and
+inputs the driver file.
+The {\tt batchmode} command prevents \MF{} from stopping if it detects an
+error; the error is written to a log file and processing continues.
+
+{\let\tt\smalltt\baselineskip9pt\parindent0pt
+\begintt
+#|iteight continuation of script|tt
+$meta "\batchmode;mode:=$mode;mag:=$mag/1000;input $file"
+\endtt
+}
+
+The next line looks at the last line of the log file produced by \MF{} to
+determine what the resolution and filename of the generated {\tt gf} font was.
+If the \MF{} run was successful, the last line of the log file will contain a
+line similar to:
+
+{\let\tt\smalltt\baselineskip9pt
+\begintt
+Output written on manfnt.210gf
+ (122 characters, 13588 bytes).
+\endtt
+}
+
+The {\tt sed} expression on this line extracts the filename and resolution from
+this line, storing them in the variable {\tt log}. (Relying on \MF{} putting
+this information on the last line of the log is not a good idea; the actual
+version of |make_font| I use is identical to the one here, except that it
+has the search pattern
+|/^Output *written *on *[^.]*\.[0-9]*gf/| in place of |$|.)
+
+{\let\tt\smalltt\baselineskip9pt\parindent0pt
+\begintt
+#|iteight continuation of script|tt
+set log=`sed -n \
+ '$s/.*on *\([^.]*\)\.\([0-9]*\)gf.*$/\1 \2/p' \
+ $file.log`
+\endtt
+}
+
+The script now checks whether the filename and resolution were found
+correctly. If they were, the {\tt gf} file is converted to a {\tt pk} file
+and stored in an appropriate directory, the {\tt tfm} file is moved to an
+appropriate directory, and any leftover files are cleaned up. If the
+name and resolution were not found, the log file is printed to the standard
+output, and leftover files are cleaned up.
+
+{\let\tt\smalltt\baselineskip9pt\parindent0pt
+\begintt
+#|iteight continuation of script|tt
+if ($#log == 2) then
+ set out=$log[1];
+ set dpi=$log[2]
+ if (! -d $pkdir/dpi$dpi) mkdir $pkdir/dpi$dpi
+ echo "$out.${dpi}gf converted to $pkdir/dpi$dpi/$file.pk"
+ $gftopk $out.${dpi}gf $pkdir/dpi$dpi/$file.pk
+ /bin/mv -f $out.tfm $tfmdir
+ /bin/rm -f $out.${dpi}gf $file.log $out.tfm
+else
+ echo "Problem; $file.log ="
+ cat $file.log
+ /bin/rm -f $file.log $file.tfm
+endif
+end
+\endtt
+}
+
+\section{Driving the {\ttit make\_font} script}
+The |make_font| script is usually driven by another C-shell script, which
+builds all of the fonts required at one mode and magnification. This script
+contains commands similar to the |make_font| commands shown above, but
+parameterised on the \MF{} mode name, {\tt pk} directory name, and
+magnification:
+
+%script
+{\let\tt\smalltt\baselineskip9pt\parindent0pt
+\begintt
+# ... set up parameters $mode, $pk and $mag
+#
+# TeX/LaTeX "math" fonts
+#
+make_font $mode $pk "$mag" cmbsy
+ 5 6 7 8 9 10 11 12 14 17
+make_font $mode $pk "$mag" cmmi
+ 5 6 7 8 9 10 11 12 14 17 20 25
+make_font $mode $pk "$mag" cmmib
+ 5 6 7 8 9 10 11 12 14 17
+# ... etc.
+make_font -logomf $mode $pk "$mag"
+ logobf 10
+make_font -logomf $mode $pk "$mag"
+ logosl 10
+make_font -mf $mode $pk "$mag" manfnt ""
+\endtt
+}
+
+The command name switch is used to select versions of \MF{} with different
+bases preloaded for the {\tt logo} and {\tt manfnt} fonts. Note that the
+magnification parameter is quoted; if you use magnifications similar to
+the |"magstep1*1000"| example above, this is required to prevent the
+C-shell expanding the {\tt *}.
+
+\section{Conclusion}
+After you have built your true-sized font, what then? To get \LaTeX{} to work
+with these fonts involves editing {\tt lfonts.tex} (or, if you are using
+Mittelbach and Sch\"opf's font selection scheme, {\tt fontdef.tex}), and
+replacing all of the magnified fonts with true-sized fonts. You then need to
+regenerate the \LaTeX{} formats with the new fonts (by running \IniTeX). I
+have found it useful to keep a copy of the original format around to allow
+users to create {\tt dvi} files which can (probably) be printed at other
+installations, but as this precludes deleting the old scaled fonts, it might
+not be feasible for everybody.
+
+\smallskip
+\line{\box1}
+\smallskip
+
+The script presented here has made the job of building new fonts from John
+Sauter's parameterised Computer Modern quicker. Table~4
+shows the sizes of the font directories created for our installation. The
+canon directory at
+300\,\dpi\ also contains the {\tt msym} and {\tt msxm} symbol fonts among
+others, so the directory size is a little inflated.
+
+\endgroup
+\enddoublecolumns
+\vfill\eject
+\begindoublecolumns
+I have not yet had time to find out if the set of sizes and fonts presented
+here is sufficient, but I will report back to \TeXline\ about further
+developments.
+I have recently changed our \dvi\ to \PS\ converter to Tom Rokicki's {\tt
+dvips}. This program comes with a shell script ({\tt MakeTeXPK)} which is
+used to create fonts which are not available. I have now modified the {\tt
+MakeTeXPK} script so that it can create true-sized fonts on demand. The {\tt
+makefont} script described here is still useful for creating large batches
+of fonts.
+One unresolved issue which needs further investigation involves the fonts
+required for photo-reduction. When the true-sized fonts are reduced from A4 to
+A5 they look poor, due to fine lines disappearing. Possible solutions to this
+problem include using different |mode_def|s to improve reduction quality,
+or building a restricted set of fonts at a larger magnification.
+\author{Angus Duggan}
+
+
+\endinput
diff --git a/info/digests/texline/no13/another b/info/digests/texline/no13/another
new file mode 100644
index 0000000000..4f2a91c9ec
--- /dev/null
+++ b/info/digests/texline/no13/another
@@ -0,0 +1,80 @@
+\title{Another Book Review}
+{\sl \TeX\ for the Impatient}. Paul W Abrahams with Karl Berry \& Kathryn A
+Hargreaves. Published by Addison Wesley, Reading, Mass.,
+1990. ISBN 0-201-51375-7. \smallskip
+\noindent
+Let's start with the easy bit: this is not a teaching
+text for the impatient. It is for those who find that
+locating something in the \TB\ can be quite a lengthy
+process. So it is a sort of \TB\ companion. Something to
+sit alongside `the book', but no wise to replace it.
+There will be those who will use it instead of `the
+book'. It isn't nearly as amusing. So those who don't
+enjoy \DeK's wit may relax a little with this volume. It
+deliberately restricts itself to {\tt plain}, and offers
+no solace or comfort to \AmSTeX\ or \LaTeX\ users.
+
+It is a sort of overgrown glossary, where \TeX\ concepts
+and commands are described and illustrated. In general
+their explanations are straightforward, and they are
+prepared to extend their descriptions to cover less
+obvious \TeX\ behaviour (for example, see the discussion
+on category codes). There is a useful chapter on `Tips
+and Techniques' which, among other things discusses ways
+of correcting `bad' page breaks, line breaks, and so on. I
+was slightly surprised that there seem to be no criteria
+proposed to describe what might be a `bad' break, or even
+more important, what comprised a good one. The
+typographic content of this book is low. No advice is
+given to dissuade the novice from those dreadful values
+of |\hsize| with 10 point fonts -- perhaps the most
+fundamental reason that \TeX\ often acquires a bad
+typographic reputation.
+
+There is a `Compendium of Useful Macros' which are
+indeed useful. But why are they there? I appreciate that
+they serve a similar role to the {\tt manmac} macros, but
+they seem odd in a reference book. I wouldn't use the one
+they give for the \LaTeX\ logo. Besides anything else, they
+omit the backslash before the {\tt TeX}. And curiouser and
+curiouser, instead of using |\TeX| in the body of the
+\BibTeX\ macro, they expand it to its kerns and boxes. But
+this is nit picking. They provide a set of commands to
+ease cross referencing -- one of the most significant
+omissions of {\tt plain} \TeX. They also give some macros
+for table construction: since |\halign| is so easy to use,
+I can't see the point myself, but\dots\
+
+So far, I've actually found this book useful, although I'm
+not yet familiar enough with their division of commands
+into various sections. I agree that it is difficult to
+classify the whole range of \TeX\ commands, and any such
+classification must be imperfect. But by including a
+`Capsule summary of Commands', as well as an adequate
+index (with only two types of entry, unlike the \TB's more
+confusing three), they cover most options, and I can
+generally find something useful and appropriate.
+
+This is a reference book, not a book to be read cover to
+cover, recursively. That rather brings into question the
+illustrations: why are they there? Tenniel's illustrations
+to {\sl Alice}, on which these are based, are among my
+favourites. It is clearly appropriate to associate \TeX\
+and {\sl Alice}. There are so many parallels. But why
+redraw them at all? I would have been inclined to use
+the originals, even allowing for the lack of continuity of
+using the impatient (white) rabbit as a theme.
+
+Do note that there is an unfortunate sequence of
+misprints, where a number of chapters have the `true'
+characters |{|, |}| and |_| transposed to other
+characters, but only in some headings. This is not as
+disasterous as it at first sounds. If you are using this
+book for reference, you will hardly notice, after the
+first few seconds of puzzlement. Karl Berry assures me
+this has been corrected for a subsequent
+printing. A useful addition to the \TeX\
+library, although apparently ignorant of
+contributions outside the canonical trio of
+Knuth, Lamport and Spivak.\author{Malcolm Clark}
+
diff --git a/info/digests/texline/no13/bcs-future b/info/digests/texline/no13/bcs-future
new file mode 100644
index 0000000000..447ae08a34
--- /dev/null
+++ b/info/digests/texline/no13/bcs-future
@@ -0,0 +1,29 @@
+\title{Future Meetings }\vskip-3pt
+\centerline{\bf of the BCS ep Group}\noindent
+The next meeting of the BCS Electronic Publishing Specialist Group will be on `Typefaces' and will be held at the St
+Bride Institute, off Fleet Street on 15 October. Details have not
+yet been finalised, but the following list of topics has been
+produced and it is planned that speakers will cover many of them:
+Font design;
+Truetype; Multiple mastering; Windows and fonts; the Bodoni
+bicentennial; Grey-scale fonts; Legal aspects; Hinting;
+Non-European glyphs; Kerning; Typefaces for DTP.
+The full programme and booking form will be distributed in early
+September.
+
+A survey of interests conducted by the EP group indicated that a meeting on
+Graphic User Interfaces would be even more popular than one on fonts.
+A meeting on this topic will be held on 5th December
+at the SUN Microsystems office in the City. More information will made
+available real soon.
+
+The first meeting of 1992 will also be in London, again at a venue
+to be confirmed, and will probably cover topics related to
+structured documentation and text management. More details in due
+course.
+
+Finally, there will be a conference in 1992. It is hoped that this will
+take place in Scotland, but planning is still at an early stage.
+More information will be sent out to group members as soon as it is
+available. If you are not already a member of the group, contact David
+Penfold for information.\noauthor
diff --git a/info/digests/texline/no13/betsy b/info/digests/texline/no13/betsy
new file mode 100644
index 0000000000..47e85aff1e
--- /dev/null
+++ b/info/digests/texline/no13/betsy
@@ -0,0 +1,47 @@
+\title{Sunny Mexico}
+A report on my \TeX\ activities in Mexico and maybe a few personal too.
+(The temperature is in the 70's --
+the air is very polluted --
+People are very charming and hospitable, and there are about 20
+million just in Mexico City.
+No one has heard of \SGML\ or CALS\dots).
+
+
+Arturo Sanchez invited me to speak at the \TeX\
+meeting in Mexico City in February 1991. A diligent host
+he organised my sightseeing, including visiting the Pyramids
+of the Sun and the Moon, built in the 6th and 7th Century.
+Real old.
+
+Did you know that {\sc the car} of Mexico is the VW Bug? There are $1+$
+million manufactured there yearly, and nearly all the taxis are
+Bugs\dots
+
+Friday was the \TeX\ user meeting held at the University, near the
+Olympic Stadium from 1968\dots
+
+About 60 people attended and the program was all in Spanish with the
+exception of my presentation. There were 4 speakers and one of the
+people before me spoke on some of the same things that I had planned, so
+it took some quick adjusting on my part.
+
+Anyway, this was a friendly crowd and very receptive. They are using
+PC \TeX\ 2.1, and have never heard of HiJaak, didn't know much about
+\TeX\ 3.0/virtual fonts, so it was quite interesting for them to hear
+about all our (ArborText) offerings. There is an Addison Wesley office there
+and 3 people were present. They ordered an upgrade on the spot (they brought
+their old version). Of all those present, all had PC's except 2 who had
+Suns. There is much interest in a `Windows' version. In
+case you are wondering, they all understood English so I
+did not have to have a translator.
+
+After a coffee break, they had a roundtable discussion in Spanish about
+various projects, problems, etc., to which I listened and understood about
+1/4. I went to dinner with the conference committee at the University
+Club. A newly developing market, a little behind ours.
+
+I have only seen one little tabloid English
+language newspaper and no TV or radio in English except a
+movie channel, so I truly feel that I have been {\sc away}.
+\author{Betsy Dale}
+
diff --git a/info/digests/texline/no13/book-reviews b/info/digests/texline/no13/book-reviews
new file mode 100644
index 0000000000..cc732c84d0
--- /dev/null
+++ b/info/digests/texline/no13/book-reviews
@@ -0,0 +1,303 @@
+\title{Book Reviews}
+{\sl \TeX\ Applications, Uses, Methods}. Edited by Malcolm Clark. Published
+by Ellis Horwood, Chichester, 1990. ISBN 0-13-912296-6.
+\smallskip
+\noindent
+This is the Proceedings of \TeX88, held at the University of Exeter. At least,
+it is as much of the proceedings as the editor and conference organiser,
+Malcolm Clark, was able to obtain; certainly all papers are represented by at
+least an abstract and the paper by three Polish authors, who were not able to
+be at the conference, is included.
+
+As one would expect, many of the papers are directed at matters of interest
+to those who use \TeX{} and that is not to devalue them in any sense.
+That \TeX{} is a very powerful typesetting language is known to anyone
+with an interest in this field and the new effects which people achieve
+never cease to amaze. However, fascinating as these matters
+are, I found other parts of the book even more interesting. The first three
+chapters provide an introduction to \TeX{} and a critique of where \TeX{}
+stands today (or at least stood three years ago). Anyone who wants to understand
+what \TeX{} is about and discover
+where \TeX{} stands {\it vis a vis} DTP systems should read these
+chapters. And they contain material which is not just true of \TeX{}.
+Hoenig in chapter~1 uses as his example theorem: `There is no royal
+road to typesetting. Typesetting is an inherently difficult and
+time consuming occupation', while Noble and Ganz in chapter~2
+suggest that `Authors and good design -- are they compatible?'
+would make a good paper title. These are both aspects which are
+often overlooked when DTP and related areas are discussed. The
+third chapter, {\sl Whither \TeX?}, examining the present role and
+future of \TeX\ was co-authored by Cathy Booth.\looseness-1
+
+There are other papers in the book which are of interest to more than
+just `\TeX{}ies'. Sadly the paper on the work at St\"urtz
+on \TeX{} output in Monotype fonts and that on CUP's implementation
+of this in the UK are only present as abstracts, as is Francis
+Cave's paper on the notation and structure of mathematical texts.
+However, the paper by Tony Norris and A L Oakley on the production
+of chemical formulae is present in full and makes interesting
+reading for those working in that area, with some general comments
+about preprocessors in general (the {\sans troff} rather than the
+(\La)\TeX{} approach).
+
+In summary, this book provides not only a fairly brief, but good,
+introduction to what \TeX{} is, but it also gives a good cross-section of
+applications, together with some broader papers, as mentioned.
+
+Finally, it should be noted that Cathy Booth was not only a contributor to
+these proceedings but also local organiser of the Conference. Although the
+book was published some time before Cathy died, it can in many ways be
+considered as a tribute to much of the work she did both before and after
+she became ill. I am sure that Malcolm would be happy to view it in that
+way.\author{David Penfold}
+
+
+\bigskip
+\noindent
+{\sl Desktop Publishing}. By Kirty Wilson-Davies, Joseph St.~John Bate and
+Michael Barnard; 4th edition revised by Ron Strutt. Published by
+Blueprint, London, in their Publisher's Guide Series, 1991. ISBN 0-948905-61-1.
+\smallskip\noindent
+{\sl Collier's Rules for Desktop Design and Typography}. By David Collier.
+Published by Addison-Wesley, Wokingham, 1991. ISBN 0-201-54416-4.
+\smallskip\noindent
+{\sl Typefaces for Desktop Publishing -- A User Guide}. By Alison Black.
+Published by Architecture Design and Technology Press, London, 1990. ISBN
+1-85454-842-7.
+\smallskip\noindent
+{\sl The Writer's Guide to Desktop Publishing}. By Kathy Lang. Published by
+Academic Press, London, 1987. ISBN 0-12-436275-3.
+\smallskip
+\noindent
+A glance at the titles of these four books would seem to indicate that they
+all cover the same ground and are aimed at the same market. More detailed
+perusal indicates that this is not the case. They are, in fact, all aimed
+at different readers, although there will be some overlap.
+
+{\sl Desktop Publishing\/}, revised by Ron Strutt, is one of a series of
+guides aimed at publishers and is an introduction to the world of DTP,
+starting from a background of typesetting and publishing. As such, it is a
+very good introduction. It is perhaps a pity that the first two illustrations
+in chapter~1 do DTP very little justice, the first being a comparison of
+typeset and laserprinter output, not at the original size but enlarged,
+although the text does not say from what, while the second compares a
+conventionally produced half-tone with a LaserWriter version, which is
+apparently not even screened. We all know that there are differences, but
+these comparisons are hardly fair and will tend to reinforce the prejudices
+of the traditional typesetter or publishing executive. That having been
+said, the book gives an excellent history and survey of DTP and its use in
+publishing. There is one important omission, however, which is that
+there is no mention at all of \TeX{}. While standard \TeX{} is not strictly DTP
+(i.e.~there is no screen manipulation), nor strictly speaking is Telos,
+which is mentioned, and to produce a book for publishers which does
+not even refer to \TeX{} in passing is an important oversight, particularly
+when almost all the major scientific and technical publishers are at least
+looking at \TeX{} and its implications.
+
+The book has a good index and a glossary which is fairly complete, except
+that CALS and RISC, for example, are used in the text without being defined
+either in the book (as far as I could find) or in the Glossary.
+
+I have to admit that the title {\sl Collier's Rules} immediately put me off
+the next book. Presumably it is modelled on {\sl Hart's Rules}, but I do
+not think that Hart himself called the latter by this name. The title has
+implications of hubris. If John Miles had called his book ({\sl Design for
+Desktop Publishing\/}, which is excellent and still available) {\sl Miles'
+Rules} (though I am sure he never would have), then people would have perhaps
+smiled, but accepted it because of his reputation. However, although I have
+heard of all the other authors of the books under review, I had not come across
+David Collier. But perhaps I am moving in
+the wrong world, because Erik Spiekermann has written a glowing Foreword
+to the book.
+
+{\sl Collier's Rules\/} is obviously for the graphic designer.
+ It starts with a chapter on Characters and builds up,
+through Words and Lines, Punctuation, Paragraphs, Illustrations and
+Graphics, to Page Layout. Each chapter starts with a few pages of
+descriptive text, followed by pages which I find difficult to read,
+although the information on them can be absorbed. The information itself
+is valuable, if not given equal prominence. For example, notes on negative
+leading are partly obscured by a graphic (a problem -- for me -- on many pages), while items such as the differences between hyphens and n- or m-dashes
+receive a disproportionate amount of room.
+
+It is interesting that Document Handling does not follow on from Page Layout but
+comes later (after Printing and Binding and Colour) and even then the documents
+considered are not books or journals. The information
+on colour takes up eight pages, which is surely not enough. Ron Strutt in
+his book says `It is a complex area and one which is not to be approached
+lightly'; Collier perhaps makes it look too easy, even though
+the text notes the difficulty.
+
+
+This is definitely a graphic designer's book and I am sure that the presentation
+will be acceptable to a graphic designer; whether it is good graphic design
+I am not sure, because some of the information gets lost.
+It is fun to look at, though difficult to read. It
+would be useful for someone starting graphic design, but is really too
+elementary for the practising graphic designer. It might make a useful
+reference book; it does have an index and a glossary, but the latter is not
+as complete as Ron Strutt's.
+
+If David Collier's book is aimed at the graphic designer, Alison Black's book
+is very definitely aimed at the book designer. It can be read from cover to
+cover or just used for reference; it includes much wisdom on choosing typefaces for specific
+purposes, with many examples. I enjoyed reading it and it would go very
+well with the book edited by William Foster and reviewed above.
+Part~1 deals with Criteria for Choosing Typefaces, Part~2 with
+Typeface Production, Reproduction and Multiplication, and Part~3 with
+The Technical Description of Typefaces. There is also a list of further
+reading which is fairly comprehensive, a listing of the sources of the
+illustrations, nearly all of which are from real publications,
+and a combined index and glossary, which in a book of this kind seems to
+work well.
+
+Although I enjoyed reading Alison Black's book, I did sometimes get lost,
+because the illustrations are placed in such a way that it is not always
+clear where the text continues. And on one other point we obviously
+disagree. An earlier issue of the BCS EP Newsletter is used as an example on
+page 45 and Alison says that `Hyphenation would also have helped, here, to
+give a smoother right-hand margin.' The text of the book is unjustified
+and hyphenated, so Alison practises what she preaches, although I
+personally find that there are too many hyphens -- but the book was
+produced using Quark Xpress, and not the latest version!
+In spite of these reservations, I would recommend the book to anyone who has
+to produce (and design) a publication, i.e.~a book or journal.
+
+Finally we come to Kathy Lang's book, which is
+directed very much at the author. For the novice it is really excellent,
+and not just for the novice, for with the `hypertext-like' approach of
+printing the abstract of each chapter in the table of contents, it is
+possible to enter the book at the point matching one's level of expertise.
+
+The book covers most (probably all) aspects of technical writing, including
+such areas as backing up material, electronic mail and organising
+information, quite apart from the more technical aspects of lay-out and
+DTP. The only real criticism one could make is that the book is beginning
+to show its age. I know Kathy is aware of that and, if this review can be
+used to encourage her and her publishers to produce a new edition, it will
+have served its purpose.
+
+In summary, Ron Strutt's book is a good introduction for those in the
+publishing and typesetting world, while Kathy Lang's, perhaps with reference
+to the Hertis book (see above) as well, is ideal for the writer approaching
+a computer for the first time (or even the second or third time). Alison
+Black's book is for anyone involved in book design, while David Collier's
+is definitely for the graphic designer.
+\author{David Penfold}
+\bigskip
+\noindent
+{\sl Typefaces for Desktop Publishing -- A User Guide}. By Alison Black.
+Published by Architecture Design and Technology Press, London, 1990. ISBN
+1-85454-842-7.
+\smallskip
+\noindent
+My usual concern when I find a contemporary book on
+typography is to see how \TeX\ fares. But first I have to
+note that the title of Alison Black's book is something
+of a misnomer. This is an excellent introduction to many
+of the practical aspects of document production. It is
+not particularly locked into typefaces, nor to deskstop
+publishing. It is though a User Guide. I suspect that the
+title was inherited from the original working party
+on desktop publishing which instigated the book. This
+working party included such \TeX\ luminaries as Catherine
+Griffin and Richard Southall. And if we read through the
+list of those thanked, we'll also find Paul Luna, Andrew
+Boag, Paul Stiff and Rachel Hewson: all typographically
+`sound' and \TeX\ aware. So we must expect a fair
+treatment.
+
+What we get is a rather matter of fact treatment. \TeX\
+and \MF\ are not presented as some highly specialist
+quirky excrescences, but as ordinary tools in the
+armoury of the user.
+
+It was however sad to note a reference to the
+`\TeX\ character set' as if Computer Modern was the only
+one which \TeX\ can use. A common enough misconception.
+
+\MF\ is used quite seriously in the text, in its role as
+a rasteriser -- one in which it has yet to be equalled.
+Black shows how the same character is rasterised at
+different resolutions. Reading carefully between the
+pixels (and referring to the Appendix `List of
+Illustrations') these are \MF\ generated (as are a number
+of the other illustrations).
+
+Unlike David Penfold, I don't think I ever got lost
+between illustrations and text. I found the design and
+layout a pleasure. Paul Stiff did an excellent job on
+this and I only hope my own book will find such an
+iconclastic and bold designer. The book is copiously
+illustrated, and all those illustrations benefit the
+text. In short, a good text, and I think I learned a lot.
+I hope I put it into practise. And thanks Alison for
+putting \TeXline\ in the `Further Reading' appendix.
+That's almost as good as pinning a used fiver to my
+review copy!
+\author{Malcolm Clark}
+
+\bigskip
+\goodbreak\noindent
+{\sl The Joy of \TeX, second ed.: a gourmet guide to
+typesetting with the \AmSTeX\ macro package}, M~D Spivak,
+PhD, American Mathematical Society, Providence, RI,
+1990, ISBN 0-8218-2997-1.
+
+\smallskip\noindent
+The review of the first edition of this book provided by
+Angela Barden in the proceedings of the Cork TUG
+conference (cf \TUGboat\ Volume 12, No.~1) encourages me
+to fly to the defense of Mike Spivak. To dismiss this
+book because it does not define `macro' astounds me. No
+doubt there are mathematicians (who else would want to
+use \AmSTeX?) who have yet to encounter the word `macro'.
+That Barden is no mathematician is confirmed by her
+difficulty of raising 2 to a power ranging from zero to
+3. Unless of course Ireland does indeed contain more than
+two sexes.
+
+But I shall assume that most potential users of this book
+have probably seen the first edition, and their first
+question will be `how different is it?'. There is not a
+great deal of difference between the two editions. The
+principal difference is a new appendix A {\sl The AMS
+Preprint Style}. Essentially this is the original
+chapter 7, expanded and transposed. There are 21
+additional pages, but this is partly a result of greater
+use of white space, rather than rewriting. My tally of
+changes includes the following: some extension to
+|\widehat| and |\widetilde|; some extra examples relating
+to |\xalignat| and |\xxalignat|; chapter~19 has some new
+or extended sections including details of the use of
+fonts in maths mode, the use of inserts with
+captions, new symbols, and vertical spacing. The sections
+on |\qed| and the use of the tab key with matrices are
+omitted. In case that worries you, |\qed| is still there,
+it has just changed its form.
+The appendix on bibliographies has been extended
+substantially.
+
+I confess that I thought that there would be
+substantially more change with the introduction of
+\AmSTeX\ 2. It all seems a bit cosmetic to me. I have no
+doubt that the macros themselves have become more robust
+and efficient. But really it could have been covered in a
+short appendix, rather than a new book. Note that this
+edition was not written by Spivak~MD~PhD, but by the AMS'
+Technical Support Group. And that rewrite was chiefly to
+expand chapter~7 and move it to appendix A. That movement
+itself has a fascinating and amusing consequence. Spivak,
+like Knuth, carefully manoevered his appendices so that
+the inital letter of each appendix title coincided with
+the alphabetic `number' of the appendix. Appendix A was
+originally `Answers to all the exercises'. It now becomes
+`The AMS Preprint Style': so far, so good. But what of
+`Bibliographies'? Sad to say, it now becomes Appendix C,
+not the anticipated B. It makes all the effort a bit
+futile. On the other hand, omitting Appendix \AA\ ensures
+that the solecism of placing it alphabetically between A
+and B is also omitted.\author{Malcolm Clark}
+
+
+\endinput
diff --git a/info/digests/texline/no13/cheltenham b/info/digests/texline/no13/cheltenham
new file mode 100644
index 0000000000..bdce4a880a
--- /dev/null
+++ b/info/digests/texline/no13/cheltenham
@@ -0,0 +1,81 @@
+\title{Cheltenham Effect}
+Cheltenham sounded an idyllic setting for a joint meeting of the
+BCS ep Group and the UK \TeX\ Users Group at the end of May, but
+lapping the town's one-way system in search of venue and parking place was
+not the perfect way to start the day. It did not take long to recover, however,
+the meeting being an interesting one, with a rather different approach and
+content to usual Group meetings.
+
+The theme was Cheltenham's emergence as a centre of many high-tech
+suppliers of equipment and services to the publishing industry. It was
+surprising to hear from the first speaker, Derek Kyte of Chelgraph, that
+this all came about by accident. Linotype, the catalyst of the Cheltenham
+Effect, had sent a team to investigate prospective sites in Wales. They
+stopped in Cheltenham on the return journey to report a lack of success to
+the Managing Director and during that meeting it was decided to set up in
+Cheltenham instead.
+
+There was no reason to rue the decision; Linotype's Cheltenham operation
+was successful, at one time employing 1100 people. The demise came when
+Linotype became part of a multi-national conglomerate and was acquired by
+Allied Chemicals, which then sought to rationalise operations by making 500
+R\&D people redundant at the Cheltenham site. This pool of talent was the
+source of many new companies, including Chelgraph, QED, Bitstream, Quorum,
+Chubb Instrumentation, Highwater Designs, Upfront, and Ntg2000.
+
+Linotype's workforce was cut back severely, but the company continues to
+make its mark internationally. Tony Lock described what the company is
+doing at Special Projects (Non-Latin Scripts). The Letraset DTP packages,
+ReadySetGo! and Design Studio, have been adapted to provide \PS\
+solutions for non-Latin scripts. This approach incidentally was first
+pursued by Diwan. Seven arabic and eleven Indian languages are now
+available with three more under development.
+
+Chris Jordan of Chelgraph compared the approach of successful companies in
+the early 1980s with the current trend. At one time leading companies tried
+to sell every type of product to everyone and marketed proprietary
+hardware. Standardisation and Open Systems have changed this. Now the most
+successful companies are those which concentrate on particular market
+niches.
+
+Tim Hawkins and Andy Thomason of Ntg2000 outlined their company's work. Ntg
+stands for `New Technology Group' and they have two market areas: newspaper
+editorial systems and software RIPs. The latter would have the advantage
+of being faster than presently available \PS\ RIPs. Ntg is a spin-off
+from LaserMaker, the Nottingham-based installer of editorial and page
+make-up systems.
+
+
+Andy Buxton of Highwater Designs explained that the company had been formed
+by personnel leaving Xenotron following its takeover by Hell (hence the
+name: Come Hell or\dots). Its main activities are in the graphics
+area, providing interfaces for Linotronic, PelBox and Ultra imagesetters.
+Compared to a purely DTP approach on the one hand and high-cost graphics
+packages on the other, Andy claimed that his company's products
+can offer both cost advantages and high-quality output.
+
+
+In contrast to these technical talks, Steven Blake of the Cheltenham Art
+Gallery and Museum gave a potted industrial history of the town. For
+several hundred years it had been a centre for small specialised
+industries. The present crop of high-tech companies continues this
+tradition.
+
+
+After a very good lunch visits were made to Linotype and Quorum, while
+Chelgraph demonstrated its A3 printer at the hall. At Linotype, the
+adaptation of Design Studio for Arabic was demonstrated and the development
+work on fonts was shown.
+
+
+Quorum showed their production facilities, which include origination,
+typesetting and printing. A speciality is the acceptance of text in
+electronic form, either on disk or via modem. The facilities available on
+the Intermedia system were comprehensively demonstrated.
+
+
+All in all a very enjoyable day, despite the intricacies of the town's
+traffic system. One good thing -- the Gold Cup was not being run!
+\author{Henry Holloway}
+
+
diff --git a/info/digests/texline/no13/courses b/info/digests/texline/no13/courses
new file mode 100644
index 0000000000..55737ca6e9
--- /dev/null
+++ b/info/digests/texline/no13/courses
@@ -0,0 +1,172 @@
+{\frenchspacing\def\two#1(#2){\bi #2:\quad#1}
+\let\Box\bigcirc
+\title{6th European \TeX\ Conference}
+The 6th European \TeX\ Conference will be held at
+La Maison de la Mutualit\'e, Paris, on 23--25th September 1991.
+The Conference will have simultaneous translation facilities.
+
+The programme of presentations consists of:
+\two Russian \TeX (A. {\sc Samarin})
+\two \TeX\ and Africa (J. {\sc Knappen})
+\two \TeX: the limit of multilingualism (M.~{\sc Fanton})
+\two Towards an arabicized version of \TeX (M.~{\sc Fanton} {\it et
+al.})
+\two \TeX niques in Siberia (Th.~{\sc Jurriens})
+\two Babel, a multilingual style options system (J.~{\sc Braams})
+\two An international version of {\sf Make\-Index} (J. {\sc Schrod})
+\two As\TeX: An integrated and customisable multiwindow environment
+ for scientific research (M. {\sc Lavaud})
+\two Managing the interface to \TeX (S.~{\sc Larsen})
+\two Shell for \TeX (B. {\sc Malyshev})
+\two Colour\TeX\hfill(Ch.~{\sc Cerin})
+\two Making graphics in \TeX, GWEZ builds tree structures
+ and print them (B.~{\sc Leguy})
+\two Conversion of MicroSoft {\sc word} into \LaTeX (P. {\sc Bacsich}
+{\it et al.})
+\two Scholar\TeX: last enhancements
+ (Y.~{\sc Haralambous})
+\two \TeX\ dismembered (A. {\sc Wittbecker})
+\two Maths into BLUes (K.~{\sc van der Laan})
+\two Organising a large collection of style files for different \TeX\
+ macro packages (A.~{\sc Binding})
+\two Typesetting SGML documents using \TeX (A. {\sc Dobrowolski})
+
+
+
+Chaired by well-known experts, the panels are for example:
+\item{\rtr} Teaching (\La)\TeX\ to a diverse audience
+\item{\rtr} (\La)\TeX\ in Europe
+
+
+
+Some sessions will be set-up on topics to be decided upon during
+the conferences.
+
+
+Various hardware and software vendors will exhibit their latest products.
+A commercial session will be organised so they can talk freely about
+their products.
+
+A open `question time' session will take place during the conference.
+
+
+The conference will cost FF1700. A discount of FF200 is available for
+members of local groups like GUTenberg, \Dante, NTG, Nordic Group,
+Italic, ukTeXug or TUG. After May 30th a
+10\% surcharge applies to all bookings.
+
+\section{\TeX\ Dinner}
+A dinner will be held on Tuesday evening at the restaurant of the
+Villette centre of Sciences and Industry. The dinner will follow the
+showing of a film using hightech sound and light systems on the
+{\it g\'eode}'s 1,000 m$^2$ hemispheric screen. Special effects take
+the viewer on an imaginary journey to another place and time. A coach
+tour of Paris by night will concluded the evening.
+All those taking part in the conference will be admitted free.
+Guests are welcome to join in the evening's entertainment for a
+FF270 charge.
+
+\section{Tutorials}
+The following tutorials will take place in the week preceeding the
+conference:
+
+\noindent$\bullet$Advanced \TeX nical Details:
+Philip {\sc Taylor}, {\sc rhbnc}:
+ This course is intended to cover the more advanced featues of
+\TeX\ macro programming, including such esoteric aspects as
+|\afterassignment|, |\futurelet|, |\expandafter|, |\uucode|, etc. Some
+time will be devoted to the area of cross referencing, both via
+external files and via control sequences, and the manipulation of
+|\catcode|s will be covered in some detail.
+
+
+\noindent$\bullet$\LaTeX\ Style Files: Chris {\sc Rowley}, Open
+University: Ever wondered how to make \LaTeX\ do what you
+wanted?
+ This course will help you understand how to modify
+ \LaTeX\ style files to give quality typesetting, and
+ may even give you the confidence to write your own.
+ Some experience with \LaTeX\ and \TeX\ would be an advantage.
+
+\noindent
+$\bullet${\mf METAFONT}: Doug {\sc Henderson}, Blue Sky Research \&
+Yannis {\sc Haralambous}, Universit\'e de Lille:
+ The course will cover the basics of {\MF}, but should
+ provide participants with enough information to generate
+ their favourite CM fonts at any design size, tinker with
+ the multitude of parameters, and even start to design their
+ own characters.
+
+\noindent
+$\bullet$Beginning and Intermediate \LaTeX\
+Malcolm {\sc Clark}, {\sc pcl}:
+ Become proficient in \LaTeX\ in four days! The
+ course covers the fascinating world of \LaTeX, concentrating
+ on the joys of structured documentation, whilst trying
+ to maintain a facade of quality typesetting. The course
+ will include some details on modification of the style files
+ to European standards, an examination of some publishers'
+ \LaTeX\ style files and the recent additions to \LaTeX, notably
+the `orthogonal' font styles. Suitable
+ for technical and non-technical alike.
+
+
+\section{Information about the tutorials}
+The location of the tutorials is different from the location of
+the congress. They will be held at \'Ecole Normale Sup\'erieure
+and the Institut Blaise Pascal Paris, on the 17th--20th September 1991.
+
+The tutorials will start on Tuesday, September 17th, at 9.30. Each
+tutorial will last four days. They will be supplemented with
+practical work on workstations. The number of participants in
+each tutorial is limited.
+
+Each of the tutorials is priced at FF2500, but
+participants on the tutorials are entitled to a discount of FF500
+from the registration fee to the 6th European \TeX\ Conference.
+
+
+
+\bigskip
+\bar
+\title{GUTenberg'91}\vskip-3pt
+\centerline{\bf Technical and Scientific Publishing}
+\noindent
+The Conference will take place at La Maison de la Mutualit\'e,
+Paris, on September 26th, 1991.
+The day will be devoted more specifically to issues connected with the
+French language, selected topics will cover French publishing
+problems. The following topics are planned:
+
+
+\bi {\TeX V3 contre ML\TeX}
+\two {Les disquettes GUTenberg'91}(N. {\sc Brouard})
+\two {L'impression des formules chimiques}
+(M. {\sc Laugier})
+\two {Un programme pour modifier les {\dvi}}
+ (M. {\sc Laugier} {\it \& al.})
+
+\noindent
+Other presentations are under consideration but have not yet been
+finalised. A `Question Time' session about networks is planned.
+The Conference will have simultaneous translation facilities.
+Simultaneous translation. Official languages are English and French.
+ The cost will be FF700. If you are
+attending the 6th \TeX\ conference, a discount of FF200 may be
+deducted from the total amount. Bookings after May 30th attract a
+surcharge of 10\%.
+
+\section{Contact}
+{\obeylines
+GUTenberg, 6th European \TeX\ Conference
+BP 21
+78354 Jouy en Josas cedex, France
+Telephone: +(33 1) 34 65 22 32
+Fax: +(33 1) 34 65 22 28
+E-mail: {\tt on@jouy.inra.fr}\strut}}
+
+
+
+\endinput
+
+
diff --git a/info/digests/texline/no13/dedham b/info/digests/texline/no13/dedham
new file mode 100644
index 0000000000..fa8b800cb4
--- /dev/null
+++ b/info/digests/texline/no13/dedham
@@ -0,0 +1,61 @@
+\title{On the fringe of Boston}
+I confess that my enthusiasm for the TUG conference in
+Dedham was limited.
+In a hotel on the outskirts of Boston; no electronic
+access; height of the summer; Red Sox out of town;
+first four day meeting; first meeting with `one-day'
+tickets; major accent on the publishing fraternity --
+persons in suits. Oh dear. It turned out a whole lot
+better.
+
+The theme of this year's meeting was `Inroads into
+Publishing' and stemmed from a proposal made by Lance
+Carnes last year to try to arrange a meeting which would
+be strongly targetted towards the publishing industry.
+This was seen as part of a longer term policy to ensure
+the future of \TeX\ by promoting it to a wider audience.
+The first two days were more strongly oriented towards
+the traditional publishing business than the others. The
+conference proper started with a keynote address from Nico
+Poppelier from Elsevier. In general this was a good talk,
+but I found it singularly unfortunate at a forum where
+there was an attempt to convince and impress the
+conservative business world, that Nico should take time
+out to list his set of `needed changes' to \TeX. This
+theme, of `how shall we change \TeX' was one which was
+repeated again and again throughout the conference.
+There is undoubtedly a body of opinion which sees the need
+for change. However, as Mike Spivak's {\sl Contrarian
+View} shows, there are opposing views too.
+
+This meeting again took the pattern of `networking
+lunches'. The notion is that the lunch tables are labelled
+with various topics and you go to the table with your
+favourite topic. It is certainly a useful idea for a
+meeting at which many people may be new, and who whant to
+locate others with similar interests. An innovation this
+year was the introduction of panels. To
+my surprise it worked remarkably well. There were a few
+good opinionated panellists. Reverting to tradition,
+Personal \TeX\ provided the wine and cheese reception, but
+another innovation -- the wine didn't run out. I don't
+know if the parallel sessions were an innovation, but they
+were a pain. Memo to conference programmers: {\sc don't
+have parallel sesssions!}
+
+The other component were the workshops. I felt sorry for
+Chris Carruthers {\sl Interpreting \LaTeXsl\ Error
+Messages}, who had a group including Frank Mittelbach,
+who really ought to know enough not to make \LaTeX\
+errors.
+
+To hand out a few honours: probably the best function was
+the Clambake, sponsored by ArborText and Micro Programs
+-- all those lobsters! The best content -- Yannis
+Haralambous; the best panel -- historical roundtable. But
+I didn't get to everything.
+
+What about the bowling you will ask. Candle\-pin;
+ten pin, with very much smaller balls (no holes!) and an
+odd set of rules. But it was an interesting challenge. So
+in the end it all worked out quite well.\author{Malcolm
diff --git a/info/digests/texline/no13/didot b/info/digests/texline/no13/didot
new file mode 100644
index 0000000000..3dd0cebbad
--- /dev/null
+++ b/info/digests/texline/no13/didot
@@ -0,0 +1,63 @@
+\centerline{\bf First European Summer School}
+\centerline{\bf in Digital Typography}
+\smallskip
+\noindent
+This Didot Summer School will be held in Lausanne,
+Switzerland, on September 23--28th, 1991. The objective
+of the School is to bring together computer scientists and
+type designers. Didot, a near acronym for Digitising and
+Designing of Type, is part of a CEC Comett II program
+aimed at developing joint training in high technology.
+Didot's specific aim is to design, implement and evaluate
+a European curriculum for digital typography.
+
+This summer school is intended for font designers,
+graphic designers, font experts, computer scientists
+(especially those specialising in graphic tools, design
+and development), and other assorted scientists,
+researchers, instructors and teachers.
+
+There will be two parallel sessions: one for font
+designers and one for computer scientists; and a set of
+courses and lectures common to all participants. The parallel sessions
+include either lectures on the technical aspects of type
+(for computer scientists), or a set of practical
+workshops on computer aided type design, intended for
+type and graphic designers. The
+common part includes global instruction, courses on the
+visual aspects of type and discussions and round tables
+at the end of each half-day.
+
+The Visual Aspects of Type course is to be given by
+Andr\'e G\"urtler and Christian Mengelt of the AGS School
+of Design in Basle; Roger Gersch (EPFL) and Jakob
+Gonczarwski (Typographics Ltd) will present the Technical
+Aspects of Type and Two Dimensional Graphics course. This
+course includes sessions on character grid fitting and font
+formats (e.g.~URW, Adobe Type~1, Truetype). Jacques
+Andr\'e will lead the workshops on Graphic-Aided Font and
+Graphic Design Systems: this comprises 5 workshops each
+of two half days, covering aspects of Fontographer,
+Letraset Font Studio, Ikarus, Typo, and \PS\ display
+programs.
+
+A number of guest speeches will
+complete the program.
+English is the official course language. No translations
+will be provided.
+Costs are SFr\,1,600 for the summer
+school (a student fee of SFr\,700 is available). Hotel
+accommodation is estimated at up to SFr\,110 per night.
+
+Contact:
+{\obeylines
+Marie Jo Pellaud, Didot Course
+EPFL-LSP
+INF-Incublens
+CH-1015 Lausanne, Switzerland
+tel: (41) 21 693 2641
+fax: (41) 21 693-5263
+email: {\tt hersch@eldi.epfl.ch}\strut
+}
+
+
diff --git a/info/digests/texline/no13/dtp b/info/digests/texline/no13/dtp
new file mode 100644
index 0000000000..cf4b9aadd1
--- /dev/null
+++ b/info/digests/texline/no13/dtp
@@ -0,0 +1,89 @@
+\centerline{\bf Desktop Publishing in}
+\centerline{\bf Astronomy and Space Sciences}
+\smallskip
+\noindent The Strasbourg Observatory\slash Astronomical
+Data Centre will be organizing a meeting on `Desktop Publishing in
+Astronomy and Space Sciences' on October 1st--3rd 1991.
+
+Desktop publishing is widespread nowadays and a number of packages are
+used by astronomers, space scientists, engineers and technicians for
+producing their papers, reports, etc., as well as their everyday mail
+(typically through Word, \TeX, \LaTeX\dots). The motivations behind the
+choice of a given package are various and not always rational ones (such as
+availability, financial constraints, word of mouth recommendations).
+
+There is a wealth of experience to be shared openly for the benefit of
+everybody and it would certainly be useful to confront performances,
+capabilities, as well as possible complementarities of the text
+processing applications that are presently most frequently used in
+astronomy and space sciences. There is most likely no `best' system,
+but it might be possible to prepare a digest of the best parts of the major
+ones without having to review computer journals.
+
+It is not only the point of view of the authors or writers which should
+matter here, but also the reasons behind the choices that a few publishers
+have already made (typically, Springer \TeX\ Macros\dots). On this side, the
+advantages are obvious: the manuscripts are delivered directly by the
+authors\slash scientific editors in a standardized machine-readable way
+(saving time and money) and the final appearance of the publications is
+substantially enhanced, be it only through its harmonization.
+
+What happens in other communities of related fields will also be
+investigated. Some publishers represent up to 500 scientific journals.
+It will be interesting to listen to their explanations as to how their
+choices have been made and for them to hear what scientists have to say
+in that respect.
+
+Another aspect of this colloquium is related to the developments carried
+out by auxiliary software companies or individuals. They are producing
+self-sustained packages, complementary tools and\slash or utilities to be
+plugged into already well-established text processing systems. Here
+again scientists should express their views, needs and wishes.
+
+The meeting is timely as desktop publishing reaches such a development
+that it would be appropriate for the corporation and for publishers to
+issue recommendations for standardization, compatibility and\slash or
+complementarity from the software producers.
+
+Sessions will be organized in such a way that each of the parties will
+be able to make their points as to the advantages they find with given
+packages, the constraints they have to comply with, the requirements
+they would have for further developments. We shall also attempt to set
+up exhibitions and\slash or demonstrations.
+
+The meeting will also aim at issuing recommendations for publishing
+standards, as well as for compatibility and/or complementarity from the
+software producers. A special session involving the editors of the major
+scientific journals is being set up by James Lequeux
+({\tt aanda@frmeu51.bitnet}).
+
+
+Proceedings will be published and distributed free of charge to the
+persons who will actually attend the meeting.
+
+There will be no registration fee; meals will have to be
+paid for individually. Because of the
+chronic shortage of rooms in Strasbourg, we advise you to secure
+your accommodation in the city as soon as possible.
+If you are interested in attending this colloquium, please contact me at
+
+{\obeylines\parindent30pt
+ Observatoire Astronomique
+ 11, rue de l'Universite
+ F-67000 Strasbourg
+ France
+ tel: +33-88.35.82.22
+ telex: 890506 starobs f
+ fax: +33-88.25.01.60
+ email: {\tt heck@frccsc21}
+}\noindent
+in order
+to be put on the mailing list to receive additional information (list of hotels,
+preliminary programme, and so on). As the audience might have to be limited, we
+advise you to do this as soon as possible.
+
+Please feel also free to send us your comments and to recommend people
+(scientists, editors, publishers, software producers, company managers,
+and so on) you think we should contact.
+\author{Andr\'e Heck}
+
diff --git a/info/digests/texline/no13/ep92 b/info/digests/texline/no13/ep92
new file mode 100644
index 0000000000..bf8f7de81d
--- /dev/null
+++ b/info/digests/texline/no13/ep92
@@ -0,0 +1,78 @@
+
+
+\title{EP92}
+An {\bf International Conference on Electronic
+Publishing, Document Manipulation and
+Typography} will be held in Lausanne,
+Swiss Federal Institute of Technology
+(Switzerland), on April 7--10, 1992.
+
+This conference will be the fourth in a
+series of international conferences organised to promote the exchange of novel
+ideas in the area of computer manipulation
+of documents.
+
+The first two conferences in the series,
+EP86 held in Nottingham, England, and
+EP88 in Nice, France, concentrated
+mainly on the specific aspect of the production of
+documents by computer, from composition to printing.
+EP90, which was held in Washington, adopted a broader
+definition of the term Computer Assisted
+Publication, and accordingly included
+more materials on new topics such as the
+application of data-base techniques to
+document handling, hypertext and hypermedia systems, and document recognition
+and analysis.
+
+EP92 will follow this trend. Its objective will
+be to present the state of the art by reporting original and recent contributions to this
+area. The conference proceedings will be
+published by Cambridge University Press
+and will be available at the conference.
+
+A day of tutorials is planned for April 7.
+Suggestions for contributions with introductory and survey topics are requested.
+
+\bitem Modelling and representation of documents
+\bitem Document structures
+\bitem Integration of text, images and graphics
+\bitem Integration of document manipulation systems with other software tools
+\bitem Standards: evaluation and implementation
+\bitem Object oriented approaches.
+
+\bitem Documents management
+\bitem Document preparation systems
+\bitem Hypertext: production, editing and visualisation
+\bitem Large text data-bases
+\bitem Distributed documents: parallel algorithms, multi-user documents
+\bitem User-machine interfaces.
+
+\bitem Document recognition and Interpretation
+\bitem Structural recognition of documents
+\bitem Filtering and image handling techniques
+\bitem Multi-lingual documents
+\bitem Semantic text structures
+\bitem Indexing techniques.
+
+\bitem Typography and graphics
+\bitem Character design
+\bitem Use of gray levels and colour technology
+\bitem Pagination and layout.
+
+\bitem Document manipulation and educatlon
+\bitem Computer assisted document production
+\bitem Experiences in teaching EP
+\bitem The place of EP in Computer Science Curricula.
+
+\noindent Contact:
+
+{\obeylines
+EP92
+Ecole Polytechnique F\'ed\'erale de Lausanne
+IN Ecublens
+CH 1015 Lausanne
+Switzerland
+{\tt ep92@eldi.epfl.ch}\strut
+}
+\endinput
diff --git a/info/digests/texline/no13/good_guys_plus b/info/digests/texline/no13/good_guys_plus
new file mode 100644
index 0000000000..3ddcc80a14
--- /dev/null
+++ b/info/digests/texline/no13/good_guys_plus
@@ -0,0 +1,57 @@
+\title{Good Guys}
+{\obeylines\parindent0pt\parskip0pt
+Angus Duggan
+Department of Computer Science
+University of Edinburgh, JCMB
+The King's Buildings, Mayfield Road
+Edinburgh EH9 3JZ, UK
+email: {\tt ajcd@uk.ac.ed.lfcs}
+\medskip\goodbreak
+
+Mike Spivak, \TeX plorators
+3701 W Alabama
+Suite 450-273
+Houston, TX 77027, USA
+email: {\tt spivak@math15.rice.edu}
+\medskip\goodbreak
+
+
+David Penfold
+Edgerton Publishing Services
+20 Edgerton Road
+Edgerton
+Huddersfield HD3 3AD, UK
+0484 519462
+\medskip\goodbreak
+
+Betsy Dale
+ArborText Inc, Suite 300
+535 W William St
+Ann Arbor, MI 48103, USA
+email: {\tt bjd@arbortext.com}
+\medskip\goodbreak
+
+David Rhead
+Cripps Computing Centre
+University Park
+Nottingham N57 2RD, UK
+email: {\tt d.rhead@uk.ac.nottingham.ccc.vme}
+\medskip\goodbreak
+
+Henry Holloway
+11 Hillcrest Road
+South Woodham Ferrers
+Essex CM3 5NU, UK
+\medskip\goodbreak
+
+Peter Ashby \& Anna Duckworth
+BCS ITEXT
+British Computer Society
+PO Box 1454
+Station Road
+Swindon SN1 1TG, UK\strut
+}
+
+
+
+\endinput
diff --git a/info/digests/texline/no13/gut b/info/digests/texline/no13/gut
new file mode 100644
index 0000000000..79c592cb52
--- /dev/null
+++ b/info/digests/texline/no13/gut
@@ -0,0 +1,138 @@
+\def\gut#1:#2:#3*#4.{\smallskip\noindent {\it #1\/}: #2, pp.#4:
+#3\smallskip}
+\catcode`\<=\active
+\def<{%
+\ifmmode\ll\else\leavevmode\raise1pt\hbox{$\scriptscriptstyle\ll$}\fi}
+\catcode`\>=\active
+\def>{%
+\ifmmode\gg\else\leavevmode\raise1pt\hbox{$\scriptscriptstyle\gg$}\fi}
+
+\centerline{\bf Cahiers GUTenberg}
+\centerline{\bf Summaries from Number 7, November 1990:}
+\gut Logiciels \TeX\ sur serveurs:
+Peter Flynn:
+An account of the various \TeX-relevant electronic archives
+available. It includes at least 8 list servers, the major
+servers (Aston), Simtel, and the hundreds of FTP
+accessible sites, as well as some clues of how to access
+CIX and even Channel 1. It also has an allusion to the
+\TeX\ Companion.
+*3--16.
+
+\gut Le gestionnaire Biblio\TeX:
+J.-F.~Vibert:
+{\sc Biblio\TeX} is a package to manage a bibliographic
+file and produce specific \BibTeX\ or \LaTeX\ output
+files. This paper gives functional and usage descriptions.
+*16--22.
+
+\gut Traitment d'index avec \LaTeXsl:
+Philippe Louarn:
+As \LaTeX\ handles structured documents, it is easy to
+create some features, such as table of contyents or
+bibliography. This article attempts to evaluate several
+methods of index generation usable with \LaTeX. A real
+example will illustrate our purpose.
+*23--28.
+
+\gut Fontes latines europ\'eenes et \TeX\ 3.0:
+Michael J.~Ferguson:
+A translation of the report on eth extended \TeX\ Font
+Encoding which has been officially approved by TUG.
+*29--31.
+
+\gut ``La typographie'' <entre guillemets>:
+Ferand Baudin:
+An account of the use of guillemets (and quotation
+marks) in european languages.
+*33--34.
+
+\gut \TeX90 F\'ailte \i\ gGol\'a\i ste na hOllsco\i le, Corca\i
+gh:
+Denis M\'e gevand:
+Report of the \TeX90 conference at Cork. Covers some
+papers, bird's-of-a-feather sessions, and the font
+encoding project (and the social stuff too).
+*35--37.
+
+\gut Ballades irlandaises:
+Bernard Gaulle \& Olivier Nicole:
+During the Cork euro\TeX\ conference two important meetings were
+plabbed: a western and eastern european \TeX\ users groups
+leaders summit and the meeting of the TUG board of
+directors. This paper gives a report of these two events.
+*38--40.
+
+\gut Comment le faire en \LaTeXsl:
+\'Eric Picheral:
+A tutorial discussing: special and reserved characters; the
+insertion of a source file; and a new {\tt description}
+environment, similar to {\tt describe}.
+*41--43.
+
+\gut Les fiches cuisine d'Onc' PostScript:
+Bruno Borghi:
+This is the fourth in this series and discusses \TeX\ and \PS,
+in particular showing some cute \PS\ tricks.
+*44--47.
+\medskip
+\centerline{\bf Summaries from Number 8, March 1991:}
+\smallskip
+\gut L'avenir de \TeX\ et de \MFsl:
+Donald E Knuth:
+Translation of the article on the future of \TeX\ and \MF\
+published in \TUGboat\ and \TeXline.
+*1--2.
+
+\gut La composition typographique:
+Alan Marshall:
+Computers have radically alteraed the organisation of editorial
+and typographic production processes. However, the basic
+activities involved have remained largely untouched by technical
+change. The article which follows describes the prioncipal
+typographical task which have to be carried out, whether it be
+with traditional or new technologies.
+*3--9.
+
+\gut La typographie et la loi:
+Andr\'e R Bertrand:
+An account of the application of copyright law to fonts. It is
+targetted mainly at french law, but also addresses international
+issues.
+*10--19.
+
+\gut Serveurs de fichiers et de fontes pour \TeX:
+Raymond Tr\'epos \& Philippe Louarn:
+This article presents computer networks and software available
+with the networking (mail, news and file transfer) and the way to
+connect to the french net (Fnet). A special case for \TeX\ users
+will be shown.
+*21--27.
+
+\gut M\'etrique des fontes PostScript:
+Jacques Andr\'e \& Justin Bur:
+This note is concerned with \PS\ font metrics. Bounding boxes
+and the Adobe Font Metric file are presented, as well as how to
+use them for justification, pair and track kerning, etc.
+*29--50.
+
+\gut Analyses bibliographiques:
+Jacques Andr\'e \& Olivier Nicole:
+Book reviews of a range of books, concentrating on {\sl Lexique
+des r\'egles typographiques en usage \'a l'Imprimerie
+nationale}, but covering a range of others, in french and
+english.
+*51--56.
+
+\gut Comment le faire en \LaTeXsl:
+\'Eric Picheral:
+More \LaTeX\ stuff, including variations on {\tt article},
+indentation after a section, and the use of {\tt verse}.
+*57--58.
+
+\gut Le coins ges gourous:
+Philippe Louarn:
+Neat stuff with matrices.
+*59--61.
+
+\endinput
diff --git a/info/digests/texline/no13/lamstex b/info/digests/texline/no13/lamstex
new file mode 100644
index 0000000000..4ae0856e5c
--- /dev/null
+++ b/info/digests/texline/no13/lamstex
@@ -0,0 +1,80 @@
+\title{\LamSTeX{} Goes Public}
+\LamSTeX{}, version 2.0, is now public domain software. I am hoping that it
+will be placed in various archives, and that TUG and others will distribute~%
+it.
+
+For questions about \LamSTeX{}, I may be contacted via email:
+{\tt spivak@math15.rice.edu}
+
+For those unfamiliar with \LamSTeX{}, {\it vis a vis} \LaTeX, here are some
+salient points:
+\bitem \LamSTeX{} is not $\cal AMS$-\LaTeX!
+\bitem \LamSTeX{} is an extension of \AmSTeX, and thus almost completely
+compatible with plain \TeX\ (an additional file, {\tt pcompat.tex}, provides
+complete compatibility, by overriding certain changes made in \AmSTeX).
+
+\bitem \LamSTeX{} provides essentially the same functionality as \LaTeX, although
+the syntax is usually more concise.
+
+\bitem \LamSTeX{} also provides this functionality in a much more flexible form; all
+automatic numbering schemes can easily be modified for special
+circumstances (many illustrations of the importance of this flexibility are
+given in the \LamSTeX\ Manual).
+
+\bitem \LamSTeX{} can now interface with \BibTeX.
+
+\bitem \LamSTeX{} provides many additional fcatures, only a few of which can be
+indicated here:
+
+\itemitem{(1)}Of particular interest are complicated commutative diagrams --
+at least as professional-looking as those that appear in journals -- and
+partitioned matrices.
+
+\itemitem{(2)}The table macros generally provide much more professional
+looking tables than other packages, because of the close attention to struts,
+because of simple methods of extending lines between rows when needed, etc.
+
+\itemitem{(3)}\LamSTeX{} has an extensive set of commands for automatic
+placement of figures and tables.
+
+\bitem Many \LaTeX\ difficulties just now being addressed have simply never existed
+in \LamSTeX{}. For example, there are no such things as `fragile' commands in
+\LamSTeX{}, and no worries about long |\write|'s and undesired expansions in
+|\write|'s to auxiliary files (like the |.toc| file). Arbitrarily long literal
+mode material can split across pages.
+
+\bitem The \LamSTeX{}{\it Wizard's Manual\/} provides {\sc extensive}
+documention; it explains in complete detail the reasons for every single
+device in the code.
+
+\bitem The \LamSTeX{} {\it Style File Designer's Manual\/} provides
+documentation for designing style files; it is essentially an extract from
+the {\it Wizard's Manual}, covering just those topics that might be needed by
+style designers.
+
+\bitem Writing the {\it Wizard's Manual\/} afforded me the opportunity to
+completely rewrite \LamSTeX{}. Version 2.0 has many small bug fixes, important
+extensions, and more efficient code. In addition, the code is much more
+modular, allowing changes for different style files to be made much more
+easily.
+
+\bitem I will support \LamSTeX{} not only with bug fixes, but with extensions that
+seem reasonable and desirable.
+
+The 300 page spiral bound \LamSTeX{} Manual, {\it \LamSTeX, The Synthesis},
+is \$30.00 (includes shipping).
+
+The 600 page {\it Wizard's Manual\/}, presumably of extremely
+limited interest, is printed on demand. It is distributed in the form of
+approximately 300 3-hole punched pages, printed (on both sides) by laser
+printer. It is \$40.00, including shipping. (A free copy may be requested
+with every order of 15 or more \LamSTeX{} Manual.)
+
+The {\it Style File Designer's Manual\/} is not yet complete. It will
+probably be about 200 pages, spiral bound like the \LamSTeX{} Manual, and
+sold at a bargain price (perhaps \$10.00, including shipping).
+
+All manuals may be purchased through \TeX plorators.
+\author{Mike Spivak}
+% 3701 W Alabama, Suite 450-273, Houston, TX 77027
+
diff --git a/info/digests/texline/no13/matter b/info/digests/texline/no13/matter
new file mode 100644
index 0000000000..9588113326
--- /dev/null
+++ b/info/digests/texline/no13/matter
@@ -0,0 +1,331 @@
+
+{
+\let\subsection\section
+
+\title{The matter of TUG}
+TUG has changed and is changing. Until the appearance of
+{\sl \TeX\ and TUG News} (TTN), TUG's newsletter, which was
+sent to every TUG member, the nature of these changes has
+not been made very public. For reasons which are sometimes
+clear and sometimes obscure, the details have not really
+been shared widely by the membership. Apart from the
+understandably bland and anodyne reports in TTN, other details can
+be found in the reports furnished by the five or six
+so-called international vice presidents. Regretably
+neither the President, Nelson Beebe, nor the Vice
+President, Rick Furuta presented their membership the
+guidance and information they deserved. But despite these
+inferred misgivings, I remain confident that TUG has a
+future, and that TUG remains the international voice of
+\TeX.
+
+TUG gives some appearance of being unhealthy and
+moribund. I suspect there are a number of reasons for
+this. Let me try to gather together some of these, and
+then tell you why I think that the alarum bells need not be
+sounded yet.
+
+
+\subsection{\TeX3}
+First, \TeX\ itself. For a moment ignore
+the euphoria about \TeX3 and virtual fonts. Really there is
+not much that is new there. ML\TeX\ had already solved the
+eight bit `problem' and virtual fonts had actually been
+around for a good many years. What \TeX3 did was to make
+these available in a non-proprietary way, so that they
+were truly part of \TeX. Perhaps more significant is
+Knuth's statement that there is to be no more development
+of \TeX\ at all (or of \MF\ or Computer Modern). The only
+proviso is that bug fixes may be carried out, until such
+times as Knuth's death, at which point work on \TeX\ must
+cease. Any development based on \TeX\ may not be called
+\TeX. It is by no means clear to me where, for example
+J\TeX, V\TeX, or extended Computer Modern fit into this
+embargo, but I guess we would all wish to respect Knuth's
+wishes. There is a slight paradox here. For many years,
+\TeX\ had not changed: basically since 1982. In the
+intervening years it has become evident that there were
+some pretty severe deficiencies in the system which, it
+could be argued, precluded it from achieving its avowed
+aim of producing `masterpieces of the typesetting art',
+unless of course that masterpiece happened to be {\sl The
+Art of Computer Programming}. The innovation of \TeX3
+suddenly reawakened the dream that perhaps Knuth would see
+\TeX\ as an evolving project. And just as suddenly, the
+prospect was dashed from our lips. My own hopes were that
+Knuth would refuse to bring \TeX\ up to an 8-bit standard,
+and equally to be unwilling to allow the hyphenation and
+diacritical support that we needed. In this way, the \TeX\
+world would have been forced to create a structure where
+enhancements like these could be accommodated, and \TeX\
+would still be \TeX. Instead, any improvements or changes
+will have to adopt a much more radical model. At much the
+same time, Leslie Lamport agreed that \LaTeX\ 2.09 would
+be `corrected' to version 2.10. This work was not to be
+done by Lamport, but by a team led by the dynamic duo
+(Mittelbach \& Sch\"opf), under the chairmanship of
+Lamport himself. This project evolved into the \LaTeX3
+project. So, in a sense, we have had the self removal of
+the chief players. What we are noting is that the flame
+is being passed on to a new generation, and that at the
+moment of being passed on it is in danger of being
+guttered.
+
+Ideally one would like the flame to be passed to TUG.
+TUG's support for \TeX\ is considerable, as one would
+hope. I guess it is widely known that it was TUG funding
+which enabled the \TeX\ project to be completed in the
+first place, and that it supports the {\tt texhax} digest
+and Orin Patashnik's completion of \BibTeX. It also
+supports a wide educational programme -- perhaps wider
+than you might realise, since many courses are delivered
+in house, with no advertising in TUGboat or elsewhere.
+
+\section{TUG works}
+A brief account of TUG's continuing activities includes
+\bitem \TUGboat: perhaps the single most cogent reason for membership
+of the group. Now published four times a year and comprising around 600
+pages in total, \TUGboat\ contains information on new developments in
+\TeX, \LaTeX, \AmSTeX, \MF, and the allied macro packages.
+
+ \bitem TUG's annual meeting brings \TeX\ users together to learn the
+latest in \TeX\ applications and innovations through seminars, talks
+and informal gatherings (the last three conferences have featured
+10-pin bowling as a major social event). Each conference is
+informative, but it is also friendly.
+
+\bitem TUG provides a single location for
+information, documentation and product purchase for
+\TeX-related materials (hardware, software, publications).
+
+
+\bitem pursues ways of extending the use and
+applications of \TeX\ into many areas (such as publishing
+-- hence the 1991 theme for the annual meeting).
+
+\bitem continues to provide seminars and classes for beginner,
+intermediate and advanced \TeX\ users. It is also developing
+new courses in other areas of concern to the community, for
+example typography, document design\dots
+
+\bitem is investigating methods for sponsorship to help
+ form and stimulate
+Local User Groups (LUGs).
+
+\bitem the publications committee is developing `\TeX\ and
+TUG News', a second TUG publication which may be available
+electronically, demonstrating \TeX's portability.
+
+\bitem the {\sc dvi} standards committee is working towards
+providing standards for drivers. The level 0 will be
+available `shortly'.
+
+\bitem is looking into ways in which it might `certify'
+\TeX\ products.
+
+\bitem is compiling a Resource Directory of all \TeX\
+material available; commercial and public domain \TeX\ implementations;
+supporting software; documentation; publishing services -- a sort of `Whole
+\TeX\ Catalogue'. TUG members should have received their copy by now.
+
+\bitem has recently purchased a disk copier so
+that it can begin to supply public domain software to the
+membership, in cooperation with Jon Radel.
+
+\bitem increasing public awareness of \TeX,
+particularly to the user of personal machines, not
+connected to any electronic network.
+
+\bitem Discounts: members obtain discounts on the annual meeting,
+TUG-sponsored courses and selected publications. There are also student
+rates for both membership and courses.
+
+From where does TUG obtain its funding? TUG's
+income comes from two sources: membership subscriptions
+and from `generated income'. The membership subscriptions
+cover \TUGboat\ but also leave a substantial surplus. In
+1990 the membership dues were \$171,000 and the
+TUGboat expenses were only about half of this at \$92,000. Note though
+that there is an advertising income of \$33,000; I assume that most of
+that advertising is in \TUGboat. Running the TUG office is met from the
+generated income. This includes sales, courses and conferences. (Yes,
+that's why they are so expensive.) In 1990, total TUG income was
+\$623,700. The two largest components of income were from the annual
+meeting and courses (\$206,000), and from the sales of
+books, software etc. (\$190,000). I~personally believe this
+factor, that the income generated from sources other than membership
+accounts for only 27\% of the total income inhibits
+serious attention to membership expansion. After all, extra members do
+not bring in significant amounts of extra cash. The net benefit is
+not large. Increasing
+membership by say 1000 would probably only generate \$35,000, less
+say \$5--10,000 for \TUGboat\ and its postage. Perhaps TUG should be
+pursuing industrial sponsorship from those hundreds of organisations who
+have or do benefit from \TeX: like DEC, Interleaf, IBM etc. At present
+they depend rather too much on the benevolence of a few vendors. No
+vendor I have talked to feels they have had any real `commercial'
+benefit from adverts in \TUGboat\ or attendance at the conferences. In
+fact, I was recently struck by the fact that in \TUGboat\ Volume~11,
+no.~4, there was no advert from PC\thinspace\TeX, for so long a stalwart
+supporter of the magazine.
+
+The dependence on courses for generation of income has
+meant that the recent downturn in the US economy has had
+a deleterious effect on TUG. The reduction in in-house
+courses has, at a stroke, induced a serious financial
+shortfall. After all, what is the first thing you cut
+back on? Why, education. In fact the sums are not so bad
+and TUG can survive on its reserves for a few years, serious thought
+has to be given to the pattern of finances.
+
+\subsection{The truth, but only some of the truth}
+But this still skirts round the problem. Let's tackle it
+at last. At the end of 1990, Ray Goucher, for many years
+TUG's Executive Director, left the organisation. I think
+it is fair to say that this was not the happiest of
+partings. Partly as a result, the Treasurer, David Ness,
+the Vice President, Rick Furuta, and later the Secretary,
+Calvin Jackson, have tendered their resignations. This in
+itself is no recipe for disaster, since the President may
+appoint replacements. Sadly though, as far as the Board is concerned,
+Nelson Beebe was curiously silent from late October 1990 through to
+about the middle of March 1991 (and not too voluble since). The
+Executive and Finance Committee were unable to act. This was especially
+sad, since the rest of the Board of Directors affirmed
+its willingness and determination to rally round in time of
+crisis and to be directed in ways which are constructive.
+In the face of this inaction, the TUG office thrived.
+Despite dire warnings from the President of mass staff
+resignations, the staff were as committed and active as
+ever. Under the temporary direction of the extremely able
+Ron Whitney, the business of TUG continued.
+
+In passing, Charlotte Larendeau, has recently married and has moved to
+California with her new husband. Charlotte's dynamic presence will be
+missed. She put her heart and soul into TUG and I'm delighted that she
+had time for romance (although rumour murmurs that email had an important
+part to play). Far from wishing to leave TUG, Charlotte may in the
+future be called on to help organise other conferences.
+
+
+\subsection{The problems restated}
+We therefore have three visible problems: that the former
+direction, embodied by Knuth (and to some extent,
+Lamport) is no longer there; that the TUG Executive
+apparently went absent without leave; and that TUG is
+going through a period of financial austerity. I do not
+believe that any of these are reasons to despair. In the
+first case, try to remember why Knuth wrote \TeX\ in the
+first place. Recall that he only expected it to be used
+by himself and his secretary; that it is a software tool
+to assist the production of {\sl The Art of Computer
+Programming}. Yes, it took on a life of its own, like
+some creation by Frankenstein. (I would be prepared to
+argue that the analogy may be pursued further, but only
+after a few beers\dots) The matter of the Executive was
+serious, but it has been evident for some years that the
+mechanism by which the executive are elected and the
+remainder of the Board appointed, needed substantial
+overhaul. It may have been adequate in the days when TUG
+membership was a small and almost exclusively from the
+United States, but it does not suit a large international
+organisation. Apart
+from the four elected office bearers, the only other
+elected members of the Board were the `International' Vice
+Presidents (presumably elected by their own groups). The
+title of Vice President is more an honorific one than one
+which actually bestows obligations on the bearer. So what
+I am saying is that this was a crisis that was bound to
+occur, by the very nature of the Board structure.
+
+And
+lastly, the financial problem: it is unfortunate that
+this should occur at a time when TUG should be extending
+its services to its membership, and should be more
+vigorously pursuing fields like publishing. Still, as
+Joachim Lammarsch of \dante\ and and Bernard Gaulle of
+\GB\ have both pointed out, much can be done with volunteer
+help. TUG seems to lack the skills to mobilise volunteers.
+Perhaps the fact that we have paid, professional, office
+staff has encouraged us, the membership, to assume that we
+are paying to have things done and therefore need not lift
+our hands to help. Clearly this is not a fair statement,
+since so many TUG members do give selflessly of their
+time and energy to TUG and \TeX\ related activities.,
+But note that the financial position is not as bad as once
+thought. Despite David Ness' scaremongering about a purported
+\$50,000 loss, attributable to the breakdown between the Executive and
+the remainder of the Board, close attention to the accounts will reveal
+not only that there is currently only a small projected loss for 1991,
+but that a sum of \$44,000 is listed in the 1990 accounts as `expense
+associated with departure of ED'. I am unable to find any evidence
+for Ness' claims. The office staff, and especially Ron Whitney are to be
+commended for their close attention to financial details over the last
+year.
+
+\subsection{A ray of hope}
+In March a board meeting was convened in Dedham. Despite the absence
+of Nelson Beebe, and most of the rest of the Executive
+and Finance committes, this was a very
+successful meeting which helped to repair most of the
+damage done by the Executive's abrogation of their
+responsibilities. This meeting has been reported to some extent in
+{\sl \TeX\ and TUG News}. I took it as a mark of some progress that
+even the dour Bernard Gaulle appeared to return more confident that TUG
+has a future. Among the plans adopted were that (at last) the Long Range
+Planning Committee will get under way; that a Publications Committee
+will review the current TUG publications and make proposals for new
+publications, which include a more informal newsletter (TTN), and that
+the voting procedure and the board structure will be overhauled. Much
+other work was done on the infrastructure of the Board, laying a useful
+foundation for the future. Reading between the lines much of the success
+of this board meeting seems to have lain in the absence of the old
+rearguard and the active, positive participation and preparation of
+people like Hope Hamilton and Christina Thiele who ensured that the
+meeting ran smoothly, was planned, and tackled the serious issues.
+Equally, the real support of the TUG office staff was an essential
+component.
+
+\subsection{Since the Annual Meeting}
+The fruits of these changes began to be reaped at the Annual Meeting at
+Dedham. The Long Range Planning Committee spend a lot of time together,
+immediately before, and during the meeting, and started to lay out a
+far reaching set of proposals which will be gathered together and
+published in some form by the end of the year. Similarly, the
+Publications Committee drew up the beginnings of a comprehensive
+overhaul of TUG's approach to publications. Other active committees
+included the Site Selection Committee for the 1992 meeting. The other
+major issue was the mechanics of the election of next year's Board. The
+Board is to be reduced in size to the President and 15 elected members,
+plus the 5 existing International Vice Presidents and the three
+Honorary members. The 15 elected Board members will be elected by the end
+of this year. If you are a TUG member, you will have received details of
+the election procedure. The only slightly awkward note was that the
+President, who will in future years be elected by postal ballot, was in
+this one special instance elected by the existing Board, but only for
+the year 1992. In this way, some continuity is ensured. It was thought
+to be unwise to have an entirely new Board {\it and\/} President. I find
+it incredibly ironic that as one of those who sought greater involvement
+of the membership in the selection of the Board and the President, I
+should now be in the position of having been elected to the post of
+President of TUG by the Board. I'm going to try to live with the irony
+(at least for one year).\looseness-1
+
+\subsection{Conclusion}
+Despite the problems I believe that \TeX\ is sufficiently
+important that joining TUG and participating in it
+actively is a small way of expressing my joy, gratitude and
+delight. It seems strange to me that we exult in the
+public domain aspect of \TeX\ and yet whinge over the
+paltry sums needed to join TUG, or fail to return something to the
+general good. If we believe that TUG needs changing, it seems more
+constructive to participate and try to change it, rather than standing
+on the sidelines and bemoaning its current state. We do not
+improve TUG by standing aloof, or by creating
+rival organisations. The Board has instigated some
+radical changes which I believe will ensure the long term
+future of the organisation. I am especially confident
+that the incoming Board will contain new blood which will
+invigorate, brim over with new ideas and spark us all
+with their enthusiasm. I look forward enthusiastically to
+my period as President.\author{Malcolm Clark}}
diff --git a/info/digests/texline/no13/newtwo-column b/info/digests/texline/no13/newtwo-column
new file mode 100644
index 0000000000..fc32d1fa60
--- /dev/null
+++ b/info/digests/texline/no13/newtwo-column
@@ -0,0 +1,166 @@
+
+%\hoffset=-0.1in
+%\voffset=-2pc
+%\raggedbottom
+%\hsize=39pc %\vsize=59pc
+%\maxdepth=2.2pt \parindent=1pc
+%\vsize=720pt
+%\hsize=6.5in
+%\baselineskip12pt
+%\parskip0pt
+%\parindent1em
+%\hfuzz1.5pt
+%\tolerance2000
+
+%\hyphenation{Post-Script}
+% Page layout
+\newdimen\pagewidth \newdimen\pageheight \newdimen\ruleht
+\newdimen\colwidth \newdimen\bigcolheight\newdimen\gutter
+\gutter=0.4in
+%\colwidth=3.1in%19pc
+\colwidth=\hsize
+\advance\colwidth by-\gutter
+\divide\colwidth by 2\relax
+%\bigcolheight=1450pt%120pc
+\bigcolheight=\vsize
+\advance\bigcolheight by\bigcolheight
+\advance\bigcolheight by 10pt
+\pagewidth=\hsize \pageheight=\vsize \ruleht=0pt%.5pt
+\abovedisplayskip=6pt plus 3pt minus 1pt
+\belowdisplayskip=6pt plus 3pt minus 1pt
+\abovedisplayshortskip=0pt plus 3pt
+\belowdisplayshortskip=4pt plus 3pt
+
+\newinsert\botins
+\def\afoot{\strut\egroup}
+\def\botpic#1{\par
+ \insert\botins\bgroup\hsize=\pagewidth
+ \offinterlineskip
+ \interlinepenalty100 \let\par=\endgraf
+ \leftskip=0pt \rightskip=0pt
+ \splittopskip=10pt plus 1pt minus 1pt \floatingpenalty=20000
+ \medskip{#1}\medskip\egroup}
+\skip\botins=12pt plus 2pt minus 4pt % space added when footnote is present
+\count\botins=2000 % footnote magnification factor (1 to 1)
+\dimen\botins=36pc % maximum footnotes per page
+
+\def\toppic#1{\par
+ \insert\topins\bgroup\hsize=\pagewidth
+ \interlinepenalty100 \let\par=\endgraf
+ \offinterlineskip
+ \leftskip=0pt \rightskip=0pt
+ \splittopskip=10pt plus 1pt minus 1pt \floatingpenalty=20000
+ \medskip{#1}\medskip\egroup}
+\skip\topins=12pt plus 2pt minus 4pt % space added when footnote is present
+\count\topins=2000 % footnote magnification factor (1 to 1)
+\dimen\topins=36pc % maximum footnotes per page
+
+\newinsert\margin
+\dimen\margin=\maxdimen
+%\count\margin=0 \skip\margin=0pt % marginal inserts take up no space
+
+\newif\iftitle
+\def\titlepage{\global\titletrue} % for pages without headlines
+%\def\rhead{{}}
+
+\def\leftheadline{\hbox to \pagewidth{%
+ \vbox to 10pt{}% strut to position the baseline
+ \sl\rhead\hfil\lhead % running head flush left
+ }}
+\def\rightheadline{\hbox to \pagewidth{%
+ \vbox to 10pt{}% strut to position the baseline
+ \sl\rhead\hfil\lhead % running head flush left
+ }}
+
+\def\onepageout#1{\shipout\vbox{ % here we define one page of output
+ \offinterlineskip % butt the boxes together
+ \vbox to 2pc{ % this part goes on top of the 44pc pages
+ \iftitle % the next is used for title pages
+ \global\titlefalse % reset the titlepage switch
+ \setcornerrules % for camera alignment
+ \else\ifodd\pageno \rightheadline\else\leftheadline\fi\fi
+ \vfill} % this completes the \vbox to 3pc
+ \vbox to \pageheight{
+ \ifvoid\margin\else % marginal info is present
+ \rlap{\kern31pc\vbox to 0pt{\kern4pt\box\margin \vss}}\fi
+ \ifvoid\topins\else % top note info is present
+ \hrule height\ruleht width\pagewidth \kern-\ruleht \kern3pt
+ \unvbox\topins
+ \vskip\skip\topins \kern-3pt
+ \hrule height\ruleht width\pagewidth \kern-\ruleht \kern3pt
+ \vskip\skip\topins \kern-3pt
+ \fi
+ #1 % now insert the main information
+ \vfill
+ \ifvoid\botins\else % bot note info is present
+ \vskip\skip\botins \kern-3pt
+ \hrule height\ruleht width\pagewidth \kern-\ruleht \kern3pt
+ \unvbox\botins
+ \vskip\skip\botins \kern-3pt
+ \hrule height\ruleht width\pagewidth \kern-\ruleht \kern3pt
+ \fi
+ \boxmaxdepth=\maxdepth
+ } % this completes the \vbox to \pageheight
+ }
+ \advancepageno}
+
+\def\setcornerrules{\hbox to \pagewidth{\vrule width 1pc height\ruleht
+ \hfil \vrule width 1pc}
+ \hbox to \pagewidth{\llap{\sevenrm(page \folio)\kern1pc}%
+ \vrule height1pc width\ruleht depth 0pt
+ \hfil \vrule width\ruleht depth 0pt}}
+
+\output{\onepageout{\unvbox255}}
+
+\newbox\partialpage
+\newdimen\savesize
+\def\begindoublecolumns{\begingroup
+ \savesize=\vsize
+ \output={\global\setbox\partialpage=\vbox{\unvbox255\bigskip}}\eject
+ \output={\doublecolumnout} \hsize=\colwidth \vsize=\bigcolheight
+ \advance\vsize by -2\ht\partialpage
+ \advance\vsize by -2\ht\botins
+ \advance\vsize by -2\ht\topins
+ \pagegoal=\vsize}
+\def\enddoublecolumns{\output={\balancecolumns}\eject
+ \global\output={\onepageout{\unvbox255}}
+ \global\vsize=\savesize
+ \endgroup \pagegoal=\vsize}
+
+\def\doublecolumnout{%
+% \splitmaxdepth=\maxdepth
+ \dimen0=\pageheight
+ \advance\dimen0 by-\ht\partialpage
+ \advance\dimen0 by-\ht\botins
+ \advance\dimen0 by-\ht\topins
+ \splittopskip=\topskip
+ \setbox0=\vsplit255 to\dimen0
+ \setbox2=\vsplit255 to\dimen0
+ \onepageout\pagesofar
+ \global\vsize=\bigcolheight
+ \unvbox255 \penalty\outputpenalty}
+\def\pagesofar{\unvbox\partialpage
+ \wd0=\hsize \wd2=\hsize \hbox to\pagewidth{\box0\hfil\box2}}
+\def\balancecolumns{\setbox0=\vbox{\unvbox255} \dimen0=\ht0
+ \advance\dimen0 by\topskip \advance\dimen0 by-\baselineskip
+ \divide\dimen0 by2 \splittopskip=\topskip
+ {\vbadness=10000 \loop \global\setbox3=\copy0
+ \global\setbox1=\vsplit3 to\dimen0
+ \ifdim\ht3>\dimen0 \global\advance\dimen0 by1pt \repeat}
+ \setbox0=\vbox to\dimen0{\unvbox1}
+ \setbox2=\vbox to\dimen0
+% {\unvbox3}
+ {\dimen2=\dp3 \unvbox3 \kern-\dimen2 \vfil}
+ \global\output={\balancingerror}
+ \pagesofar}
+\newhelp\balerrhelp{Please change the page into one that works.}
+\def\balancingerror{\errhelp=\balerrhelp
+ \errmessage{Page can't be balanced}
+ \onepageout{\unvbox255}}
+
+
+
+
+
+
+
diff --git a/info/digests/texline/no13/obit b/info/digests/texline/no13/obit
new file mode 100644
index 0000000000..86007c6845
--- /dev/null
+++ b/info/digests/texline/no13/obit
@@ -0,0 +1,99 @@
+\hrule height1pt depth 1pt
+\medskip
+\centerline{\bf Catherine Mary Booth}
+\vskip-5pt
+\begindoublecolumns\noindent
+Cathy Booth died on July 27th, 1991. She had known that
+she had cancer of the kidneys for just about a year. She
+had undergone a major operation last summer, but sadly it
+appears that the extensive surgery performed at that time
+was too late to control the cancer. Nevertheless, for the
+last year she fought the disease consistently,
+cheeerfully and resolutely. She was determined that she
+should not be treated any differently, despite the gradual
+decline in mobility and energy which ensued. Her
+undiminished enthusiasm was evident to those who met her
+at last year's TUG conference at Cork last September, and
+at the various meetings she continued to attend until her
+second major operation earlier this year. But between
+those two events she pursued an active social
+life, with at least two skiing trips (although
+she was unable to ski by the second). Ultimately she was
+confined to a wheel chair and moved into a hospice at
+Tiverton, near her Exeter home, in the hope that her house
+would be modified to allow her to return to it and
+continue her life normally. However, this was not to be,
+and she was to die at the hospice, with most of her close
+family at her bedside. Mercifully she died both peacefully
+and gracefully.\looseness1
+
+Cathy was born on June 19th, 1952. She attended Exeter
+University, where she completed a BSc in Geography. She
+clearly fell in love with Exeter, and spent the rest of
+her life in and around it. She spent some time after
+University working on Exmoor, and later had her own
+business as a furniture restorer. But in 1984, after a
+period in hospital, where she began to do some computing,
+she started a post as Computing Development Officer back at
+Exeter University. One of her first responsibilities was
+\TeX. She attended the IUSC conference on Typography and
+Design Methods for Computer Typesetting held at Oxford
+University at Easter 1985. Following that meeting, she
+attended a \TeX\ course held at Imperial College. Her
+involvement and concern with \TeX, and more generally with
+Electronic Publishing grew consistently from that time.
+
+She attended many of the \TeX\ conferences in Europe (in
+Strasbourg, Karlsruhe and Cork), as well as TUG meetings
+in North America (in Montreal and Stanford), and
+some of the GUTenberg meetings in Paris. But it will be
+the \TeX88 conference held at Exeter University with
+which she may be best remembered to many in the \TeX\
+world. Cathy was the local organiser for this meeting: the
+huge success of the meeting must be atrributed in no small
+way to her vivacity and personal magnetism. But this is to
+underestimate the huge attention to detail which she
+undertook in the months running up to the conference. This
+ensured the smooth running of the events: in particular,
+the affectionately remembered excursion from Exeter to
+Totnes which included a steam train and a river cruiser.
+
+Cathy was an excellent teacher of \TeX. She taught a
+number of TUG courses on Beginning and Intermediate \TeX,
+and other \TeX\ courses at Exeter University. At the
+University, she also developed courses which united her
+skill with \TeX\ and her design abilities. This facility
+with design was just one side of more general artistic
+skills. This manifested itself more recently when she
+completed an Art History course, for which the results
+had appeared only a few days before she died.
+Characteristically, her exam results were excellent.
+
+Besides her other activities in \TeX\ and Electronic
+Publishing, she had been a member of the UK \TeX\ Users
+Group committee since the foundation of the group, as
+well as a member of the committee of the BCS Electronic
+Publishing Specialist Group. Those of us lucky enough to
+be on those committees with her will recall her
+very real contribution to the work of these groups. Again
+her range of innovative ideas, coupled with her down to
+earth attention to detail made a significant improvement
+to all that was achieved by those bodies.
+
+We have lost one of the best. \strut
+\enddoublecolumns
+\medskip
+\hrule height1pt depth 1pt
+\medskip
+\line{\hfill\vbox{\hsize0.65\hsize\noindent
+It has been proposed that a memorial
+fund be set up in memory of Cathy. The first rather
+tentative ideas are that this fund would help to
+perpetuate her memory by being available to support \TeX\
+projects. The legal aspects are currently being
+explored. I hope that many of Cathy's friends and
+colleagues will be eager to contribute to this and will
+ensure that this proposed memorial truly reflects the
+place that she occupied in the whole
+community.\author{Malcolm Clark}}\hfill}
+\vfill
diff --git a/info/digests/texline/no13/playpen b/info/digests/texline/no13/playpen
new file mode 100644
index 0000000000..346fb6b982
--- /dev/null
+++ b/info/digests/texline/no13/playpen
@@ -0,0 +1,169 @@
+\title{Electronic Publishing -- Out of the Playpen}
+\noindent
+The third annual conference of the
+BCS Electronic Publishing Specialist Group took place at Exeter
+College, Oxford on 21--22nd March. It was a stimulating event.
+
+This two-day meeting must be one of the best amongst many that
+bring together people with varied backgrounds to take a wide look
+at what is happening in the application of computer-based
+techniques to the dissemination of information. An awareness that
+information becomes knowledge only through concern by authors,
+editors, producers and/or publishers for methods was apparent in
+Oxford; philosophical issues and a historical perspective were
+perhaps encouraged amongst the Dreaming Spires. Fine detail was
+not overlooked however.
+
+Formal sessions, and the equally important times in between,
+provided face-to-face communications for over fifty highly
+motivated delegates from all levels in many areas of information
+handling. The environment wherever delegates assembled could
+be said to be laden with valuable interchanges which not
+only focused on all aspects of electronic page make-up, which is
+the solid base of the Group's interests, but also encompassed
+commercial realities and futurology.
+
+
+One comment overheard that could be said to add a perspective (or
+two?) concerned the desirability or otherwise of slanting the
+familiar male\slash female symbols in italic typefaces in an \SGML\
+environment! Aside from such detail, Electronic Publishing
+specialists must always be concerned with the hardware and
+software employed as well as the continuing process of
+standardisation, usability and ever wider applications.
+Presentations on diverse topics within one meeting in this
+subject can always be brought into focus by very interesting
+speakers and this meeting excelled in this too; throughout, the
+sub-theme of `coping with change' was addressed.
+
+
+The conference was attended by delegates from a variety of
+organisations, including universities, publishers, the Finnish
+State Computer Centre, IBM, DEC and the Bible Society.
+The first (pre-conference) session, especially for those arriving
+on the Wednesday evening, entitled {\sl Choosing a Typeface} was given by
+Paul Luna, Head of Art and Design, Arts \& Reference Division, Oxford
+University Press. At the frontiers of innovation in a 500-year
+old organisation, Paul re-designed the range of Oxford
+Dictionaries in Monotype Nimrod from 1984, designed the Oxford
+Shakespeare Volumes in 1986, and the Revised English Bible in
+1990. His talk focused on choosing typefaces for the redesigned University
+Gazette and he provided a great deal of insight into why a typeface does
+(or does not look) right in a particular context.
+
+The first full day started with a welcome address by
+Professor Sir Roger Elliott, Chief Executive of Oxford University
+Press. A theoretical physicist, Sir Roger noted that
+three other speakers shared his background. By touching upon
+aspects of intellectual property protection and fair reward to
+publishers for adding value to information, this eminent
+scientist set the scene for all speakers, in suitably authoritative style
+and in the context of OUP's own wide ranging electronic
+publishing achievements. Delegates enjoyed
+further opportunity to meet several of OUP's electronic publishing
+specialists
+and see software and CD-ROM based products at a sherry
+party sponsored by `The Press' before the conference dinner on the
+same evening.
+
+
+
+
+Following the opening address, Eric van Herwijnen gave his views
+on {\sl \SGML\ in the Real World} . Eric is from CERN, Geneva, where
+he is the head of text processing and is responsible for
+scientific document production (CERN publishes 1000 documents a
+year). By answering the questions `what is?, who uses? and how to
+start, with \SGML', this speaker took the assembled experts into the
+library of the future from which users select on-line and print
+the page as they perceive a need for it. The recently much
+enlarged Elsevier Science Publishers would be expected to have
+views on this concept, and Nico Poppelier from that company then gave a
+presentation on {\sl \SGML\ and \TeX\ in Scientific Publishing} from
+his standpoint of author submission of manuscripts using \TeX\
+and conversion of it and word-processing formats to and from
+\SGML.
+
+\TeX ies may have been surprised and pleased by the prominence given to
+\TeX\ in these first three presentations. It may be no coincidence that
+all three are (or were) physicists.
+
+Barbara Lloyd, a publishing consultant with DEC, talked directly
+about {\sl Electronic Publishing Out of the Playpen}
+from the large user systems viewpoint. It was good to learn that
+DEC practice what they preach, even to the extent of putting user
+manuals on CD-ROM. An exploration of the possibilities of significantly
+improving communication by applying latest technology
+included an intriguing `book-reader' in `windows'.
+
+The next speaker was Edward James, Lecturer and Consultant in Educational
+Computing at Imperial College, (also a Director of Juniper
+Systems Partnership Ltd). In his talk {\sl Publishing without
+Paper} he considered environmental and other failings of existing
+paper-based publishing methods, and went on to describe (and sell
+a sampler for \quid1.00) his computer package which enables authors
+who are inexperienced in computing to add value to their
+paperless publications. His `paper' paper, lacking the hypertext, was
+also given out.
+
+The last talk of the first day was given by a first-class public
+speaker, Tony Feldman, whose {\sl The Electronic Book Arrives} examined
+the origins and rapid growth of hand-held electronic reference
+publishing (palmtop computers), and assessed the impact of these
+devices on traditional publishing and looked ahead to the first
+electronic books on optical disk. The Japanese are coming!
+
+The dinner in Hall was all that such an occasion should be, good
+food, wine and company with a sparkling (despite travelling from
+the Gulf War that very day) speaker -- Michael Bywater, who writes for
+Punch and MacUser. The guest's journalistic skills were evident throughout
+his very amusing and poignant speech, as well as in his write-up
+of the event in MacUser (5~April 1991, p.~106). Delegates were
+made fully aware of the EP expert's responsibility by the
+punchline `the history of culture is the history of publishing'.
+
+
+
+The first presentation on Friday was by Jacques Andr\'e of
+INRIA/IRISA of the University of Rennes, one of the initiators of
+the DIDOT project to coordinate training in numerical
+typography. Jacques' talk on {\sl The DIDOT Project and Digital
+Typography in Europe} focused on the state of the art of digital
+typography, explaining the need to bring together type designers
+and computer people, as well as giving some fascinating examples of
+what you can do with typefaces if you know how to manipulate
+\PS\ (and if you want to!).
+
+Following this, Paul Bacsich of the Open University, where he is
+Senior Project Manager in Information Technology and Head of the
+Electronic Media Research Group, spoke about {\sl An Encyclopaedia
+of European Characters}, speaking of the need to clarify what
+exactly a character was. He defined eleven species including
+Roman letters, punctuation, maths and scientific, modern Greek as
+well as the more familiar characters, and
+discussed some of the problems involved in creating the encyclopaedia and in coding and accessing
+the characters.
+
+{\sl Achieving the Automatic, the Invisible, Hyphen} was discussed by
+Ronald McIntosh of Computer Hyphenation Ltd. Ronald, together
+with David Fawthrop, has developed the Hyphenologist program which allows
+proper word division in 40 languages. In the past British hyphenation has
+generally been based on etymology, but is now mainly following the US
+practice of using the phonetic method. Ronald explained how the various
+algorithms work, with extensive examples.
+
+The last presentation of the conference was given by Ali Assam of
+Diwan. Talking about {\sl Distributed Newspaper Publishing} he
+explained how in 1988 Diwan became the system integrator for the
+world's first broadsheet to be produced, edited and remotely
+printed using microcomputers, and discussed the application of
+Diwan's pre-press and information management system products
+using low cost computer and communications technology.
+The use of \PS\ as a medium for transmitting made-up pages
+around the world to be printed in many remote sites was
+yet another reminder of how developing technology makes information
+more accessible.
+
+Altogether a most useful and interesting conference, held in
+beautiful surroundings.
+\author{Peter Ashby and Anna Duckworth}
diff --git a/info/digests/texline/no13/rhead.txt b/info/digests/texline/no13/rhead.txt
new file mode 100644
index 0000000000..c5802b598f
--- /dev/null
+++ b/info/digests/texline/no13/rhead.txt
@@ -0,0 +1,859 @@
+% David Rhead
+% (JANET: d.rhead@uk.ac.nottingham.ccc.vme)
+%
+
+\begingroup
+\def\Blatex{{\bf L\kern-.30em\raise.3ex\hbox{\scb A}\kern-.15em\TeX}}
+\def\Bbibtex{{\bf B{\scb IB}\kern-.2em\TeX}}
+\def\ttbackslash{{\tt\char'134}}
+\def\bs{\tt\char'134}
+\def\cite#1{[#1]}
+\def\label#1{{\it #1}}
+\let\ref\relax
+\let\protect\relax
+\def\hline{\noalign{\hrule}}
+\def\item#1{\par\hangindent1em\hangafter1{\noindent
+\hbox to 1em{\hfil#1\hfil}}}
+\def\itemitem#1{\par\hangindent2em\hangafter1{\noindent
+\hbox to 2em{\quad\hfil#1\hfil}}}
+\def\bi{\item{$\bullet$}}
+\def\rtr{$\triangleright$}
+
+\def\description{\begingroup
+\def\item[##1]{\par\hangindent20pt{\noindent\bf##1}}}%
+\def\enddescription{\endgroup}
+\def\section#1{\medskip\goodbreak\leftline{%
+\let\BibTeX\Bbibtex\let\LaTeX\Blatex
+\bf#1}\par\noindent\ignorespaces}
+\def\subsection#1{\smallskip\goodbreak\leftline{$\bullet$\fib#1}\par
+\noindent\ignorespaces}
+\def\subsubsection#1{\smallskip\goodbreak\leftline{\fib#1}\noindent\ignorespaces}
+
+
+\title{How might \LaTeXbf3 deal}
+\centerline{\bf with citations and reference-lists?}
+\section{I Introduction}
+Since there are now plans for a new version of \LaTeX\
+\cite{1,2}, this may be a
+good time to consider how a future version should deal with citations and
+reference-lists.
+
+My viewpoint is that of an advisor to authors who use \LaTeX\ 2.09.
+I am often in the position of having to decide whether \LaTeX\
+acts inappropriately or whether an author is asking for something
+inappropriate. Often I have the impression that \LaTeX\ sometimes
+makes it unnecessarily difficult for people to comply with the conventions that
+are standard in `academic publishing'.
+
+In making the suggestions that follow, I do realise that it's easier for me
+to suggest that the volunteers developing \LaTeX3 might provide some new
+facilities than it is for a volunteer to find time to do the work!
+I assume that the reader is familiar with the relevant sections of
+Lamport's {\sl\LaTeXsl, A Document Preparation System}.
+
+\section{II Conventions to be supported}
+\subsection{II(i) Citation schemes}
+In mainstream publishing
+\cite{3,4,5,6,7,8,9,10,11,12}, there seem to be three basic schemes for
+citations and the corresponding reference-lists:
+{\description
+\item[reference by number] In this scheme, citations are
+normally numbered in order of first citation. In particular, `order of first
+citation' is used by over 300 biomedical journals \cite{8,9}, and is specified
+in the ISO standard \cite{10}. (Thus, in \BibTeX\ terms, the usual
+numbering sequence is that given by {\tt unsrt}.) The number is used as a
+`label' in the reference-list.
+\item[author-date]~There are two main forms of
+citation, depending on whether
+ or not the cited author's name occurs naturally in a sentence. In the
+ first case, the citation is of the form \hbox{`\ \dots\ (1972)
+ \dots\ '}, whereas in the second case it is of the form \hbox{`\ \dots\
+ (Crane, 1972) \dots\ '}. There are no `labels' in the
+ reference-list, which is arranged in alphabetical order of authors'
+ surnames (with supplementary rules for `tie-breaking').
+\item[short form]~The `short form' scheme is often used when citations
+ occur in footnotes. Typically, the first citation (or the first
+ citation in the current chapter) gives a fairly full reference but
+ subsequent citations use a short form. The `short form' may be
+ introduced within the first citation, or given in a table of
+ abbreviations. There are no `labels' in the reference-list,
+ which may be subdivided by `type of cited document'.
+ The scheme is common in the humanities, but also seems to be used by
+ some software-houses when referring to their own publications (see, for
+ example, \cite{13}).
+
+\enddescription}
+
+\noindent
+I think it is desirable that \LaTeX\ should provide explicit support for
+all three citation schemes, in order to make it straightforward to achieve the
+effects that people routinely achieve with traditional publishing procedures.
+
+Notice that:
+\item{\rtr}It is not, in general, possible to convert a document from one
+scheme
+ to another (for example, from `reference by number' to author-date)
+ automatically. Some re-writing is required.
+\item{\rtr}The number of items of information that need to be available
+ differ between the schemes. For a `reference by number'
+ citation, it is only necessary to keep track of one item
+ (the number), whereas for the other schemes it is necessary to keep
+ track of more than one item (that is, the author and the date, or the
+ `fairly full form' and the `short form')
+ so that they can be used separately.
+\item{\rtr}Occasionally, two different schemes may be used in parallel
+ within the same document. (For example, in \cite{13},
+ a software-house seems to use `short form' when citing
+ its own publications, but author-date when citing other publications.)
+
+\noindent
+Thus, it seems to me that the three schemes are best regarded as logically
+distinct.
+
+However, within a particular scheme, there are variations of punctuation, etc.,
+that can be regarded as matters of `house style'.
+For example, some journals that have adopted a `reference by number'
+scheme use bracketed numerals for citations, while others use superscripts.
+Such variations can be accommodated by differences between style files.
+
+\subsection{II(ii) Additional references}
+In addition to a list of `works cited', some documents
+have an additional reference-list that specifies `further reading'
+or `all sources consulted' (see \cite{5,~pp182 \& 192}),
+\cite{8,~p40} and \cite{8,~p22}). There needs to be
+some provision for typesetting such additional lists.
+
+
+\section{III Deficiencies in \LaTeX\ 2.09}
+\subsection{III(i) Citations}
+When used in conjunction with \BibTeX\ and |\bibliographystyle{unsrt}|,
+\LaTeX\ 2.09 makes a good job of organising citations (and sorting the
+corresponding reference-list) according to the `reference by number'
+scheme as required by many journals.
+
+Generally, however, \LaTeX\ 2.09 does not provide the breadth or depth
+of facilities needed to support the variety of requirements for
+mainstream publishing:
+
+\item{\rtr}It is unfortunate that the `reference by number' sequence obtained
+ most naturally by the do-it-yourself-er \cite{1,~p73} from
+ \LaTeX\ 2.09 (`order of appearance within {\tt thebibliography}')
+ is unlikely to be what the do-it-yourself-er's journal-editor requires
+ (which will usually be `order of first citation'). The
+ do-it-yourself-er is given no warning (either in the manual or by
+ the software) that sorting is likely to be needed.
+\item{\rtr}Although one can use style-options such as {\tt apalike} and
+ {\tt aaai} to re-define |\cite| and {\tt thebibliography}
+ for an author-date scheme, there are many obstacles placed in the
+ user's way:
+ \itemitem{$\star$}The existence of the style-options is not documented
+in
+ \cite{1}.
+ \itemitem{$\star$}If one finds a style-option in a (software) archive,
+it
+ may need modification to produce the precise effect required.
+ \itemitem{$\star$}It is not obvious how one should refer separately to
+two
+ items (author and date) supplied via a |\bibitem| argument
+ originally designed for one. The do-it-yourself-er might
+ have to study style files such as {\tt aaai.sty} and {\tt bbl}
+ files such as those produced by {\tt aaai-named.bst} to
+ deduce how to do this.
+\item{\rtr}The `short form' scheme seems unsupported.
+\item{\rtr}At certain points in a document, an author my need to cite
+ several works at once. It may be necessary to specify a
+ page (or section, etc.) for each work. For instance,
+ \cite{6,~p404} suggests references of the form
+ `(Kelley 1896a, 10; Kelley 1896b; Kelley 1907, 3)'.
+ This is not easy in \LaTeX\ 2.09, since |\cite|'s
+ optional argument applies to the citation as a whole. The
+ author cannot supply a separate `optional argument'
+ for each work. (By contrast, {\sf EndNote}'s analogous facilities
+ \cite{15,~p58} seem to allow each individual work
+ to be given its own `additional text'.)
+\item{\rtr}It does not seem easy to use different schemes in parallel
+ within the same document. If |\cite| and
+ {\tt thebibliography} are defined as required for one scheme,
+ they will usually be unsuitable for any other.
+
+\subsection{III(ii) Additional references}
+As stated in section \ref{II(ii)} an author may need to
+typeset a list of `further reading' etc., in addition to
+the usual list of `works cited'.
+
+If using the {\tt thebibliography} environment from one of \LaTeX\
+2.09's standard styles for such additional references, an author will be
+faced with the following problems:
+\item{\rtr}the title will be the same as that for the list of `works
+ cited', namely `References' for {\tt article} and
+ `Bibliography' for {\tt report} and {\tt book}
+\item{\rtr}the `labels' (which may be appropriate in the list
+ of `works cited', particularly for the `reference
+ by number' scheme) will also appear in the
+ additional list (where they are inappropriate), because
+ both lists use the same definition of |\bibitem|
+\item{\rtr}by default, the `labels' will not be unique, since
+ the `works cited' list and the `additional references'
+ list will both be numbered from one
+\item{\rtr}it will be necessary to supply dummy {\it cite-key\/}s,
+ purely to satisfy the syntax required for a |\bibitem|.
+
+\subsection{III(iii) Other problems}
+The definitions of the {\tt thebibliography} environment in \LaTeX\
+2.09's standard styles:
+\item{\rtr}issue either a |\section*| or a |\chapter*| command,
+ using a {\it heading} of `References'for {\tt article}
+ and `Bibliography' for {\tt report} and {\tt book}
+\item{\rtr}set {\it left-head\/} and {\it right-head\/} to either
+ `REFERENCES' or `BIBLIOGRAPHY'
+\item{\rtr}do not arrange for a table-of-contents entry.
+
+\noindent
+These definitions can cause problems when the {\it heading}, etc.\
+supplied by the standard style is inappropriate, or when a table-of-contents
+entry is desired.
+Admittedly, anyone who doesn't like the standard styles is free to
+take copies of the style files and modify them to suit their requirements.
+However, I have the impression that:
+\item{\rtr}among people who are competent to modify style files,
+ modification of these aspects of the standard styles is `the
+ rule' rather than `the exception'
+\item{\rtr}those \LaTeX\ users who aren't particularly computer-literate
+ find the whole business mysterious, and seek out support staff
+ who have to modify these aspects of the style files for them.
+
+\noindent
+Overall, this seems to be an area where \LaTeX\ 2.09 is failing to
+`free people from formatting concerns to allow them to
+concentrate on writing'\cite{1,~p8}.
+
+An associated problem is that modified style files may no longer be
+compatible with standard utilities such as {\tt lablst}.
+
+\section{IV Introduction of new facilities}
+It has been decided \cite{2} that \LaTeX3
+ will be compatible with \LaTeX\ 2.09 input files. Thus, in particular,
+\LaTeX3 must define |\cite| and |thebibliography| so that they
+have the same effect on \LaTeX\ 2.09 input files as the \LaTeX\ 2.09
+definitions do. This implies that it would be difficult for \LaTeX3 to
+(for example) define |\cite| so that there can be an optional argument
+for each work in a multiple citation and define |\bibitem| so that it can
+have an `author' argument and a `date' argument.
+
+It therefore seems best to provide duplicates of the \LaTeX\ 2.09 facilities
+in \LaTeX3 (for `backwards compatibility') but to attempt to
+provide new commands/environments in parallel so as to provide the required
+functionality. The new facilities would be regarded as the `normal'
+facilities, would be described in the body of the successor to \cite{1},
+ and
+would be the natural choice for new users. The old facilities would be
+regarded as `deprecated' and relegated to an appendix of the successor
+to \cite{1}.
+
+Thus we can have both backwards compatibility and improved facilities
+for the future.
+
+\section{V Division of labour}
+\subsection{V(i) Details needed for document `as a whole'}
+The three basic citation schemes mentioned in section \ref{II(i)}
+determine certain details of a document `as a whole'. For each
+citation, there must be an entry in a reference-list. Each entry in
+the relevant reference-list must have associated information that can be
+used in citations.
+
+\subsection{V(ii) Details needed for reference-list, etc.}
+There are a lot of other details that need to be resolved.
+
+The information within each reference-list entry will probably need
+formatting according to certain rules of `house style'.
+The information given in citations needs organising in a consistent way
+(particularly for the `short form' scheme).
+
+Different people may want to assemble their reference-lists in different ways.
+Some people may wish to `do it themselves' \cite{1,~p73} from
+a physical card-index, while some may prefer to use \BibTeX\ to get details
+from a {\tt bib} file. In some disciplines,~proprietary systems such as
+{\sf EndNote} \cite{15} seem popular (because they help the user to search
+a database for literature to cite, as well as helping the user
+incorporate details of the literature into a document).
+Researchers may also wish to incorporate material obtained by searching
+details held on a {\sc cd-rom}.
+
+A reference-list generally needs sorting into a particular order. Since the
+list may occupy several pages, I assume that any sorting is best done outside
+\LaTeX, either by other software (e.g., \BibTeX) or manually by the author.
+
+\subsection{V(iii) \LaTeX\ and other software}
+It seems best to regard the movement of text-strings (e.g., an author's
+surname) within the `document as a whole' as a task that is distinct
+from the arrangement of details within the text-strings, and to assume a
+`division of labour' in which the former task is performed by \LaTeX\
+while the latter is performed by some other software or manually by the author.
+The `division of labour' between \LaTeX\ 2.09 and \BibTeX\ seems to set
+a good precedent.
+
+This division of labour will lead to modular software. Once the
+interface between a reference-list and the rest of the document has
+been defined,~people can use \LaTeX\ for the body of their document,
+but can:
+
+\item{\rtr}experiment with different software (\BibTeX, {\sf EndNote})
+ for formatting the details of their reference-lists
+\item{\rtr}enhance the other software (e.g., \BibTeX) independently
+ of enhancements to \LaTeX.
+\item{\rtr}lay their reference-lists out manually if they prefer.
+
+
+\section{VI \LaTeX3: A possible user interface?}
+\subsection{VI(i) Specifications and names}
+If the reasoning given in sections \ref{II}, \ref{IV}
+and \ref{V} is accepted, consideration needs to be given to
+the form that new commands/environments should take in order to support the
+three basic citation schemes, and to provide facilities for `additional
+references'. In particular, it will be necessary to choose
+names other than |\cite|, {\tt thebibliography} and |\bibitem| (since
+these names will be kept for the facilities provided for compatibility with
+\LaTeX\ 2.09).
+
+
+\subsection{VI(ii) Four sets of commands/environments}
+It seems to me that it would probably be convenient to have three sets of
+commands/environments for dealing with citations and the corresponding
+reference-lists, each set specifically designed to implement a particular
+citation scheme. Having three such sets gives scope for taking proper
+account of the peculiarities of each scheme, without having one scheme
+adversely affected by the peculiarities of another.
+
+To avoid the difficulties mentioned in section \ref{III(ii)},
+it might also be worth having a specific environment for
+`additional references'.
+
+\LaTeX3 might, for example, have commands/environments as specified
+in table 1.
+
+\topinsert
+\hsize6.5in
+\centerline{\offinterlineskip
+\vbox{\halign{\strut#\hfil&\hfil#\hfil&\hfil#\hfil&\hfil#\hfil&\hfil#\hfil\cr
+\hline
+ & Citation & Environment for & Entry in \cr
+ & & reference-list & reference-list \cr
+\hline
+Reference by number & \bs numcite & {\tt numrefs} & \bs numentry \cr
+\hline
+Author-date & \bs dcite
+ & {\tt adrefs} & \bs adentry \cr
+ & \bs adcite & & \cr
+\hline
+Short form & \bs firstcite & {\tt sfrefs} & \bs sfentry \cr
+ & \bs sfcite & & \cr
+\hline
+Additional references& -- & {\tt morerefs} & \bs moreentry \cr
+\hline
+{\it Analogue at 2.09} & \bs cite & {\tt thebibliography}
+ & \bs bibitem \cr
+\hline
+}}}
+\caption{Table 1: suggested specifications for commands\slash environments
+in \Blatex3}
+\bigskip
+\hrule height1pt depth1pt\bigskip \endinsert
+
+Here it is assumed that:
+\item{\rtr}|\numcite| and |\numentry| have {\it key-list} and
+ {\it cite-key} (respectively) as their only mandatory arguments.
+\item{\rtr}|\dcite| and |\adcite| have {\it key-list} as argument.
+ |\dcite| gives a citation of the form (1972),
+ while |\adcite| gives a citation of the form (Crane, 1972).
+ |\adentry| has three arguments: the {\it cite-key},
+ the author (e.g., Crane), and the date (e.g., 1972).
+\item{\rtr}|\firstcite| and |\sfcite| have {\it key-list} as argument.
+ |\firstcite| gives the form of citation to be used when a work
+ is first mentioned. |\sfcite| gives the short form
+ to be used in subsequent citations.
+ The arguments of
+ |\sfentry| might include: the {\it cite-key}, the form
+ of reference to be used at the first citation, and the short form
+ to be used subsequently.
+ Whereas |\numentry| and |\adentry| can `introduce'
+ the full reference (like |\item| starts a new item
+ \cite{1,~p166}), it may be better for |\sfentry|
+ to have the full reference as an argument, so that it can be used
+ as the default `form to be used at first citation'.
+
+\noindent
+Although it would be desirable for the successors to the `standard styles'
+to define facilities for all three citation schemes, other
+|\documentstyle|s need not define facilities for all three. For example,
+a journal that wants its authors to use the author-date scheme would supply a
+style file that only provides author-date facilities.
+
+\subsection{VI(iii) Further details}
+\subsubsection{Reference by number}
+The |\numcite| might take the form
+|\numcite{|{\it key-list}|}| and similarly, |\numentry| commands would be
+|\numentry{|{\it cite-key}|}|. Notice that, since |\numentry|
+is specifically designed for `reference by number', there is no need to
+allow an optional {\it label} argument like that for |\bibitem|.
+
+To conform to the ISO specification \cite{10}, the successors to the
+`standard styles' would arrange for |\numcite| to give a citation of the form
+(24) and for |\numentry| to give a reference-list entry of the form
+\description
+\item[{\rm 24.}] {\sc Crane, D.} {\it Invisible colleges.} \dots
+\enddescription
+
+
+Perhaps \LaTeX3 could use the {\tt aux} file to refine an initial estimate
+of the width of the final |\numentry|'s `label', so that the
+do-it-yourself-er wouldn't need to supply a {\it widest-label\/} argument.
+
+\subsubsection{Author-date}
+The commands |\dcite|, |\adcite| and |\adentry| might
+be defined to have the forms |\dcite{|{\it key-list}|}|,
+|\adcite{|{\it key-list}|}| and
+|\adentry{|{\it cite-key}|}{|{\it author}|}{|{\it date}|}|.
+The {\tt adrefs} environment would {\it not} have a {\it widest-label}
+argument, since in this scheme entries in the reference-list are unlabelled.
+
+If such a definition of |\adentry| was documented in the successor to
+\cite{1}, a do-it-yourself-er would be able to use the author-date
+system just as easily as the `reference by number' system.
+
+To conform to the ISO specification \cite{10}, the successors to the
+`standard styles' would arrange for |\dcite| to give a citation of
+the form (1972), for |\adcite| to give a citation of the form
+(Crane, 1972), and for |\adentry| to give a reference-list entry with no
+label.
+
+\subsubsection{Short form}
+The |\firstcite|, |\sfcite| and |\sfentry| commands might
+be defined as |\firstcite{|{\it key-list}|}|,
+|\sfcite{|{\it key-list}|}| and
+|\sfentry{|{\it cite-key}|}[|{\it
+ fairly-full-form}|]{|{\it short-form}|}{|{\it
+ full-reference}|}|.
+Such definitions would, in effect, automate Butcher's manual method of
+ensuring consistency \cite{5,~p178}.
+Having {\it full-reference} as an argument means that the full reference
+can be used as the default {\it fairly-full-form} (to be used when the work
+is first cited \cite{6,~p407}).
+The {\tt sfrefs} environment would {\em not} have a
+{\it widest-label} argument.
+
+The successors to the `standard styles' would arrange for |\firstcite|
+to produce the {\it fairly-full-form} and |\sfcite| to produce the
+{\it short-form}.
+This makes the pessimistic assumption that \LaTeX\ can not itself determine
+whether a citation is the `first citation' of a particular work.
+If someone was ingenious enough to produce code that determined whether a
+citation is a `first citation', {\tt\ttbackslash firstcite} would be
+unnecessary (except,~perhaps, for the construction of tables of abbreviations
+\cite{6,~p414}.)
+To conform to the ISO specification \cite{10}, neither
+|\firstcite| nor |\sfcite|
+would add any punctuation (but, for example, a style file that implemented
+the MLA conventions would have to add brackets \cite{7, ch.\ 5}).
+In the successors to the `standard styles',
+the |\sfentry| would produce an entry with no label.
+
+People producing other style files would be free to implement other
+conventions \cite{5,~p168}.
+
+Some works may have no bibliography or may have just a `select
+bibliography' \cite{5,~p168}. For such works, it will still
+be necessary to supply the details for use by |\firstcite| and
+|\sfcite|. It may therefore be worth allowing a form of
+{\tt sfrefs} (e.g., |\begin{sfrefs}[null]|)
+that holds details of cited works but does no typesetting.
+
+\subsubsection{Additional references}
+Since the entries in an `additional list' will not be cited as such
+(although an `all sources consulted' list may contain a duplicate of
+a cited entry in a `works cited' list), the list will be typeset
+without `labels'. Even in a document that uses the `reference by
+number' citation scheme (and so needs `labels' in the {\tt numrefs}
+list), there will be no `labels' for the entries in an additional list.
+
+It therefore seems likely that the {\tt morerefs} environment could
+be implemented as a variation of {\tt adrefs} or {\tt sfrefs}, the main changes
+being:
+
+\item{\rtr}a change of title (but see section \ref{VII(iii)})
+\item{\rtr}absence of
+ {\it cite-key, author, date, fairly-full-form} and {\it short-form}
+ arguments.
+
+\subsection{VI(iv) Order within the reference-list}
+As stated in section \ref{V}, it is probably best to leave
+any sorting of the reference-list to some other software, or to the author.
+
+However, it might be possible for \LaTeX\ to provide a warning if a
+reference-list is obviously in the wrong order. Perhaps:
+\item{\rtr}although there may be no easy alternative to numbering
+ |\numcite|s in order of appearance within {\tt numrefs}
+ (even though `order of first citation' is usually what
+ is required), \LaTeX\ could give a warning if a |\numcite|
+ gave a number that exceeded the `biggest number produced
+ by |\numcite| so far' by more than one.
+\item{\rtr}there could be a warning if an |\adentry| had an
+ {\it author} whose first letter came before the first letter of the
+ preceding |\adentry|'s {\it author} in the alphabet.
+
+\subsection{VI(v) Citation of a specific division}
+%\label{division}
+As stated in section \ref{III(i)}, provision needs to be made for
+the citation of a particular division (e.g.,~page, section, chapter,
+equation) of another work. The syntax of citation commands should
+not only allow several works to be cited simultaneously, but should also
+allow the relevant division of each work to be specified.
+
+From the author's point-of-view, there would be a variety of satisfactory
+ways to specify citations that are to appear as
+`[4,~p10; 5; 6,~p3]', e.g.
+
+{\frenchspacing
+\leftline{\bs numcite\char'173smith[p. 10],brown,jones[p. 3]\char'175}
+\leftline{\bs numcite\char'173smith, p. 10; brown; jones, p. 3\char'175}
+\leftline{\bs numcite\char'173smith \& p. 10; brown; jones \& p. 3\char'175}
+}
+
+\noindent
+The precise syntax would have to take
+account of the practicalities of programming a command that has to be able
+to accept pairs of arguments, where the second member of each pair is optional.
+
+Analogous facilities would be needed for author-date and `short form'
+citations.
+
+Incidentally, since abbreviations such as p., ch., sec., and fig.\ are
+common when such divisions are specified, I think that citation commands
+should arrange for the optional arguments to be typeset with
+|\frenchspacing|.
+
+\section{VII Details of reference-lists}
+\subsection{VII(i) Variations within mainstream practice}
+Although many academic and technical publications involve only a single
+undivided reference-list, some such publications involve:
+{\description
+\item[more than one list]
+ This situation can arise:
+
+ \itemitem{$\star$}when there is a list of `further reading' etc.,
+ as well as the list of `works cited'.
+ This case has been covered in sections \ref{II(ii)},
+ \ref{III(ii)}, \ref{VI(ii)} and \ref{VI(iii)}.
+ \itemitem{$\star$}when conference proceedings are produced, since each
+ contribution may have its own reference-list.
+ \itemitem{$\star$}in manuals for software. For example, in \cite{13}, a
+ software house's own publications are introduced in the preface
+ and cited (in effect) using a `short form' scheme, while
+ other people's publications are listed at the end of the manual
+ and are cited using the author-date scheme.
+\item[subdivisions within a list]
+ Some reference-lists,~particularly in the humanities, are subdivided
+ according to the source of the cited documents (see
+ \cite{5,~p183}, \cite{6,~p425} and
+ \cite{7,~p88}).
+
+\enddescription}
+
+In some cases, an author may wish to add explanatory paragraphs describing,
+for example, how material was chosen for a `select bibliography'
+\cite{6, fig.\ 15.11} or information about access to (document)
+archives \cite{6, fig.\ 15.16}.
+
+\subsection{VII(ii) \LaTeX\ 2.09}
+\LaTeX\ 2.09 can cope with documents that have more than one
+{\tt thebibliography} environment, and seems to deal satisfactorily
+with a situation in which some |\cite| commands are to
+one {\tt thebibliography} and some are to another (provided that
+the {\it cite-key\/}s are unique). The default effect is
+to give {\it label\/}s that are not unique, which will be acceptable
+when each contribution to a `conference proceedings' has its
+references numbered from one, but not if `works cited'
+and `additional references' are both numbered from one
+(see section \ref{III(ii)}).
+
+The specification of {\tt thebibliography} \cite{1,~p187}
+does not allow anything other than |\bibitem|s within a
+{\tt thebibliography} environment. Hence, it is not clear
+how one can introduce subheadings within a reference-list.
+(In practice, a |\section*| seems to work between
+|\bibitem|s, but I suspect that it puts \LaTeX\ 2.09 into a loop
+if placed before the first |\bibitem|.)
+
+Anyone trying to add explanatory paragraphs (as in \cite{6, fig.\ 15.11}
+and \cite{6, fig.\ 15.16}) will probably find that \LaTeX\ 2.09
+objects that `{|Something's wrong--perhaps a missing \item|}'.
+
+\subsection{VII(iii) \LaTeX3}
+Ideally, in order to provide support for the conventions that are routine
+in mainstream publishing practice, \LaTeX3 should be able to cope with
+all the variations outlined in section \ref{VII(i)}.
+
+\subsubsection{Multiple lists}
+The suggestions made in section \ref{VI} would probably cater for most
+situations where a document has more than one reference-list.
+
+The distinction between {\tt morerefs} and the other environments for
+reference-lists would take care of situations where there is a list of
+`additional references' as well as a list of `works cited'.
+The distinction between the `short form' commands/environment
+and the other commands/environments would take care of situations where a
+software house uses `short form' for its own publications
+and some other scheme for other publications. Conference proceedings
+will be able to have `a reference-list for each contribution'
+if \LaTeX3 follows the \LaTeX\ 2.09 precedent that allows
+more than one {\tt thebibliography} in a document.
+
+\subsubsection{Subdivisions and explanatory paragraphs}
+Because the sciences have different conventions
+from the humanities,~people using the `reference by number' citation
+scheme are unlikely to want the options of subdividing their reference-list
+and inserting explanatory paragraphs. Therefore, it would be legitimate to
+say (for example) `subdivisions and explanatory paragraphs are supported
+within {\tt adrefs}, {\tt sfrefs} and {\tt morerefs} but not within
+{\tt numrefs}', if this made the programming task easier.
+
+For example, it might be convenient to implement {\tt numrefs} as
+a `list-making environment' (as in \LaTeX\ 2.09) but to implement
+the other environments in some other way. Lack of support for subdivisions
+and explanatory paragraphs is unlikely to matter in {\tt numrefs}; the
+`other way' (more like |\paragraph|,~perhaps?) might make it
+easier to implement support for these facilities in the other environments.
+
+\subsubsection{Other problems}
+%\label{reflist-scope}
+One approach to some of the problems mentioned in section \ref{III(iii)}
+is for the standard styles to define the heading for the reference-list by,
+for example, |\def\numrefsheading{References}|, so that anyone who wants
+to change the heading can do so by issuing a |\renewcommand| command
+somewhere before the start of their reference-list.
+
+Another approach is to work in terms of the standard publishing industry
+concept of `back matter' \cite{6,~p4}. Instead of having to
+understand where the {\it heading}, {\it left-head}, {\it right-head} and
+table-of-contents entry (or lack of it) originate for units such as the
+glossary (if any), the reference-list(s) and the index (if any)
+{\em separately}, an author would only have to understand how these features
+are treated {\em consistently} within `back matter'.
+
+Although the `back matter' approach could be used if environments
+such as {\tt numrefs} followed the {\tt thebibliography} precedent and issued
+commands such as |\chapter| or |\section| themselves, authors
+might find the way that {\it heading}, {\it left-head}, {\it right-head} and
+table-of-contents entry materialize less mysterious if it was just the same
+for a reference-list as for (say) a glossary. This would imply that
+{\tt numrefs}, {\tt adrefs}, {\tt sfrefs} and {\tt morerefs} should
+not issue commands like |\chapter| or |\section| themselves.
+As a bonus, it would then be possible for an author to insert an explanatory
+paragraph before the reference-list, and to arrange for subdivisions.
+
+For example, if there was a {\tt backmatter} environment within which
+|\chapter| was treated as defining a unit of `back matter',
+an author's file might contain commands such as
+\begintt
+\begin{backmatter}
+ \chapter{Glossary}
+ ...
+ \chapter{References}
+ \section{Primary sources}
+ \begin{sfrefs}
+ ...
+ \end{sfrefs}
+ \section{Secondary sources}
+ \begin{sfrefs}
+ ...
+ \end{sfrefs}
+ \chapter{Further reading}
+ \begin{morerefs}
+ ...
+ \end{morerefs}
+\end{backmatter}
+\endtt
+
+\section{VIII Conclusion}
+\LaTeX\ has a large number of users, and potential users, who wish to produce
+documents that conform to the conventions that are standard in academic
+publishing. One element of their requirement is the need to conform to the
+conventions for citations and reference-lists that are usual in their
+disciplines.
+
+The choice for \LaTeX3 may be between:
+\item{\rtr}having more facilities for citations and reference-lists than
+ \LaTeX\ 2.09, perhaps as suggested in section \ref{VI}.
+ This would imply an increase in:
+ \itemitem{$\star$}the amount of code needed to implement the facilities,
+and
+ the guru time needed for writing the code
+ \itemitem{$\star$}the number of pages needed, in the successor to
+\cite{1},
+ to describe the facilities -- perhaps 8 pages rather than
+ the 2 pages in \cite{1}.
+\item{\rtr}no significant increase in the facilities provided for citations
+ and reference-lists. Contrary to the idea of `freeing people
+ from formatting concerns to allow them to concentrate on writing'
+ \cite{1,~p8}, many authors (perhaps most authors) would be
+ wasting time:
+ \itemitem{$\star$}hacking at style-files
+ \itemitem{$\star$}searching (software) archives for ready made solutions
+ \itemitem{$\star$}taking up support staff's time in the search for advice
+(with the
+ support staff
+ in turn taking up gurus' time in their search for solutions).
+
+\noindent
+ Moreover, most of this time would be wasted by (or on behalf of) authors
+ who don't want anything exotic; they just want to conform
+ to the conventions standard in traditional academic publishing.
+I'm inclined to think that the first option would be the lesser of the
+two evils.
+
+\section{Appendix: interface with \BibTeX}
+The preceding sections make some suggestions for a \LaTeX3 user
+interface that would enable the do-it-yourself-er to conform to
+the conventions that are usual in academic publishing.
+It is also necessary to consider the implications for the interface to
+\BibTeX.
+
+\subsection{Single reference-list}
+Inspecting {\tt bst} files gives me the impression that, if it
+was decided to adopt a scheme such as that described in section
+\ref{VI}, it would be fairly easy to produce new {\tt bst} files
+to supersede existing ones. For example, a {\tt bst} file
+that implemented a `reference by number' scheme would write
+|\numentry| commands rather than |\bibitem| commands.
+
+If {\tt bst} files were created in this way, they would be able to
+deal with the straightforward situation when there is a single
+reference-list that contains all works cited (plus, possibly,
+any works specified by a command like |\nocite|).
+
+\subsection{Multiple reference-lists, all with the same style}
+More complicated situations can arise in which a document involves
+several reference-lists. For example:
+
+\item{\rtr}The editor of the proceedings of a conference might want the
+ published proceedings to have a reference-list at the end of each
+ chapter.
+\item{\rtr}If, as suggested in section \ref{VII(iii)}, {\tt sfrefs} was
+ implemented in a way that allowed a sequence of {\tt sfrefs} environments
+ to each be preceded by a |\section| command, then, as far as
+ \BibTeX\ is concerned, each {\tt sfrefs} environment might be a separate
+ reference-list.
+
+In both these examples, the document would involve several reference-lists,
+but each reference-list would need to be typeset in a common style.
+I assume that the main problems would be in arranging:
+
+\item{\rtr}to have multiple {\tt bbl} files, or distinct divisions of a single
+ {\tt bbl} file
+\item{\rtr}that each reference-list takes its entries from the correct {\tt bbl}
+ file, or from the correct division of a single {\tt bbl} file.
+
+\subsection{Two reference-lists, each with a different style}
+People producing documents that have a second reference-list (e.g.,
+`further reading') in addition to the list of `works cited'
+might want the first list typeset in one style and the second
+list typeset in another. (In particular, if the `reference by number'
+scheme is used, the first list will have `labels' but the second
+list will have no `labels'.) If the commands/environments suggested
+in section \ref{VI} were implemented, the first list would use
+{\tt numrefs}, {\tt adrefs} or {\tt sfrefs}, while the second list would
+use {\tt morerefs}.
+
+In this situation, it would be necessary to communicate to \BibTeX\
+that two lists are required, but that they are to be typeset in different
+styles. Since the second list is to contain `works {\em not\/}
+cited', it will also be necessary to specify the works to be shown in the
+second list.
+
+If it is decided to extend the interface between \LaTeX\ and \BibTeX\ to
+cater for such situations, it will probably be necessary to consider
+defining alternatives to \LaTeX\ 2.09's |\bibliography| and
+|\bibliographystyle| commands, since it seems unlikely that the syntax
+of the \LaTeX\ 2.09 commands could be extended so as to pass the necessary
+information. One might, for example, consider syntax such as
+|\bibtexcites[|{\it cites-style}|]{|{\it bib-files}|}|
+and
+|\bibtexmore[|{\it more-style}|]{|{\it bib-files}|}{|{\it
+ key-list}|}|.
+Here, it is assumed that:
+
+\item{\rtr}the |\documentstyle| would set defaults for the {\it cites-style}
+ and {\it more-style} that are to be passed to \BibTeX, but the user
+ can over-ride the defaults via the optional arguments to
+ |\bibtexcites| and |\bibtexmore|
+\item{\rtr}|\bibtexmore|'s {\it key-list} argument would be used to
+ specify the works to be included in the list of `additional
+ references'.
+
+If it is not practicable to extend the \LaTeX\slash \BibTeX\ interface
+to cater for these situations automatically, it would presumably be a matter of
+some `human intervention':
+\item{\rtr} to prepare a {\tt bbl} file for the `additional references'
+\item{\rtr} to |\input| the {\tt bbl} file.
+
+\def\item#1{\par\hangindent1.5em\hangafter1{\noindent
+\hbox to 1.5em{#1\hfil}}}
+\def\bibitem#1#2{\item{{#1}}{#2}}
+\section{Bibliography}
+\bibitem{1} {\sc Leslie Lamport.}
+ {\it \LaTeXsl: A document preparation system.}
+ Addison-Wesley, 1986.
+\bibitem{2} {\sc Frank Mittelbach and Rainer Sch\"{o}pf.}
+ With \LaTeX\ into the nineties.
+ {\it TUGboat,} 1989, {\bf 10}, 681--690.
+\bibitem{3}
+ {\it Citing publications by bibliographical references.}
+ BS 5605. British Standards Institution, 1978.
+\bibitem{4}
+ {\it Citation of unpublished documents.}
+ BS 6371. British Standards Institution, 1983.
+\bibitem{5}
+ {\sc Judith Butcher.}
+ {\it Copy-editing.}
+ Cambridge University Press, 1981.
+\bibitem{6}
+ {\it The Chicago manual of style.}
+ Chicago University Press, 1982.
+\bibitem{7}
+ {\sc Joseph Gibaldi and Walter S. Achert.}
+ {\it MLA handbook for writers of research papers.}
+ Modern Language Association of America, 1988.
+\bibitem{8}
+ {\sc Edward J. Huth.}
+ {\it Medical style and format.}
+ ISI Press, 1987.
+\bibitem{9}
+ {\sc ICMJE, International Committee of Medical Journal Editors.}
+ Uniform requirements for manuscripts submitted to biomedical
+ journals.
+ {\it British Medical Journal,} 1988, {\bf 296}, 401--405.
+\bibitem{10}
+ {\it Documentation -- bibliographic references
+ -- content, form and structure.}
+ ISO 690. International Organization for Standardization, 1987.
+\bibitem{11}
+ {\sc Maeve O'Connor.}
+ {\it Editing scientific books and journals.}
+ Pitman Medical, 1978.
+\bibitem{12}
+ {\sc Gillian Page, Robert Campbell and Jack Meadows.}
+ {\it Journal publishing: principles and practice.}
+ Butterworths, 1987.
+\bibitem{13}
+ {\sc Marija J. Noru\v{s}is.}
+ {\it SPSS-X Introductory Statistics Guide for Release~3.}
+ SPSS Inc., 1988.
+\bibitem{14}
+ {\it Presentation of theses and dissertations.}
+ BS 4821. British Standards Institution, 1990.
+\bibitem{15}
+ {\it EndNote: A reference database and bibliography maker.}
+ Berkeley: Niles \& Associates, Inc., 1989.
+\author{David Rhead}
+
+ \endgroup
+\endinput
diff --git a/info/digests/texline/no13/sgml b/info/digests/texline/no13/sgml
new file mode 100644
index 0000000000..739a1de8b2
--- /dev/null
+++ b/info/digests/texline/no13/sgml
@@ -0,0 +1,18 @@
+\title{SGML in the UK}
+In a move to stimulate activity in the UK by the
+\SGML\ Users' Group, a meeting is being held in the autumn for all
+those who are interested. The exact date and venue have not yet been fixed,
+although the meeting will probably be in London. It is planned that notification
+will be
+sent to all who are or have been members of the Users' Group.
+
+
+For further information write to:
+{\obeylines\parindent20pt
+Nigel Bray
+Database Publishing Systems Ltd
+608 Delta Business Park
+Great Western Way
+Swindon
+Wilts SN5 7XF\strut
+}
diff --git a/info/digests/texline/no13/spivak b/info/digests/texline/no13/spivak
new file mode 100644
index 0000000000..caf7f48f30
--- /dev/null
+++ b/info/digests/texline/no13/spivak
@@ -0,0 +1,185 @@
+
+\title{A Contrarian View On \TeX{} Extensions}
+\vskip-3pt
+\centerline{\sl An open letter to the \TeX{} community}\smallskip\noindent
+Recently in \TUGboat\ the question of \TeX{} extensions has generated
+considerable discussion (`pronouncements' might be a more accurate term,
+since this discussion has devolved almost entirely to a few interested
+adherents). Donald Knuth's brief statement in Volume~11, No.~4 (also
+printed in \TeXline\ 12) makes quite clear what he happens to think of the
+whole idea, but this seems to be regarded as a minor inconvenience to be
+circumvented, as in the article by Nelson Beebe that immediately follows.
+
+I should probably begin by admitting that, granted three wishes, I could
+probably expend them on \TeX{} extensions. Nevertheless, I feel that some
+one should speak out against \TeX{} extensions, or at the very least,
+against many of the proposed extensions; though \TUGboat\ articles seldom
+generate any response, I expect there are many who feel strongly about
+them, but don't bother writing.
+
+Many of the suggested \TeX{} extensions fall into three categories:
+
+$\bullet$Allowing \TeX{} to do ugly typesetting.
+
+$\bullet$Making \TeX{} do things 100\% automatically that should really be
+done 95\% automatically.
+
+$\bullet$A third category that I'll come to later.
+
+The first category is amply illustrated by Frank Mittelbach's article in
+Volume~11, No.~3. In connection with the ever pernicious problem of
+typesetting in narrow columns, a proposed extension to \TeX{} would change
+spacing rules according to a scheme attributed to Manfred Siemoneit. My
+first reaction to the accompanying illustrations was: Boy, is that ugly! My
+next reaction: Just who is Manfred Siemoneit, and why should his particular
+scheme be incorporated into \TeX{}? My final reaction: Why stop there?!
+Since this extension is meant to address a problem common to magazine
+publishers, why not use the methods employed by, and presumably desired by,
+these publishers? Those who have remained blissfully ignorant of these
+matters are invited to examine {\sl Time} or {\sl Newsweek\/} and other
+journals of their ilk -- just for their typography, of course! In these
+narrow columns, entire lines are condensed optically, so that the letters
+themselves are condensed in width. Sure, I happen to think it's ugly, but I
+also think ragged-right, letter spacing, and just about every other
+narrow-column device is ugly. In any case, what I think or you think
+doesn't matter, if the whole point is to allow \TeX{} to accommodate the
+multifarious desires of the typesetting industry. And on this particular
+point, the accommodation is quite possible, though that brings us to the
+third category, which will be discussed later.
+
+(Since the whole question of taste has inevitably already intruded itself, I might
+also caution that many of Mittlebach's pronouncements, like his blithe
+statement that hanging punctuation `is a sign of good quality typesetting',
+shouldn't be taken too seriously.)
+
+The second category is well illustrated by two \TUGboat\ articles of quite
+contrasting natures.
+
+The first is an article by David F. Rogers in Volume~9, No.~3, recounting
+problems encountered using \TeX{} to produce a book, {\sl Procedural
+Elements for Computer Graphics}, replete with tables and illustrations, in
+the absence of a macro package adequately implementing requirements
+specified by the book designer. This article was widely regarded as a
+challenge for \TeX{}, and I admit to using it as the starting point for
+requirements for automatic figure placement in \LamSTeX{}. In fact, I
+obtained the book in question to use as a test for the \LamSTeX{} macros.
+Now this book is admittedly typographically complex -- indeed, tables,
+figures, etc., intrude so profusely that in places one might long to resort
+to page-layout `by hand'.
+
+However, Mr.~Rogers seems to think that this procedure is well-nigh impossible.
+An inkling of his difficulties may be gleaned from the following lament
+(italics in the original): `To prevent \TeX{} from reformatting the pages
+to this point a |\vfill\eject| is placed at the bottom of the previous page.
+This, of course, does not always work. \TeX{} occasionally decides that the
+previous material is best presented with an incomplete last line! When this
+happens material must be moved word-by-word from the current page\dots'
+
+Now it is a shame, indeed shameful, that this article not only appeared
+unedited in \TUGboat, but that neither editors nor readers ever subsequently
+explained that the |\vfill|, an inherently vertical mode command, causes the
+paragraph to end, with those dire results, and that the proper way to force
+a page break after a line is with |\vadjust{\break}|. As a result, who
+knows how many \TeX{} users (and would-be users) now think that there is no
+reasonable way to force page breaks in \TeX{}? (By the way, \AmSTeX{} and
+\LamSTeX{} both have |\pagebreak|, which produces exactly the results the
+author wanted.)
+
+In a book of this nature, forcing page breaks and inserting tables and illustrations
+in specific places is probably preferable to having \TeX{} make all
+decisions automatically, even if that is possible. There will invariably be
+situations where an `out-of-order' placement will result in a more
+convenient or pleasing arrangement. (A minor example: on page~18 of
+{\sl Procedural Elements} I would have avoided the footnote that comes right
+under a Figure caption.) And, in general, many of the complaints about
+\TeX{}, and requests for extensions, ignore the fact that \TeX{} isn't
+meant to be a totally automatic system; it is specifically designed for
+interaction with the author, or typesetter, a point explicitly made several
+times in the \TB.
+
+The second article, a query by Frederick H.~Bartlett in Volume~9, No.~1,
+involves high quality typesetting, where a standard typesetting trick is to
+shorten or lengthen a pair of facing pages to improve appearances. This was
+supposed to be done automatically, because `While, admittedly, it may be
+perfectly legitimate to expect an author to struggle with his file over
+half a dozen or so runs to make it perfect, a typesetter's time is much too
+valuable to indulge in such foolishness.'
+
+Mr.~Bartlett's idea was to have the |\output| routine first store the facing pages in
+boxes (much like a two-column routine). Normally each of the pages, after
+being combined with the |\headline| and |\footline| material, would be
+shipped out; but if the total badness of the boxes was too big, then they
+would first be reset in height (by |\unvbox|ing them within a |\vbox| of the
+new height). The problem was that it was impossible to find out \TeX{}'s
+|\badness| for the boxes.
+
+Now this problem has actually gone away in version 3 of \TeX{}, but I claim that it
+was never that serious a problem anyway. One could easily make a macro,
+|\changeheight|, to be used in a form like
+\begintt
+\changeheight{22+ 68- ... }
+\endtt
+to indicate that pages 22 and 23 should be made one line longer, pages 68 and 69 one
+line less, etc., with the |\output| routine taking information from this
+macro to perform the indicated changes on these pages.
+
+Of course, this isn't automatic, since the list has to be generated somehow. But remember that
+we are now talking about high quality typesetting. Even granting the value
+of a typesetter's time, it wouldn't take that much effort to look through
+that very last version of the output, note the pages 22, 68,\dots, needing
+changes, and insert a |\changeheight| line in the file. The file would have
+to be \TeX{}'ed once again, but that's not even `typesetter's time', only
+machine time (I presume that this highly regarded typesetter has a fast
+computer that can re\TeX{} a complete book in only a few minutes). But
+still one more argument for automatic resetting might then be advanced:
+What if you miss a page? The answer to that is very simple: If you miss
+the bad page, it wasn't there! After all, the idea is to modify pages that
+look bad (to this highly paid typesetters eye), not pages to which \TeX{}
+happens to assign some particular |\badness|; indeed, \TeX{}'s |\badness|
+estimate may have little to do with the badness to the human eye.
+
+Finally, we come to the third category: special effects that are not possible
+directly with \TeX{}, but that are quite possible with post-processors,
+such as Bechtolsheim's |dvi2dvi| (Volume~10, No.~3). These effects include
+change bars; underlined or stuck-out text; and inclusion of \TeX{}'ed
+material from other documents. From quite a few years ago, in fact, I
+recall an advertisement for a \dvi\ post-processor that achieved another
+desideratum of the typesetting industry, namely, letter-spacing [adding
+extra space between letters in a line instead of concentrating the extra
+spacing between words], though the proffered sample output may have only
+served to disenchant people with the practice. A similar program could be
+incorporated within a \dvi\ to \PS\ translator to optically scale
+entire lines, as discussed previously. And, of course, once we allow \TeX{}
+to interact with \PS, all sorts of special effects become available.
+
+Purists might prefer document preparation to be a one-shot affair, but once
+you've accepted something like a \LaTeX{} double-pass system, not to mention
+all sorts of auxiliary processes, like index sorting, it becomes absurd to
+eschew \dvi\ post-processors, which are always much faster than \TeX{}
+itself.
+
+One could suggest dozens of minor tools that would make the \TeX{} user's life
+more pleasant. For example, at the lowest level, a standardized sensible
+directory structure for magnified fonts that doesn't require a calculator,
+and a program for finding and removing magnified fonts that doesn't require
+manually changing to directories with long-winded names. Or standardized,
+widely disseminated macros for inclusion of \PS\ files and literals (sure,
+it's easy if you know what you're talking about, but the people who don't
+are totally baffled). Programs for examining the details of a font, and for
+changing kerning, ligatures, and |\fontdimen| parameters by seeing their
+effects on the screen; |tftopl| and |pltotf| should only be used behind the
+scenes -- the everyday user, including typesetters creating their own
+kerning tables, don't want to know about these things. Similar programs for
+creating virtual fonts without knowing the details of |vpl| files.
+
+Bigger \TeX{}'s, obviously coming soon, will also help, but the most important
+tool, possibly revolutionizing \TeX{} usage, would be an interactive \TeX{}
+(the \TB, page 387, makes clear that this is not an `extension'.)
+
+I'm not saying that any one should be prevented from making a \TeX{}
+`extension' with all the features that have been suggested. I just think
+(a)~that they shouldn't call it `\TeX{}' -- why not something completely
+different, like `Frame', for example; and (b)~that TUG should not be
+supporting this effort when there are so many other important areas that it
+has so badly neglected.
+\author{Mike Spivak}
diff --git a/info/digests/texline/no13/texline.head b/info/digests/texline/no13/texline.head
new file mode 100644
index 0000000000..494c5eccdd
--- /dev/null
+++ b/info/digests/texline/no13/texline.head
@@ -0,0 +1,115 @@
+
+
+%\topinsert
+\begingroup
+\overfullrule0pt
+\font\huge palatino at65truept%
+\font\normal palatino at 10pt
+\newbox\info
+\newbox\banner
+\newbox\long
+\newbox\issn
+\setbox\issn\hbox{\normal ISSN 0961-3978}
+
+\setbox\info=\vtop{%
+\font\small=cmr7 at 7truept%
+\baselineskip=7.5truept%
+\small
+\setbox\long\hbox{printed at Imperial College Computer Centre}%
+\hsize=\wd\long
+\def\monyr{\ifcase\month\or January\or February\or March\or April
+ \or May\or June\or July\or August\or September\or October
+ \or November\or December\fi\ \number\year}%
+\line{\hfill Number 13, September 1991}
+\line{\hfill a Newsletter of the \TeX\ community}
+\line{\hfill edited by}
+\line{\hfill Malcolm Clark}
+\line{\hfill PO Box 1897}
+\line{\hfill London NW6 1DQ}
+\line{\hfill Tel: 071 435 8983}
+\line{\hfill Fax: 071 433 3576}
+\line{\hfill Janet: malcolmc@uk.ac.pcl.mole}}
+
+\setbox\banner\vtop{\hsize275pt
+\line{\hfill\huge\TeX\kern-0.1em line\kern-0.15em1\kern-0.1em3}
+\dp\issn0pt\ht\issn0pt
+\line{\hfill\box\issn\hfill}}
+\hfuzz30pt
+
+\kern-0.5in\hbox{\box\info\hfil\lower45pt\box\banner}
+\endgroup
+%\endinsert
+
+\endinput
+\begindoublecolumns
+{\parindent0pt\obeylines
+The editor
+{\sl Cahiers GUTenberg}
+c/o IRISA
+Campus Universitaire de Beaulieu
+35042 Rennes Cedex
+France}
+\bigskip
+\noindent Dear Sir
+\medskip
+\noindent
+The allusion that `les num\'eros 11 et 12 semblent devoir \^etre les
+derniers' of this esteemed organ are premature. I am delighted to
+note that number 13 is well underway. It will include the following:
+
+{\parindent0pt\parskip0.5pt\obeylines
+A Script for building true-sized fonts \author{\sl Angus Duggan}
+Sunny Mexico \author{\sl Betsy Dale}
+The matter of TUG \author{\sl Malcolm Clark}
+Flow charts with \TeX \author{\sl Michael Ramek}
+Virtually there \author{\sl Malcolm Clark}
+The components of \TeX \author{\sl Joachim Schrod}
+Klimt, Freud \& Dante \author{\sl Malcolm Clark}
+Report from uk\TeX ug meeting \author{\sl Chris Rowley}
+Report from BCS ep meeting, Oxford \author{\sl Malcolm Clark \& Chris Rowley}
+How may \LaTeX\ 3.0 deal with citations and reference lists? \hfill{\sl David~Rhead}
+
+\smallskip
+Abstracts, {\sl Cahiers GUTenberg}
+\smallskip
+Book reviews:
+Alison Black: Typefaces for desktop publishing: a user guide
+Paul Abrahams, Karl Berry \& Kathryn Hargreaves: \TeX\ for the Impatient
+Malcolm Clark (ed): \TeX, Applications, Uses, Methods
+\smallskip
+Forthcoming meetings:
+UK \TeX\ Users Group
+GUTenberg, Paris
+EP92, Lausanne
+Desktop Publishing in Astronomy and Space Sciences, Strasbourg
+European \TeX\ Conference, Paris
+TUG Meeting, Dedham, Boston
+}
+
+\bigskip
+`Le nouveau bulletin {\sl baskerville\/}' bears no relationship at all to
+\TeXline. {\fib Baskerville} is the journal of the UK \TeX\ Users Group. The
+first issue was edited by Adrian (no relation) Clark, while the second is
+being edited by Philip (certainly no relation!) Taylor. My involvement
+with {\fib Baskerville} is very indirect, as Chairman of the UK \TeX\ Users
+Group. It is in this role that I contribute material to Baskerville.
+While the first editor of {\fib Baskerville} expressed the view that the advent
+of this new journal signalled the demise of \TeXline, a view similar to
+your own above, I suspect that it will be some years before \TeXline\
+expires. We have already outlived his editorship.
+There is no difficulty in obtaining sufficient articles to make
+production of \TeXline\ worthwhile. Production costs have been
+underwritten by \TeX\kern-0.1emcel for number 13, and I am confident that future
+editions can be similarly subsidised by other parts of the \TeX\ industry. My confidence
+in the future of the newsletter is reflected in the fact that it now
+sports an ISSN: it would be ironic to cease production after obtaining
+this stamp of legitimacy.
+
+\bigskip
+\quad\hfill Best wishes
+\vskip1in
+\quad\hfill Malcolm Clark
+
+\quad\hfill editor, \TeXline
+\enddoublecolumns
+
diff --git a/info/digests/texline/no13/texline.tex b/info/digests/texline/no13/texline.tex
new file mode 100644
index 0000000000..d2cba0e133
--- /dev/null
+++ b/info/digests/texline/no13/texline.tex
@@ -0,0 +1,234 @@
+\message{TeXline macros}
+\vsize9.5in
+\hsize6.5in
+\input newtwo-column%%%%%
+\input verbar
+\tolerance3000
+\lefthyphenmin3
+\righthyphenmin3
+\emergencystretch5pt
+\doublehyphendemerits10000
+\hfuzz2.5pt
+\vfuzz2.5pt
+\baselineskip12pt
+\parskip0pt
+\parindent1em
+\abovedisplayskip1pt
+\belowdisplayskip1pt
+\brokenpenalty1000
+\clubpenalty=10000
+\widowpenalty=10000
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\nopagenumbers
+\headline{\ifnum\pageno>1
+\ifodd\pageno{\sl \TeXline\ 13 \hss \folio}
+\else{\folio \hss\TeXline\ 13}\fi\fi}
+\def\rhead{\ifnum\pageno>1
+ \ifodd\pageno\sl\TeXline\ 13\hss
+ \else\sl\folio\hss\fi\else
+\fi}
+\def\lhead{\ifnum\pageno>1
+ \ifodd\pageno\sl\hss\folio
+ \else\sl\hss\TeXline\ 13\fi\else
+\fi}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\def\,{\ifmmode\mskip\thinmuskip\else\thinspace\fi}
+\def\nl{\hfill\break}
+\def\item#1{\par\hangindent1em\hangafter1{\noindent\bf#1}}
+\def\itemitem#1{\par\hangindent2em\hangafter1{\noindent\enspace\bf#1\ }}
+\def\bi{\item{$\bullet$}}
+\let\bitem\bi
+\def\rtr{\hbox to1em{\hfil$\triangleright$}}
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\def\title#1{\centerline{\bf#1}\smallskip\noindent\ignorespaces}
+\def\section#1{%
+ \medskip\goodbreak\leftline{\let\sc\scit\sl #1}\par\noindent\ignorespaces}
+\def\subsection#1{\medskip\goodbreak\leftline{$\bullet$\sl#1}\par
+\noindent\ignorespaces}
+\def\noauthor{\strut}
+\def\author#1{{\ifvmode\rightline{\sl#1\strut}\else
+ \unskip\nobreak\hfil\penalty50\hskip2em\hbox{}\nobreak
+ \hfil\sl#1\strut\parfillskip0pt\par\fi}}
+\def\caption#1{\medskip\setbox0\hbox{\bf#1}\ifdim\wd0>\hsize
+ \noindent{\bf#1}\else\centerline{\copy0}\fi}
+\long\def\frame#1#2{\vbox{\dimen0=#1\multiply\dimen0 by2
+ \advance\hsize by-\dimen0\hrule\hbox{\vrule\hskip#1\vbox
+ {\multiply\tolerance by
+ 4\overfullrule0pt\parindent0pt\parskip#1
+ \vskip#1{}#2\vskip#1}\hskip#1\vrule}\hrule}}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\def\frac#1/#2{\leavevmode\kern0.1em
+ \raise0.5ex\hbox{\the\scriptfont0 #1}\kern-0.1em
+ /\kern-0.15em\lower0.25ex\hbox{\the\scriptfont0 #2}}
+\def\*#1{\ifmmode\discretionary{\thinspace\the\textfont2\char2#1}{#1}{#1}\else\accent'27#1\fi}
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\font\iteight=cmti8
+\font\ttit=cmsltt10
+\font\scb=cmbx8
+\font\sans=cmss10
+\font\sc=cmcsc10
+\font\fib cmfib8
+\font\mf=logo10
+\font\mfb=logobf10
+\font\mfsl=logosl10
+\let\em\it
+\let\sf\sans
+\font\symb=symbol at 10pt
+\font\cmu=cmu10
+\font\smalltt=cmtt8
+\font\eightsy=cmsy8 \skewchar\eightsy='60
+\def\scit#1{\iteight\uppercase{#1}}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\hyphenation{every-thing}
+
+\def\bar{\smallskip\goodbreak{\noindent\hrule depth3pt}\medskip}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\def\TeX{T\hbox{\hskip-.1667em\lower.424ex\hbox{E}\hskip-.125em X}}
+\def\MF{{\rm{\mf META}\-{\mf FONT}}}
+\def\MFb{{\bf{\mfb META}\-{\mfb FONT}}}
+\def\MFsl{{\sl{\mfsl META}\-{\mfsl FONT}}}
+\def\MFbook{{\sl The \MFsl\kern1pt book}}
+\chardef\apple='360
+\def\Mac{{\symb\apple}}
+\def\MarkUp{MarkUp '8\kern-0.2em\lower0.45ex\hbox{7}}
+\def\LaTeX{{\rm L\kern-.36em\raise.3ex\hbox{\sc a}\kern-.15em
+ T\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}
+\def\La{\rm L\kern-0.36em\raise0.3ex\hbox{\sc a}}
+\def\LaTeXsl{{\it L\kern-.36em\raise.3ex\hbox{\iteight
+ A}\kern-.15emT\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}
+\def\LaTeXbf{{\bf L\kern-.36em\raise.3ex\hbox{\scb
+ A}\kern-.15emT\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}
+\def\DeK{D\kern-0.1667em\lower0.5ex\hbox{E}\kern-0.125emK}
+\def\LeX{L\kern-0.1667em\lower0.5ex\hbox{E}\kern-0.125emX}
+\def\TeXline{{\sl\TeX\kern-0.1em line}}
+\let\Texline\TeXline
+\def\SGML{\hbox{\sc sgml}}
+\let\sgml\SGML
+\def\ISO{{\sc iso}}
+\def\ANSI{{\sc ansi}}
+\def\PS{P{\sc{ost}}\-S{\sc{cript}}}
+\def\MSDOS{{\sc ms\-\dos}}
+\let\msdos\MSDOS
+\def\DOS{{\sc dos}}
+\let\dos\DOS
+\def\PCDOS{{\sc pc\-\dos}}
+\let\pcdos\PCDOS
+\def\IBM{{\sc ibm}}
+\def\plain{{\tt plain}\kern-0.1667em\TeX}
+\def\ukTuG{{\sc uk}\kern-0.1emT\kern-0.1667em\lower0.5ex\hbox{U}\kern-0.125emG}
+\def\ukTUGbf{{\scb UK}\kern-0.1emT\kern-0.1667em\lower0.5ex\hbox{U}\kern-0.125emG}
+\def\TeXtures{{\sl Textures}}
+\let\Textures\TeXtures
+\def\TeXpert{{\sl\TeX\kern-0.1em pert systems\/}}
+\def\TeXhax{\TeX{\sc hax}}
+\let\hax\TeXhax
+\def\TeXbook{{\sl \TeX book}}
+\let\TB\TeXbook
+\def\PCTeX{{\sc pc}\kern-0.1em\TeX}
+\let\ps\PS
+\def\TS{Type \&~Set}
+\def\dvi{{\tt dvi}}
+\let\DVI\dvi
+\def\tfm{{\tt tfm}}
+\let\TFM\tfm
+\def\pxl{{\tt pxl}}
+\let\PXL\pxl
+\def\gf{{\tt gf}}
+\let\GF\gf
+\def\pk{{\tt pk}}
+\let\PK\pk
+\def\CM{{\rm Computer Modern}}
+\def\WEB{{\tt WEB}}
+\def\Weave{{\tt Weave}}
+\def\Tangle{{\tt Tangle}}
+\def\quid{{\cmu\$}}
+\def\unix{{\sc unix}}
+\let\Unix\unix
+\def\AmSTeX{$\cal A$\kern-.1667em\lower.5ex\hbox{$\cal M$}\kern-.125em
+ $\cal S$-\TeX}
+\def\VorTeX{V\kern-.2em\lower.5ex\hbox{O}\kern-.125em R\TeX}
+\def\BiBTeX{{\sc Bib}\kern-.2em\TeX}
+\let\BibTeX\BiBTeX
+\def\SliTeX{{\sc Sli}\TeX}
+\def\IniTeX{{\sc Ini}\TeX}
+\def\MakeIndex{{\sans MakeIndex}}
+\def\TEX{T\kern-0.1667em\lower0.5ex\hbox{\^E}\kern-0.125em X}
+\def\JANET{{\sc Janet}}
+\let\Janet\JANET
+\def\DVItoVDU{DVIto\kern-.15em VDU}
+\def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC}
+\def\PiCTeX{\PiC\TeX}
+\def\XeT{X\kern-0.1667em\lower.5ex\hbox{E}\kern-.125em T-\TeX}
+\def\FASTeX{F\kern-.1667em \lower.5ex\hbox{A}\kern-.1667em S\TeX}
+\def\TUGboat{{\sc TUGboat}}
+\def\psfig{{\it psfig}}
+\def\OzTeX{O\kern-.03em z\kern-.15em\TeX}
+\def\degrees{$^\circ$}
+\def\LamSTeX{L\kern-.4em\raise.3ex\hbox{$\scriptstyle\cal A$}\kern-.25em
+ \lower.4ex\hbox{\eightsy M}\kern-.1em{$\cal S$}-\TeX}
+\let\LamsTeX\LamSTeX
+\def\dante{{\sc Dante}}
+\let\Dante\dante
+\let\DANTE\dante
+\def\GUTenberg{G{\sc ut}enberg}
+\let\GB\GUTenberg
+\def\DW{Dominik Wujastyk}
+\def\DEK{D\kern-0.1667em\lower0.5ex\hbox{E}\kern-0.125em K}
+\def\TeXMaG{\TeX M\kern-0.22em\lower0.5ex\hbox{A}\kern-0.27emG}
+\def\u{\accent'27u}
+\def\by{$\times$}
+\def\inch{$''$}
+\def\ascii{{\sc ascii}}
+\let\ASCII\ascii
+\def\ebcdic{{\sc ebcdic}}
+\let\EBCDIC\ebcdic
+\def\eqn{{\sans eqn}}
+\def\troff{{\sans troff}}
+\def\b{{\tt\char'134}}
+\def\wysiwyg{{\it wysiwyg\/}}
+\def\mwc{Malcolm Clark}
+\def\dpi{dpi}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+
+% Look in the 'Windows' menu for the pictures window
+% It's like the Scrapbook -- cut and paste pictures
+%
+
+\def\picture #1 by #2 (#3){
+ \vbox to #2{
+ \hrule width #1 height 0pt depth 0pt
+ \vfill
+ \special{picture #3} % this is the low-level interface
+ }
+ }
+
+\def\scaledpicture #1 by #2 (#3 scaled #4){{
+ \dimen0=#1 \dimen1=#2
+ \divide\dimen0 by 1000 \multiply\dimen0 by #4
+ \divide\dimen1 by 1000 \multiply\dimen1 by #4
+ \picture \dimen0 by \dimen1 (#3 scaled #4)}
+ }
+\def\pict #1 by #2 (#3){
+ \vbox to #2{
+ \hrule width #1 height 0pt depth 0pt
+ \vfill
+ \special{pictfile #3} % this is the low-level interface
+ }
+ }
+
+\def\scaledpict #1 by #2 (#3 scaled #4){{
+ \dimen0=#1 \dimen1=#2
+ \divide\dimen0 by 1000 \multiply\dimen0 by #4
+ \divide\dimen1 by 1000 \multiply\dimen1 by #4
+ \pict \dimen0 by \dimen1 (#3 scaled #4)}
+ }
diff --git a/info/digests/texline/no13/toc b/info/digests/texline/no13/toc
new file mode 100644
index 0000000000..2bde20d5ee
--- /dev/null
+++ b/info/digests/texline/no13/toc
@@ -0,0 +1,63 @@
+\title{Table of Contents}
+{\parindent0pt\parskip0.5pt\obeylines
+A Contrarian View On \TeX{} Extensions\dotfill1
+{\quad\sl Mike Spivak}
+%
+Electronic Publishing -- Out of the Playpen\dotfill3
+{\quad\sl Peter Ashby and Anna Duckworth}
+%
+Unicode\dotfill4
+{\quad\sl David Penfold}
+%
+Future Meetings of the BCS ep Group\dotfill5
+%
+SGML in the UK\dotfill5
+%
+Cheltenham Effect\dotfill5
+{\quad\sl Henry Holloway}
+%
+The matter of TUG\dotfill6
+{\quad\sl Malcolm Clark}
+%
+Book Reviews\dotfill9
+%
+Sunny Mexico\dotfill12
+{\quad\sl Betsy Dale}
+%
+How might \LaTeX3 deal with citations and reference-lists?\dotfill13
+{\quad\sl David Rhead}
+%
+Desktop Publishing in Astronomy and Space Sciences\dotfill 21
+{\quad\sl Andr\'e Heck}
+%
+6th European \TeX\ Conference\dotfill21
+%
+GUTenberg'91\dotfill22
+%
+Cahiers GUTenberg:
+Summaries from Number 7, November 1990\dotfill 23
+Summaries from Number 8, March 1991\dotfill 23
+%
+Industrial Light and Magic\dotfill24
+%
+First European Summer School in Digital Typography\dotfill24
+%
+\LamSTeX{} Goes Public\dotfill25
+{\quad\sl Mike Spivak}
+%
+A Script for building true-sized fonts\dotfill25
+{\quad\sl Angus Duggan}
+%
+Call for Papers\dotfill29
+%
+Another Book Review\dotfill29
+%
+uk\TeX ug: future meetings\dotfill30
+%
+On the fringe of Boston\dotfill30
+%
+Good Guys\dotfill31
+%
+Catherine Mary Booth\dotfill32
+%
+}
diff --git a/info/digests/texline/no13/uktexug b/info/digests/texline/no13/uktexug
new file mode 100644
index 0000000000..5a2d40727b
--- /dev/null
+++ b/info/digests/texline/no13/uktexug
@@ -0,0 +1,54 @@
+\title{uk\TeX ug: future meetings}\noindent
+{\bf October 16th:} the AGM will be held at {\bf Aston
+University}, the spiritual home of \TeX\ in Europe and the
+home of the world renowned Aston Archive of \TeX\
+paraphanalia. To support the AGM there will be a meeting on
+{\sl Fun with \TeX}. This has to be seen to be believed. We
+will also take the opportunity of being at the electronic
+hub of the \TeX\ world to harangue and moan at the
+Archivists.
+\smallskip\noindent
+{\bf November 20: Oxford University} -- the broad theme for
+this meeting will be {\sl Macro packages and style files}.
+Jonathon Fine and Se\'an Leitch are already lined up for
+this and other members will be fingered\slash volunteered.
+There will also be a \LaTeX3 (lxiii) update. This meeting is
+intended to provide an opportunity for all members to
+contribute, and there is still time to offer a
+contribution. Short talks are at least as welcome as long
+ones (and often much more so). If you have a neat
+application you want to share, or a bee in your bonnet
+about something \TeX like, now's your chance to get on your
+soapbox.
+\smallskip\noindent
+{\bf February 11, 1992:} a meeting in London, at the
+{\bf School of Oriental and African Studies}. Probable
+subject: {\sl \TeX\ for Book and Journal Production}.
+Following hard on the heels of the TUG meeting in Dedham
+{\sl Inroads into Publishing}, and the {\sc Gut}enberg {\sl
+Technical and Scientific Publishing} meeting, uk\TeX ug
+brings you the first \TeX\ meeting on publishing, in
+London, in February!
+\smallskip\noindent
+{\bf Easter, 1992:} A one-day meeting in Scotland, possibly
+{\bf Edinburgh}, timed so that those attending the projected
+BCS EP Specialist Group meeting in Glasgow will not have to
+pay British Rail twice. But note the cheap rail fares
+available to Sassenachs travelling to God's own country --
+only \quid44 from stations in the south to Glasgow and
+Edinburgh. Subject to be announced.
+\smallskip\noindent
+{\bf June/July, 1992:} we are investigating the possibility
+of visiting the Department of Typography at the
+{\bf University of Reading}. The subject of the meeting will
+be {\sl Design Issues}. This meeting is the usual summer
+jaunt to the country.
+\smallskip\noindent
+{\bf Some time:} we hope to organise training days to cover
+the theoretical and practical applications of \MF. We also
+hope to organise a workshop to look at the various ways of
+producing multicolumn output in \TeX. There is also a
+possibility that the group will organise 3- or 4-day
+courses on \TeX\ and \LaTeX\ at a location in London during
+next summer.\noauthor
+
diff --git a/info/digests/texline/no13/unicode b/info/digests/texline/no13/unicode
new file mode 100644
index 0000000000..3e12a19717
--- /dev/null
+++ b/info/digests/texline/no13/unicode
@@ -0,0 +1,62 @@
+\title{Unicode}
+Those of us who have been working with text for some time are familiar with
+the many different ways in which accents, other diacritics and
+non-alphanumeric symbols are coded, not to mention non-Latin texts like
+Arabic, Kanji, and all the other languages in which the staff at the
+School of Oriental and African Studies manage to produce setting.
+
+Of course, we all use \ASCII\ (or \EBCDIC, which is not very different),
+unless you happen to use Locoscript, but there is no standard way of
+representing characters above \ASCII\ 127. The DOS high-level \ASCII\
+characters have become a sort of standard on pcs, but certainly cannot be
+assumed in any text file.
+
+Unicode is a new character coding system based on \ASCII. It has been
+produced by a consortium, Unicode Inc., which includes Apple, Xerox, IBM, Microsoft, SUN, Novell, Aldus,
+and NeXT, and is a 16-bit system. It therefore allows 65,536 characters to
+be coded. This number is still not enough to include all the Chinese,
+Japanese and Korean traditional characters (alphabets is the wrong word
+here), which together add up to about 125,000 symbols, although eliminating
+duplicates in the different languages reduces this to about 36,000
+characters in common use. This is still considered to be too many when taken in conjunction
+with the other symbols required.
+
+Unicode then uses a process called `unification' so that each character is
+given a code.
+Irrespective of what language the character is in, what it means, or how it is
+pronounced, it will still have the same code. This is similar to the way
+that \ASCII\ codes letters without any reference to how they are pronounced
+in different languages, except that in the Eastern languages, the `Han'
+characters represent words rather than letters. After unification, there
+are about 18,000 characters and the total `character set' now stands at
+about 25,000, which leaves plenty of room for `non-unified' Han characters
+and other alphabets (have they include Amharac, for example?).
+Incidentally, the first 128 characters correspond to \ASCII. This is a
+relief and seems obvious, but how often has the obvious not been what is
+produced? Nonetheless a translation table or program will be necessary to go from
+16-bit to 7- or 8-bit coding, or vice-versa.
+
+Most of the vendors involved in the Unicode project plan to produce systems
+which incorporate Unicode. Unfortunately, however,
+the situation is not that simple; there is another system, which the
+International Standards Organisation (ISO) has been working on.
+The standards committee has produced a Draft International Standard (DIS
+10646), which takes an opposite approach to Unicode, retaining the national
+character sets. The coding here is 32-bit and the first eight bits indicate
+the character set, with the remaining 24 indicating the character.
+$2^{24}$ is nearly 17 million, so even the Chinese character set can
+be included with ease. This format is intended to maintain compatibility
+with existing standards.
+
+Which system will be adopted? The final aims of the two groups are eventually the
+same, but their intermediate aims are different, to have
+machine-independent coding (Unicode) and to be compatible with existing standards (ISO). It is interesting to note that the Japanese national standards
+group has voted against DIS 10646 because it rejects Han unification, which
+they feel is so vital that they have developed their own unifying
+standards.
+
+Time will tell, but if past experience is anything to go by, then it is the
+ad-hoc standard, available on the hardware, which will be adopted.
+Nonetheless, we will still require translation programs (and people to
+write them) for some time yet!
+\author{David Penfold}
diff --git a/info/digests/texline/no13/vegas b/info/digests/texline/no13/vegas
new file mode 100644
index 0000000000..9a6b72286b
--- /dev/null
+++ b/info/digests/texline/no13/vegas
@@ -0,0 +1,50 @@
+\title{Call for Papers}
+Papers are invited for a {\bf Symposium on Document
+Analysis and Information Retrieval} in Las Vegas, Nevada,
+on March 16--18th, 1992. The scope of the conference covers
+research in systems for automatic retrieval with emphasis
+on the retrioeval of information from printed documents.
+Specific aspects of such systems include, but are not
+limited to, the theory and the practice of:
+
+\leftline{\bf Document Processing}
+\bitem Page Processing
+\bitem Zoning
+\bitem Segmentation
+\bitem Character Recognition
+\bitem Graphic recognition, maps\slash mechanical
+drawings
+
+\leftline{\bf Information Retrieval}
+\bitem Full text retrieval
+\bitem Query optimization
+\bitem Expansion\slash compression tools
+\bitem Semantic access tools
+\bitem Knowledge extraction from text
+\bitem Information retrieval and database systems
+
+\noindent Send no less than seven copies of papers to
+either
+{\obeylines
+Kazem Taghva
+Dept Elec/Computer Eng
+University of Nevada
+4505 Maryland Parkway
+Las Vegas, NV 89154, USA
+{\tt eewlb@cs.univ.edu}
+\noindent or
+Kazem Taghva
+Dept Elec/Computer Eng
+University of Nevada
+4505 Maryland Parkway
+Las Vegas, NV 89154, USA
+{\tt taghva@cs.univ.edu}
+}
+
+\noindent
+Papers should be about 5,000 words long. To promote
+cross-fertilization between works in progress, short
+synopses of susbtantial projects are also invited. These
+should be 1,000--1,500 words. The papers should contain
+enough information for the progream committee to
+understand the scope of the solution being
diff --git a/info/digests/texline/no13/verbar.tex b/info/digests/texline/no13/verbar.tex
new file mode 100644
index 0000000000..49515932e2
--- /dev/null
+++ b/info/digests/texline/no13/verbar.tex
@@ -0,0 +1,33 @@
+% verbatim macros from the TeXbook
+\newskip\ttglue
+\ttglue=0.5em plus 0.25em minus 0.15em
+\outer\def\begindisplay{\obeylines\startdisplay}
+{\obeylines\gdef\startdisplay#1
+ {\catcode`\^^M=5$$#1\halign\bgroup\indent##\hfil&&\qquad##\hfil\cr}}
+\outer\def\enddisplay{\crcr\egroup$$}
+\message{macros for verbatim scanning}
+\chardef\other=12
+\def\ttverbatim{\begingroup
+ \catcode`\\=\other
+ \catcode`\{=\other
+ \catcode`\}=\other
+ \catcode`\$=\other
+ \catcode`\&=\other
+ \catcode`\#=\other
+ \catcode`\%=\other
+ \catcode`\~=\other
+ \catcode`\_=\other
+ \catcode`\^=\other
+ \obeyspaces \obeylines \tt}
+{\obeyspaces\gdef {\ifvmode\indent\fi\space}}% a little extra
+
+\outer\def\begintt{$$\let\par=\endgraf \ttverbatim \parskip=0pt
+ \catcode`\|=0 \rightskip-5pc \ttfinish}
+{\catcode`\|=0 |catcode`|\=\other % | is temporary escape character
+ |obeylines % end of line is active
+ |gdef|ttfinish#1^^M#2\endtt{#1|vbox{#2}|endgroup$$}}
+
+\catcode`\|=\active
+{\obeylines \gdef|{\ttverbatim \spaceskip\ttglue \let^^M=\ \let|=\endgroup}}
+
+