% local.tex -- released 12 February 1988
% Copyright(c) 1988 by Leslie Lamport
%   for LaTeX version 2.09
%
% This file is used to produce a Local Guide for LaTeX users containing
% information specific to a site plus errors and omissions from the LaTeX
% manual (published by Addison-Wesley).
%
% The installer of LaTeX at a site is responsible for customizing this
% document and providing copies for users.  He will have to read the
% text of this file CAREFULLY to see what must be added, removed, and
% changed.  

% The \contact command is defined to generate the name of the person to
% whom questions should be sent.  This should be someone at the site.
% Most users' questions are easily answered by anyone slightly familiar
% with LaTeX or TeX. Don't bother anyone at another site with questions
% that can be answered locally.

\documentstyle[titlepage,timrom,11pt]{article}

\addtolength{\oddsidemargin}{-.875in}
\addtolength{\evensidemargin}{-.875in}
\addtolength{\textwidth}{1.75in}

\addtolength{\topmargin}{-.875in}
\addtolength{\textheight}{1.75in}

\newcommand{\contact}{OLC}
\font\niftyboldfont = c-bol
\def\bftt{\niftyboldfont}

\newcommand{\BibTeX}{{\rm B\kern-.05em{\sc i\kern-.025em b}\kern-.08em
    T\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}

\newcommand{\SLiTeX}{{\rm S\kern-.06em{\sc l\kern-.035emi}\kern-.06em T\kern
   -.1667em\lower.7ex\hbox{E}\kern-.125emX}}


\newcommand\bs{\char '134 }  % A backslash character for \tt font


\title{Using \LaTeX\ at Project Athena\\
{\normalsize ``The Local Guide''}}

\author{John Kohl and Sharon Belville\\
(from the original by Leslie Lamport)}

\date{April 6, 1990\\              % Keep this date current
For \LaTeX\ Version 2.09} 

\begin{document}

\maketitle

\tableofcontents

\newpage

\LaTeX\ runs on a variety of computers at many different sites.  This
document tells you how to use \LaTeX\ on a Project Athena workstation. It is
not about \LaTeX\ itself, which is described by the manual---{\em \LaTeX: A
Document Preparation System}, published by Addison-Wesley, available at the
MIT Coop at Kendall Square and fine book stores everywhere.

If you have a question that you can't answer by reading the manual and this
document, ask \contact, by typing {\tt olc} at the {\tt athena\%} prompt.  The
consultants should also be informed of any possible \LaTeX\ bugs or
undocumented anomalies.

{\em Inessential \LaTeX}, published by the SIPB,\footnote{Student Information
Processing Board, W20-557, 253-7788.} gives a good brief introduction to
\LaTeX\ for the novice.  There is also more documentation available through
on-line help.\footnote{Type {\tt help} at the {\tt athena\%} prompt and look
under ``Text Processing.''} This document is an adaptation of the standard
\LaTeX\ Local Guide distributed with \LaTeX.  It deals mostly with \LaTeX\
issues unique to the Project Athena environment.

\section{Getting Started}

\subsection{Running a Sample File} \label{sec:sample}

Before preparing your own documents, you may want to get acquainted with
\LaTeX\ by running it on a sample input file.  First make your own copy of the
file \mbox{\tt sample.tex} by typing the following Unix command:

\vspace*{1ex}\begin{tt}
  athena\%  {\bftt cp  /usr/athena/lib/tex/macros/sample.tex  .}
\end{tt}\vspace*{1ex}

\noindent (You must type the space followed by the period at the end.  This
and all other Unix commands are ended by typing {\em return}.)  A copy of the
file \mbox{\tt sample.tex} is now in your current directory; you can edit it
just like any other file.  If you destroy or mess up your copy, typing the
above command again gets you a fresh one.

Next, run \LaTeX\ on the file \mbox{\tt sample.tex} by typing:

\vspace*{1ex}
\begin{tt}
  athena\%  {\bftt latex  sample.tex}
\end{tt}
\vspace*{1ex}

\noindent When \LaTeX\ has finished, it will have produced the file \mbox{\tt
sample.dvi} in your directory.  If you are on an X display, you can use the
command:

\vspace*{1ex}
\begin{tt}
  athena\%  {\bftt xdvi  sample.dvi  \&}
\end{tt}
\vspace*{1ex}

\noindent to view the formatted file on your screen.  Documentation on the
xdvi program is in the manual page, which you can read by typing:

\vspace*{1ex}
\begin{tt}
  athena\%  {\bftt man  xdvi}
\end{tt}
\vspace*{1ex}

\noindent You can print this file by typing the command:

\vspace*{1ex}
\begin{bftt}
  dvi2ps  -r  sample.dvi  |  lpr  -P{\em printername} 
\end{bftt}
\vspace*{1ex}

\noindent Be sure to substitute the name of the printer in your cluster for
{\em printername} in the command line (e.g. {\tt dvi2ps -r sample.dvi | lpr
-Plinus}).  This command converts the {\tt dvi} output to PostScript ({\tt
dvi2ps}) and sends it to the specified printer ({\tt lpr}).  The {\tt -r}
option reverses the order of the output of the pages, so that page one is
printed first.

After your output has been printed, you can delete \mbox{\tt sample.dvi} by
typing:

\vspace*{1ex}
\begin{tt}
  athena\%  {\bftt delete  sample.dvi}
\end{tt}
\vspace*{1ex}

\noindent You can likewise delete the {\tt sample.aux} and {\tt sample.log}
files.  See Section~\ref{sec:op-system} for more information on the {\tt .aux}
files.


\subsection{Preparing and Running \LaTeX\ on Your Own Files}

You must use a text editor to prepare an input file for \LaTeX. The document
{\em Essential Emacs\/}, available from Graphic Arts in the basement of
Building 11, describes GNU Emacs, the standard text editor available at
Project Athena.  There is also documentation available through on-line help.
Type \mbox{\tt help} at the \mbox{\tt athena\%} prompt and look under ``Text
Processing.''

The easiest way to start learning about \LaTeX\ is by examining the file
\mbox{\tt small.tex} with your text editor.  You can obtain your own copy of
this file, in your directory, by typing the command:

\vspace*{1ex}
\begin{tt}
  athena\%  {\bftt cp  /usr/athena/lib/tex/macros/small.tex  .}
\end{tt}
\vspace*{1ex}

After you have prepared your file, whose name should have the extension {\tt
.tex}, you must run it through \LaTeX\ and print the output.  Follow the
instructions in Section~\ref{sec:sample}, except substitute the first name of
your file for ``\mbox{\tt sample}''.  To save disk space, \mbox{\tt delete}
the dvi file after printing the output, then \mbox{\tt expunge} the backup
copy (for example, type \mbox{\tt delete sample.dvi} and then \mbox{\tt
expunge sample.dvi}).


%List the text editors, available, and any special features they have
%for producing \LaTeX\ input.  Explain how the various text editors
%could cause bad characters to appear in the input file that would
%generate the
%\begin{verbatim}
%! Text line contains an invalid character.
%\end{verbatim}
%error.

If you are using Emacs to prepare a \LaTeX\ input file, you can use many
advanced features of the \LaTeX{}-mode.  Usually when you edit a file whose
name ends in \mbox{\tt .tex}, Emacs assumes you are editing a \TeX\ file.  You
can change into a special \LaTeX\ mode by typing \mbox{\tt M-x latex-mode}
once you are editing the file.  Once you have done this, you can type
\mbox{\tt C-h m} for more information on this editing mode.

If you want to stop \LaTeX\ in the middle of its execution, perhaps because it
is printing a seemingly unending string of uninformative error messages, type
{\em Control-C\/} (press $C$ while holding down the key labeled {\em CTRL\/}).
This will make \LaTeX\ stop as if it had encountered an ordinary error, and
you can then return to Unix command level by typing {\tt X}, as described in
the manual.  If typing {\em Control-C\/} doesn't work, typing {\em
Control-Z\/} will get you immediately to Unix command level, but this will
leave a stopped job hanging around.  This is not optimal, because \LaTeX\ uses
a lot of memory, and you may not be able to start another \LaTeX\ process.
There should be no reason to type {\em Control-Z\/}.

If \LaTeX\ is already stopped with an error, you can use the ``X'' command to
exit \LaTeX\ and return to the {\tt athena\%} prompt.  If you get a ``file not
found'' message, neither {\em Control-Z\/}, {\em Control-C\/}, nor ``X'' will
work; you need to enter {\em Control-D\/} to exit.

To use the {\em ispell\/} program for finding spelling errors in a \LaTeX\
input file named \mbox{\tt myfile.tex}, type the following command:

\vspace*{1ex}
\begin{tt}
  athena\%  {\bftt ispell  -t  myfile.tex}
\end{tt}
\vspace*{1ex}

\noindent This will begin an interactive session in which you can correct any spelling
errors in your file.  Read the manual page on {\em ispell\/} (by typing
\mbox{\tt man ispell}) for information on how to use it.

\section{Carrying On}

\subsection{\LaTeX\ on Unix} \label{sec:op-system}

The only special problems in using \LaTeX\ caused by the Unix operating system
involve the way Unix handles files.  The first problem arises because, when a
program starts to write a file, Unix destroys the previous version of that
file.  Thus, if an error forces you to stop \LaTeX\ prematurely (by typing
{\em Control-C\/} or {\em Control-Z\/}), then the files that \LaTeX\ was
writing are incomplete, and the previous complete versions have been
destroyed.  You probably don't care about the output on the {\tt dvi} file,
but, if you are making a table of contents or using cross-referencing
commands, then \LaTeX\ also writes one or more {\em auxiliary files\/} that it
reads the next time it processes the same input file.  If the auxiliary files
are incomplete because \LaTeX\ was stopped before reaching the end of its
input file, then the table of contents and cross-references will be incorrect
the next time \LaTeX\ is run on the same input file.  You will have to run
\LaTeX\ a second time to get them right.  If you want to avoid having to run
\LaTeX\ twice after making an error---for example, if your input is very
long---then you should save copies of these auxiliary files before running
\LaTeX. An input file named \mbox{\tt myfile.tex} and all the auxiliary files
produced by \LaTeX\ from it are included in the Unix file specifier \mbox{\tt
myfile.*}.  Use the Unix {\tt cp} command to save copies of these files.

\vspace*{1ex}
\begin{tt}
  athena\%  {\bftt cp  myfile.*  /tmp}
\end{tt}
\vspace*{1ex}

The second problem in using \LaTeX\ on Unix involves the files that \LaTeX\
reads.  The file whose name you type with Unix's {\tt latex} command is called
the {\em root file}.  In addition to reading the root file, \LaTeX\ also reads
the files specified by \hbox{\verb|\input|} and \hbox{\verb|\include|}
commands.  With the Unix directory system, \LaTeX\ must know not only the
names of these file but also on what directories they are.  It will have no
problem finding the correct files if you follow two simple rules:
\begin{enumerate}
 \item Run \LaTeX\ from the directory containing the root file.
 \item Keep all files specified by \hbox{\verb|\input|} and 
      \hbox{\verb|\include|} commands in the same directory as the root
       file.
\end{enumerate}
If you follow these rules, you never have to type an Unix path specifier when
using \LaTeX.

You should never break the first rule, otherwise \LaTeX\ will have trouble
finding auxiliary files.  (To run \LaTeX\ on someone else's file, copy the
file to your directory.) If you break the second rule, specifying a file from
another directory in an \hbox{\verb|\input|} or \hbox{\verb|\include|}
command, you must use a complete path name.  For example, to include the file
\mbox{\tt hisfile.tex} from Jruser's directory \hbox{\verb|/foo/bar|}, you
can type
\begin{verbatim}
     \include{/mit/jruser/foo/bar/hisfile}
\end{verbatim}
You should have already typed \mbox{\tt attach jruser} to have Jruser's
locker available on your workstation.  A \verb|~| character may not appear in
the argument of an \hbox{\verb|\input|} or \hbox{\verb|\include|} command, so
you {\em can't\/} use a file name such as
\hbox{\verb|~jruser/foo/bar/hisfile|}. 

For people who don't like to obey rules, here is exactly how \LaTeX\ finds its
files.  The root file is found by Unix according to its usual rules.  \LaTeX's
auxiliary files are read and written in the directory from which it is run.
All file names specified in the \LaTeX\ input, including the names of
document-style ({\tt sty}) files specified by the \hbox{\verb|\documentstyle|}
command, are interpreted relative to the directory from which \LaTeX\ is run.
If \LaTeX\ does not find a file starting in this directory, it looks in the
directory \hbox{\verb|/usr/athena/lib/tex/macros|}.  You can change the
directories in which \LaTeX\ looks for its input files by setting the
environment variable \mbox{\tt TEXINPUTS}.  Putting the command
\begin{verbatim}
setenv TEXINPUTS .:/mit/jruser/myown:/usr/athena/lib/tex/macros:
\end{verbatim}
in your \mbox{\tt .environment} file causes \LaTeX\ to look for files first in
the current directory, then in Jruser's {\tt /myown} directory, and then in
the system directory.  You might want to do this if your name is Jruser and
you have your own personal document-style files in your {\tt /myown}
directory.

\subsection{Document Styles}

There are many document styles and style options available at Athena that are
not described in the manual.  The file \mbox{\tt
/usr/athena/lib/tex/macros/00index} briefly describes the styles that are not
described here.  Many of these files come from the \LaTeX-Style collection
started by Ken Yap at the University of Rochester.  Some useful styles are:
the \mbox{\tt proc} style option for making camera-ready copy for conference
proceedings, the {\tt bezier} option for drawing curves, the {\tt ifthen}
option for implementing {\bf if-then-else} and {\bf while-do} control
structures, the {\tt doublespace} option for people creating documents such as
theses, which {\bf must} be doublespaced.  Finally, we have a template
designed to meet MIT thesis requirements.


\subsubsection{The {\tt proc} Style Option}

The {\tt proc} option is used with the \mbox{\tt article} document style.  It
produces two-column output for ACM and IEEE conference proceedings.  The
command \hbox{\verb|\copyrightspace|} makes the blank space at the bottom of
the first column of the first page, where the proceedings editor will insert a
copyright notice.  This command works by producing a blank footnote, so it is
placed in the text of the first column.  It must go after any
\hbox{\verb|\footnote|} command that generates a footnote in that column.

\LaTeX\ automatically numbers the output pages.  It's a good idea to identify
the paper on each page of output.  Placing the command: 
\begin{verbatim}
     \markright{Jones---Foo}
\end{verbatim}
in the preamble (before the \hbox{\verb|\begin{document}|} command) prints
``Jones---Foo'' at the bottom of each page.

\subsubsection{The {\tt bezier} Style Option}

This option defines a single command, \hbox{\verb|\bezier|}, that draws a
curved line in a {\tt picture} environment.  Let $P_{i}$ be the point with
coordinates $(x_{i},y_{i})$, for $i=1$, 2, and 3.  The command
\begin{itemize} \tt
\item[]
\verb|\bezier{|$n$\verb|}(|$x_{1}$,$y_{1}$)($x_{2}$,$y_{2}$)($x_{3}$,$y_{3}$)
\end{itemize}
draws $n$ points on the quadratic Bezier spline determined by the three
points $P_{1}$, $P_{2}$, and $P_{3}$.  The locus of points on this
spline is a parabolic arc from $P_{1}$ to $P_{3}$ having the line
$P_{1}P_{2}$ tangent to it at $P_{1}$ and the line $P_{2}P_{3}$ tangent
to it at $P_{3}$.  Note that $P_{2}$ is {\em not\/} on this arc unless
$P_{1}$, $P_{2}$, and $P_{3}$ are colinear, in which case the arc is a
straight line.  Bezier splines are useful because it's easy to join two
of them together smoothly by giving them the same tangent line where
they meet.

It takes roughly 75 points per inch to form a solid line, depending upon the
line thickness.  See Section~C.13.3 of the manual for commands to specify line
thickness in a {\tt picture} environment.  This command is {\em very\/} slow,
and \TeX\ has enough memory to hold only about 1000 points plus a page of
text.  (Remember that \TeX\ keeps the current page plus all as yet unprinted
figures in memory.) So, the \verb|bezier| command should be used for only a
small number of small curves.


\subsubsection{The {\tt ifthen} Style Option}

This option provides two programming language features that are useful
only for people who already know how to program.  It defines the
two commands
\begin{itemize} 
\item[]
\verb|\ifthenelse{|{\em test\/}\verb|}{|{\em then clause\/}\verb|}{|%
{\em else clause\/}\verb|}|\\
\verb|\whiledo{|{\em test\/}\verb|}{|{\em do clause\/}\verb|}|
\end{itemize}
that implement the following two Pascal language structures
\begin{itemize}
\item[]
\begin{tabbing}
{\bf if} {\em test\/} \= {\bf then} \= {\em then clause\/} \\
 \> {\bf else} \> {\em else clause\/} \\[2pt]
{\bf while} {\em test\/} {\bf do} {\em do clause\/}
\end{tabbing}
\end{itemize}
The {\em then\/}, {\em else\/}, and {\em do\/} clauses
are ordinary \LaTeX\ input; {\em test\/} is one of the following:
\begin{itemize}
 \item A relation between two numbers formed with {\tt <}, {\tt >},
or {\tt =}; for example, \hbox{\verb|\value{page}>3|}.
 \item \verb|\equal{|{\em string1\/}\verb|}{|%
{\em string2\/}\verb|}|, which evaluates to {\em true\/} if {\em
string1\/} and {\em string2\/} are the same strings of characters after
all commands have been replaced by their definitions.  (Upper- and
lowercase letters are unequal.)
 \item A logical combination of the above two kinds of tests
    using the operators \hbox{\verb|\or|}, \hbox{\verb|\and|},
    and \hbox{\verb|\not|} and the parentheses \hbox{\verb|\(|}
    and \hbox{\verb|\)|}---for example:
\begin{verbatim}
\not \( \value{section} = 1  \and  \equal{Jones}{\myname} \)
\end{verbatim}
\end{itemize}
The {\em test\/} argument is a violently moving argument, which means
that not only fragile commands but even some commands that are not
normally fragile will break, causing \TeX\ to enter an infinite loop.
The \verb|\protect| command works in these situations.

These commands, together with \hbox{\verb|\renewcommand|} and the commands of
Section~C.7.4 for manipulating counters, open up a whole new world of hacking.


\subsubsection{The {\tt showidx} Style Option}

This style option, for use with the {\tt report} or {\tt book} document
styles, causes index entries to be printed in the outer margin.  It does not
change the effect of \verb|\makeindex|, which controls whether or not an {\tt
.idx} file is written.  No attempt is made to avoid overprinting marginal
notes.  This option issues a \verb|\flushbottom| declaration.

\subsubsection{The {\tt thesis} Style Option}

The style option {\tt mitthesis} can be used in producing a document which
meets the MIT thesis formatting requirements.  To see a sample thesis that you
can use as a template, type the following commands:

\vspace*{1ex}
\begin{tt}
  athena\%  {\bftt attach  thesis}

  athena\%  {\bftt cd  /mit/thesis/tex}

  athena\%  {\bftt more  README}
\end{tt}
\vspace*{1ex}

\noindent The file {\tt README} explains the files in the directory.  

\subsection{Where the Files Are}

% must explain where the following files are:
%   small.tex, sample.tex, *.sty, *.doc, lablst.tex, idx.tex

All of the \LaTeX\ files mentioned in the manual, including the {\tt sty} and
{\tt doc} files, as well as the sample files {\tt small.tex} and {\tt
sample.tex}, are in the directory \mbox{\tt /usr/athena/lib/tex/macros}.
Fonts are stored in another directory: the {\tt tfm} files (used by \TeX\ and
\LaTeX) and the pixel files (used by {\em dvi2ps\/}, {\em xdvi\/}, and other
device drivers) are in \mbox{\tt /usr/athena/lib/tex/fonts}. 

\subsection{Running {\tt lablst.tex} and {\tt idx.tex}}

A list of labels and citations in an input file is printed by running \LaTeX\
on the input file \mbox{\tt lablst.tex}, which is done by typing

\vspace*{1ex}
\begin{tt}
  athena\%  {\bftt latex  /usr/athena/lib/tex/macros/lablst.tex}
\end{tt}
\vspace*{1ex}

\noindent \LaTeX\ will then ask for the name of the input file, which should be
typed without an extension, and for the name of the main document style (e.g.,
\mbox{\tt article}), used by that file.

The index entries on an {\tt idx} file are printed by running \LaTeX\
on the file \mbox{\tt idx.tex}, which is done by typing

\vspace*{1ex}
\begin{tt}
  athena\%  {\bftt latex  /usr/athena/lib/tex/macros/idx.tex}
\end{tt}
\vspace*{1ex}

\noindent \LaTeX\ will ask for the name of the {\tt idx} file, which is typed
without an extension.



\subsection{Differences from the Manual}

All \LaTeX\ features described in the manual are provided by the
implementation at Project Athena.

%Explain here any characters that can appear in input files other than
%the ones listed in Section 2.1.

%Tell if the \mbox{\tt log} file has an extension other than
%\mbox{\tt .log}.  Note: on TOPS-20, its extension is \mbox{\tt .lst}.

%Describe the sizes of disks and circles the are available.

%Don't forget to mention if the invisible fonts needed for \SLiTeX\
%color slides are unavailable.

\subsection{Using \BibTeX}

\BibTeX\ is a program for compiling a reference list for a document
from a bibliographic database.  It is run by typing

\vspace*{1ex}
\begin{tt}
  athena\%  {\bftt bibtex  myfile.tex}
\end{tt}
\vspace*{1ex}

\noindent where \mbox{\tt myfile.tex} is the name of your \LaTeX\ input file.
This reads the file \mbox{\tt myfile.aux}, which was generated when you ran
\LaTeX\ on \mbox{\tt myfile.tex}, and produces the file \mbox{\tt myfile.bbl}.
\BibTeX\ should be run from the directory containing \mbox{\tt myfile.tex}
(which should be the same directory from which \LaTeX\ was run on that file).

If the {\tt bib} file is not in the same directory as the \LaTeX\ input
file---for example, if you're using someone else's {\tt bib} file---then you
must include a path as part of the file name specified by the
\hbox{\verb|\bibliography|} command.  A \verb|~| cannot appear in the argument
of a \hbox{\verb|\bibliography|} command, so you should use a complete path
name.  For example, the \LaTeX\ command
\begin{verbatim}
  \bibliography{/mit/jruser/bibfiles/gnus}
\end{verbatim}
specifies the file \mbox{\tt gnus.bib} kept by Jruser in his \mbox{\tt
/bibfiles} directory.


There is now no formal provision for sharing bibliographic database
information, nor are there programs to assist in making your own {\tt bib}
files.  Suggestions for forming one or more common {\tt bib} files are
welcome.

In addition to the bibliography styles described in the manual, there is a
{\tt ieeetr} style that formats entries in the style of the IEEE transactions.

In addition to the usual three-letter abbreviations for the months, the
following abbreviations are defined by the bibliography styles:
\begin{list}{}{\labelwidth 0pt \itemindent-.5\leftmargin
       \itemsep=1pt
       \let\makelabel\descriptionlabel}\it
\item[\tt acmcs] ACM Computing Surveys
\item[\tt acta] Acta Informatica
\item[\tt cacm] Communications of the ACM
\item[\tt ibmjrd] IBM Journal of Research and Development
\item[\tt ibmsj] IBM Systems Journal
\item[\tt ieeese] IEEE Transactions on Software Engineering
\item[\tt ieeetc] IEEE Transactions on Computers
\item[\tt ieeetcad]
 IEEE Transactions on Computer-Aided Design of Integrated Circuits
\item[\tt ipl] Information Processing Letters
\item[\tt jacm] Journal of the ACM
\item[\tt jcss] Journal of Computer and System Sciences
\item[\tt scp] Science of Computer Programming
\item[\tt sicomp] SIAM Journal on Computing
\item[\tt tocs] ACM Transactions on Computer Systems
\item[\tt tods] ACM Transactions on Database Systems
\item[\tt tog] ACM Transactions on Graphics
\item[\tt toms] ACM Transactions on Mathematical Software
\item[\tt toois] ACM Transactions on Office Information Systems
\item[\tt toplas] ACM Transactions on Programming Languages and Systems
\item[\tt tcs] Theoretical Computer Science
\end{list}

% Note: All styles should share the same set of abbreviations.

\subsection{Using \SLiTeX}

\SLiTeX\ is a version of \LaTeX\ for making slides.  To run \SLiTeX\ with a
root file \mbox{\tt myroot.tex}, you type:

\vspace*{1ex}\begin{tt}
  athena\%  {\bftt slitex  myroot.tex}
\end{tt}\vspace*{1ex}

\noindent (You should be connected to the directory containing \mbox{\tt
myroot.tex}.) Refer to Section~\ref{sec:op-system} if you want slide files or
\hbox{\verb|\input|} files to be in a different directory from your root file.

Color slides are made by copying the color layers produced by \SLiTeX\ onto
color transparencies.  Graphic Arts may provide such a service; give them a
call if you have need for it.

\subsection{Using {\em Index\/}} \label{sec:makeindex}

The {\em \LaTeX{}Index\/} program helps in making an index.  It is 
described in its manual page, available by typing:

\vspace*{1ex}\begin{tt}
  athena\%  {\bftt man -M /usr/sipb/man index}
\end{tt}\vspace*{1ex}

\noindent You should have already have the {\tt sipb} locker {\tt attach}ed to
your workstation.

\subsection{Fonts}

Almost all the symbols available on our fonts can be generated by ordinary
\LaTeX\ commands.  However, there are type sizes not obtainable by \LaTeX's
size-changing commands with the ordinary document styles.  Consult a local
\TeX\ expert to find the \TeX\ name for such a font.

Tables~\ref{tab:styles} and \ref{tab:fonts} allow you to determine if the font
for a type style at a particular size is preloaded, loaded on demand, or
unavailable.  Table~\ref{tab:styles} tells you what size of type is used for
each \LaTeX\ type-size command in the various document-style options.  For
example, with the {\tt 12pt} option, the \hbox{\verb|\large|} declaration
causes \LaTeX\ to use 14pt type.  Table~\ref{tab:fonts} tells, for every type
size, to which class of fonts each type style belongs.  For example, in 14pt
type, \verb|\bf| uses a preloaded font and the other five type-style commands
use load-on-demand fonts.  Roman (\verb|\rm|) and math italic (\verb|\mit|)
fonts are all preloaded; the \hbox{\verb|\em|} declaration uses either italic
(\verb|\it|) or roman.

%Describe any special fonts available here.

%Tell where to find a font manual, listing the character numbers of
%the symbols on different fonts.

%Include a table telling which fonts are preloaded, loaded on demand,
%and unavailable.  

\subsection{Using PostScript Fonts}

For the PostScript fonts, there are \LaTeX\ {\em style options} that work as
follows:
\begin{verbatim}
  \documentstyle[11pt,timrom]{article}
\end{verbatim}
will use Times as the font family (it will also use \mbox{\tt 11pt} as the
base size and \mbox{\tt article} as the style).  The following PostScript
families are currently available:

\vspace*{1ex}
\begin{tabular}{ll}
 timrom&Times\\
 newcen&NewCentury-Schoolbook
\end{tabular}
\vspace*{1ex}

\noindent The following will probably be supported in the near future:

\vspace*{1ex}
\begin{tabular}{ll}
 helv&Helvetica\\
 avantg&Avant-Garde\\
 bookman&Bookman
\end{tabular}
\vspace*{1ex}

Also in the near future we should be changing dvi-to-ps drivers, which should
not affect \LaTeX\ source files that use PostScript fonts, but which will
change \verb|\specials| and which will require that the \LaTeX\ source files
be run through \LaTeX\ again (i.e., the {\tt dvi} files will be
semi-obsolete).  [This will also give us the additional fonts.]

We also have some other fonts available from raw TeX that will be
\LaTeX{}-usable in the near future; we intend to have ``Concrete Modern'' and
``Pandora'' ready by the next release.

\begin{table}[h]
\centering
\begin{tabular}{l|r|r|r|}
\multicolumn{1}{l}{size} & 
\multicolumn{1}{c}{default (10pt)} &
        \multicolumn{1}{c}{11pt option}  &
        \multicolumn{1}{c}{12pt option}\\
\cline{2-4}
\verb|\tiny|       & 5pt  & 6pt & 6pt\\
\cline{2-4}
\verb|\scriptsize| & 7pt  & 8pt & 8pt\\
\cline{2-4}
\verb|\footnotesize| & 8pt & 9pt & 10pt \\
\cline{2-4}
\verb|\small|        & 9pt & 10pt & 11pt \\
\cline{2-4}
\verb|\normalsize| & 10pt & 11pt & 12pt \\
\cline{2-4}
\verb|\large|      & 12pt & 12pt & 14pt \\
\cline{2-4}
\verb|\Large|      & 14pt & 14pt & 17pt \\
\cline{2-4}
\verb|\LARGE|      & 17pt & 17pt & 20pt\\
\cline{2-4}
\verb|\huge|       & 20pt & 20pt & 25pt\\
\cline{2-4}
\verb|\Huge|       & 25pt & 25pt & 25pt\\
\cline{2-4}
\end{tabular}
\protect\caption{Type sizes for \LaTeX\ size-changing
commands.}\label{tab:styles}  
\end{table}

\begin{table}[h]
\centering
\begin{tabular}{l|c|c|c|c|c|c|}
\multicolumn{1}{l}{}& 
\multicolumn{1}{c}{\tt \bs it} &
\multicolumn{1}{c}{\tt \bs bf} &
\multicolumn{1}{c}{\tt \bs sl} &
\multicolumn{1}{c}{\tt \bs sf} &
\multicolumn{1}{c}{\tt \bs sc} &
\multicolumn{1}{c}{\tt \bs tt} \\
\cline{2-7}
5pt  & D & D & X & X & X & X \\
\cline{2-7}
6pt  & X & D & X & X & X & X \\
\cline{2-7}
7pt  & P & D & X & X & X & X \\
\cline{2-7}
8pt  & P & D & D & D & D & D \\
\cline{2-7}
9pt  & P & P & D & D & D & P \\
\cline{2-7}
10pt & P & P & P & P & D & P \\
\cline{2-7}
11pt & P & P & P & P & D & P \\
\cline{2-7}
12pt & P & P & P & P & D & P \\
\cline{2-7}
14pt & D & P & D & D & D & D \\
\cline{2-7}
17pt & D & P & D & D & D & D \\
\cline{2-7}
20pt & D & D & D & D & D & D \\
\cline{2-7}
25pt & X & D & X & X & X & X \\
\cline{2-7}
\end{tabular}
\protect\caption{Font classes: P = preloaded, D = loaded on demand, 
         X = unavailable.}\label{tab:fonts}
\end{table}

\subsection{Special Versions}

No foreign-language or other special versions of \LaTeX\ are currently
available at Project Athena.  (Of course, you can get foreign symbols.  See
Section 3.2 in the manual for information.)


\section{Bugs}

There are a few known bugs in \LaTeX\ that occur very seldom and cause the
user little trouble, but would be very difficult to fix.  Moreover, given the
nature of complex systems, it is not unlikely that the corrections would lead
to even worse problems.  Therefore, these bugs will probably not be fixed.

The bugs and ways to get around them are listed below.  Do not worry about any
of them until you are preparing the final draft, since changes to the text are
very likely to cause the problem to disappear.
\begin{itemize}
\item In rare instances, a figure or table will be printed on the page
preceding the text where the {\tt figure} or {\tt table} environment appears.
This can be fixed by moving the environment further towards the end of the
document.

\item A marginal note at the top of a page may appear in the wrong margin.
This can be fixed by inserting a redundant \verb|\pagebreak| command to force
a page break exactly where \LaTeX\ started the new page anyway.

\item A footnote can be broken across two pages when it should fit on a
single page.  This happens when there is one or more figures or tables on the
page.  The problem is corrected by moving, towards the end of the file, the
last {\tt figure} or {\tt table} environment that produces a figure or table
on the page where the footnote starts.
\end{itemize}


\section{Errata and Additions to the Manual}

\input{addendum}
\end{document}

%&c&@i*\hbox{* 2@s\|\ @i|}|#&
%&i&\index{#}&
%&m&\mbox#&
%&t&{\tt #}&
%&v&\hbox{\verb|#|}&
%&b&\verb|#|&
%&h&\hbox#&
