\documentclass[11pt]{article}
\usepackage{fontfaq}
\begin{document}
\title{The Simple Guide to Type 1 Fonts in \LaTeX\newline Version 0.99}
\author{Matthew Amster-Burton (\href{mailto:mamster@mamster.net}{mamster@mamster.net})}
\maketitle\tableofcontents\clearpage
\section{Important Note}
This document has been superseded by Philipp Lehman's ``The Font
Installation Guide:  Using Postscript Fonts to Their Full
Potential with \LaTeX,'' available
\href{http://www.ctan.org/tex-archive/info/Type1fonts/fontinstallationguide.pdf}{on
the web}.  Lehman's document covers everything this one does and
more, and it's better organized.

The source for the document you're reading is available.  Here's
the \href{http://www.mamster.net/tex/fontfaq.tex}{main file} and
the \href{http://www.mamster.net/tex/fontfaq.sty}{style file}.
Please feel free to modify and redistribute this file;  I request
that you keep my name on it.

\section{Introduction}
It comes up on \texttt{comp.text.tex} almost every day: ``How do I
install my Type 1 fonts in \TeX/\LaTeX?  How do I use expert
fonts?  How do I specify oldstyle figures instead of lining
figures?''  Generally these questions get answered with the usual
amount of grumbling, but the answers tend to vary in quality and
everyone has their own advice.

Most people neither need nor want to delve into the gory details
of \pkg{fontinst} or \TeX's virtual font mechanism---they just
want to get their font installed and working with a minimum of
fuss. As far as I know, there is no document on this subject that
is both clear and complete.  This is an attempt to remedy that
situation. The process described below will not solve every font
problem you come across.  It's designed for the simple, everyday
case that clogs the newsgroup.  Let's begin.

\section{Type 1 fonts:  background and glossary}

The Type 1 format was developed by Adobe Systems.  Adobe remains
the largest supplier of Type 1 fonts, but there are many other
quality type foundries including Agfa-Monotype, \acro{DTL}, and
Hoefler. Type 1 is an \emph{outline} font format, which means that
fonts in this format can be scaled to any size. Fonts can be
broken down into two general categories: body type and display
type.  Body type is suitable for typesetting long stretches of
text.  Display type is suitable only for titles, ad copy, and the
like.  Most body typefaces work perfectly well in a display
capacity, but the reverse is untrue (see figure
\ref{displayface}). This document works equally well for
installing body and display types.

Nearly all of the popular typefaces you see in regular use are
available in Type 1 format.  Before you use this document to
install a new font, make sure you don't already have it installed:
most \TeX\ installations already include the basic Postscript
fonts Times, Palatino, and Helvetica.  See the documentation for
\acro{PSNFSS}.\footnote{\acro{PSNFSS} documentation:
\url{http://tex.loria.fr/general/new/fntguide.html}}

Not all font sets contain the same number of characters.  All will
come with capital and lowercase letters (except for certain
display types such as Trajan that have only capital letters) and a
set of numerals, punctuation marks, and certain accented
characters and math symbols.  In addition to the above, fonts may
also include an \emph{expert set}, which usually consists of small
caps, extra ligatures, text figures (``lowercase numbers'' that
integrate better with text), and some extra punctuation and
superscript/subscript characters.  A font with its expert set is
often referred to as an ``expert font.'' Note that the expert set
by itself is as useless as Della's combs in \emph{The Gift of the
Magi}. This document explains how to install expert fonts.

Instead of an expert set, a font may offer a \SCOSF variant, which
contains capitals \emph{and} small caps, text figures, and
punctuation, but no extra ligatures or super- and subscripts.
Unlike an expert set, a \SCOSF font can be used by itself to set
text in \caps{Capitals \emph{\&} Small Caps}.  This document does
not explain how to install \SCOSF fonts; however, if you don't
care about text figures (I would argue that you should, but it's
up to you) you may follow the instructions in this document for
non-expert fonts and will end up with a usable result.  For an
illustration of the difference between an expert font and a \SCOSF
font, see figure \ref{expertscosf}.

A Type 1 font will come with a set of files for each variant
(explain this).  Depending on the vendor and the package you buy,
each variant may be represented by between two and four files as
follows:

\PFB files contain the actual font outlines.  These are always
required and always supplied.

\AFM files contain font metrics describing the spacing and other
characteristics of the letterforms. For example, an italic font's
\AFM file will tell you the angle of the italic's slant.  If you
feel like modifying the kerning tables of a font, start here.
\AFM files are text and can be edited by hand.

\PFM files are a neutered binary-format version of \AFM files for
use on the Windows platform.  They are required for installing
fonts under Windows, but \TeX doesn't need them at all.  If you
have an Adobe-supplied font with \PFM files but no {\AFM}s, you
can usually download the {\AFM}s from Adobe's FTP site.  There is
a program for converting {\PFM}s to {\AFM}s, but I've never gotten
it to work right.  I have had some luck generating \AFM files from
{\PFM}s using the commercial font editor FontLab\footnote{FontLab:
\url{http://www.fontlab.com/}} and the free editor
PfaEdit,\footnote{PfaEdit: \url{http://pfaedit.sf.net/}} but the
resulting \AFM usually requires some hand-editing.

\INF files are text-format files that allow Windows to regenerate
a \PFM file based on the \AFM.  As you would expect, these files
are also ignored by \TeX.

\subsection{Other font formats}

\textbf{TrueType} is a format developed by Microsoft as a
competitor to Type 1.  There is a web page\footnote{Using TrueType
fonts with \TeX\ and \pdftex:
\url{http://www.radamir.com/tex/ttf-tex.htm}} explaining how to
use these fonts with \TeX.

\textbf{OpenType} is the newest format on the block.  Jointly
developed by Microsoft and Adobe, OpenType fonts can contain up to
65,536 characters and comply with the Unicode standard for
international text.  Unfortunately, \TeX\ itself is limited to 256
characters per font, and the OpenType format is incompatible with
most popular versions of \TeX.\footnote{This is not exactly true:
A few OpenType fonts are internally stored in TrueType font. One
of these, the Palatino Linotype font that comes with Windows XP
and Windows 2000, has been adapted for use with \TeX.} Someone
would do well to write a program that converts an OpenType font to
a pair of Type 1 fonts, regular and expert.

\textbf{Multiple Master} fonts are a Type 1 variation that allow
to you interpolate along various axes such as weight, optical
size, or width, meaning, for example, that you can make a font
exactly as bold or light as you like.  They never caught on,
probably because they are tricky to use, and Adobe (who was the
main vendor of \MM fonts) is replacing them with OpenType fonts as
fast as they can.  Some people have come up with clever ways to
generate Multiple Master (\MM) fonts on the fly, but generally, to
use \MM fonts, you have to generate instances and install them
like regular Type 1 fonts. There is a free utility called
\pkg{mminstance}\footnote{\pkg{mminstance}:
\url{http://www.lcdf.org/~eddietwo/type/}} to handle this for you,
but it requires \AMFM files, which are hard to come by. Without
the \AMFM files, you'll have to use a commercial utility such as
FontLab.

\subsection{Potential pitfalls}

All of the expert sets provided by Adobe should work fine with
this document.  Expert sets from other vendors, however, may not,
because they don't sort the characters in the same way.  For
example, the procedure outlined in this \acro{FAQ} will not work
with the expert sets from \acro{DTL} or Carter \emph{\&} Cone.
These fonts can be made to work with \TeX, but it requires some
under-the-hood work with \pkg{fontinst} beyond the scope of this
document.

\begin{figure}
\begin{tabular}{l|l}
\includegraphics[height=1.5in]{sabonsample.pdf} & \includegraphics[height=1.5in]{minionsample.pdf}
\end{tabular}
\caption{\SCOSF vs expert fonts.  Left:  From top, Sabon Regular,
Sabon \acro{SC}, Sabon Regular Italic, Sabon ItalicOsF.  Right:
From top, Minion Regular, Minion Regular Expert, Minion Italic,
Minion Italic Expert.  Note that expert sets do not contain
capital letters.} \label{expertscosf}
\end{figure}

\section{Is this document right for you?}

This is the right document for you if you find yourself in the
following situation:

\begin{itemize}
\item You have some Type 1 fonts you want to install.

\item You may have expert fonts available, in which case you'd
like to get small caps, extra ligatures, and text figures working
properly.  Work through section \ref{nonexpert} but see section
\ref{expert} for the additional steps needed to install an expert
set.

\item You do not have ``\SCOSF'' fonts, which are more complicated
to install and beyond the scope of this document. (I'll be
covering them in a future \acro{FAQ}.) There are prepackaged
metrics for some such fonts (including the popular Adobe releases
of \acro{ITC} New Baskerville, Times Ten, and Stempel Garamond)
available from font maven Walter Schmidt.\footnote{Walter
Schmidt's font page: \url{http://home.vr-web.de/was/fonts}}
\end{itemize}

\section{Maintaining a \file{localtexmf} directory}

No matter what \TeX\ system you use, maintain a local directory
(either system-wide on a single-user system such as Windows, or
under your home directory on a multiuser Unix system). Installing
fonts means dropping files all over your hard drive, and if you
don't have a way of keep track of what files you've added to your
\TeX\ distribution, you are going to cry later.  I will refer to
the local directory as \file{localtexmf};  call yours whatever you
want.

\acro{CTAN} has some good documentation\footnote{Managing a
one-person \TeX\ system:
\url{http://www.ctan.org/installationadvice/}} on maintaining a
local directory.  The same document includes some incomplete font
installation advice and is not a replacement for this document.

\section{Prerequisites}

You'll need the following:

\begin{itemize}
\item A \TeX{} system based on \TeX3.  This includes most popular
free and shareware distributions, including MiK\TeX{} for Windows,
Oz\TeX{} for Mac, and te\TeX{} for Unix.  It does not include
Y\textit{\&}Y \TeX, which uses its own virtual font system but
makes Type 1 fonts easy to install.  If you're using
Y\textit{\&}Y, read your documentation rather than this document.

\item A recent version of \pkg{fontinst}, 1.8 or
newer.\footnote{\pkg{fontinst}:
\url{http://www.tug.org/applications/fontinst/}}  Available from
the Comprehensive \TeX\ Archive Network
(\acro{CTAN}).\footnote{\acro{CTAN}: \url{http://www.ctan.org/}}

\item A map table based on the Karl Berry font naming
scheme.\footnote{Berry map files:
\url{http://www.tug.org/fontname/fontname_4.html}} If you have the
\pkg{fontname} package installed (most distributions install it by
default), you should find a directory of map files. Under a
\acro{TDS}-compliant system, it's \file{texmf/fontname}.
\end{itemize}

\section{The Process}
\label{nonexpert}

Throughout this procedure, we'll work with an example font.  I'll
use Adobe Minion, which is the font used to set this document (in
\acro{PDF} form, at least).  When appropriate, I'll discuss how to
install the expert set.

\subsection{Make sure you have all the pieces}

You'll need the \PFB and \AFM files for the font family you wish
to install.  Don't try to install more than one font family at a
time.  If you don't have the \AFM files, you can download them
from Adobe's \acro{FTP} site.\footnote{Adobe \acro{AFM} files:
\url{ftp://ftp.adobe.com/pub/adobe/type/win/all/afmfiles}} This
site tends to go down sporadically; if you have trouble, keep
trying, and when you get through, download all the {\AFM}s you
think you'll need. You may also have \PFM and \INF files; these
have nothing to do with \TeX{} and may be deleted. Put all your
font files in a single scratch directory.

\subsection{Rename the font files to the Karl Berry standard}

If you understand the naming rules, great.  If you don't, who
cares? Just follow the map file.  For example, here's a line from
\file{adobe.map}:

\begin{verbatim}
pmnr8a    Minion-Regular                    A    143    morg____
\end{verbatim}

This tells you that the font Minion-Regular is known to Adobe as
\file{morg____} (that is, \file{morg____.pfb} and
\file{morg____.afm}) and in the Berry scheme as \file{pmnr8a}. So,
under \acro{DOS}:

\begin{verbatim}
C:>ren morg____.* pmnr8a.*
\end{verbatim}

And under bash:

\begin{verbatim}
% for filename in "$@" ; do ...
\end{verbatim}

There's another useful piece of information in the line from the
map file.  The number, 143, tells you in what directory you'll
find the \AFM file on the Adobe \acro{FTP} site.

Now, if you are an old-school batch file hacker, you are probably
thinking to yourself, ``Why in the world would I do this manually
when all the information is right there in the map file?''  You
are a person after my own heart.  I've created a Perl script to
rename the files automatically.  It's included at the end of this
document or you can
\href{http://www.mamster.net/tex/berry.pl}{download} it.

\subsection{Create a \pkg{fontinst} script}

The \pkg{fontinst} package has a command that takes care of any
simple font installation task:  \verb+\latinfamily+. Create a file
(I tend to call mine \file{fi.tex}) containing the following:

\begin{verbatim}
\input fontinst.sty
\latinfamily{pmn}{}
\bye
\end{verbatim}

\file{pmn} is the Berry shorthand for Adobe Minion;  replace it
with the abbreviation for your font.

\subsection{Run the script through \TeX}

Nothing tricky here:

\begin{verbatim}
% tex fi
\end{verbatim}

When \pkg{fontinst} finishes (it can take a substantial amount of
time), you should have a bunch of \file{*.pl}, \file{*.vpl},
\file{*.mtx}, and \file{*.fd} files.  If you don't, something went
wrong.  Look through the log (\file{fi.log} in our example) for
errors.

\subsection{Compile the \file{*.pl} and \file{*.vpl} files}

The \file{*.pl} files must be compiled into \file{*.tfm} files;
the \file{*.vpl} files must be compiled into \file{*.vf} files.
This is done using the \pkg{pltotf} and \pkg{vptovf} utilities,
which should be included with your \TeX\ distribution. The syntax
is as follows:

\begin{verbatim}
pltotf file.pl file.tfm
vptovf file.vpl file.vf file.tfm
\end{verbatim}

For some reason, the utilities included with MiK\TeX\ require the
full syntax, but under te\TeX\ most of the arguments are optional,
making life much easier:

\begin{verbatim}
pltotf file
vptovf file
\end{verbatim}

As above, you should automate this with a script.

\subsection{Delete the leftover junk}

You no longer need the \file{*.mtx}, \file{*.pl}, and \file{*.vpl}
files and should delete them.

\subsection{Move the files to the proper directories}

Under any \acro{TDS}-compliant system (including MiK\TeX\ and
te\TeX), the files go like this:

\skipper
\begin{tabular}{ll}
File type & Directory \\
\hline \file{*.pfb} &
\file{localtexmf/fonts/type1/\emph{vendor}/\emph{name}} \\
\file{*.afm} & \file{localtexmf/fonts/afm/\emph{vendor}/\emph{name}} \\
\file{*.tfm} & \file{localtexmf/fonts/tfm/\emph{vendor}/\emph{name}} \\
\file{*.vf}  & \file{localtexmf/fonts/vf/\emph{vendor}/\emph{name}} \\
\file{*.fd}  &
\file{localtexmf/tex/latex/\emph{vendor}/\emph{name}}
\end{tabular}
\skipper

So, for example, \file{pmnr8a.pfb} (Minion Regular) would go in\\
\file{localtexmf/fonts/type1/adobe/minion}.

\subsection{Create a \LaTeX package}

If you use \LaTeX, you'll want to make a package to simplify the
use of your new font.  You can place it in the same directory as
the \file{*.fd} files.  Your \file{minion.sty} should look like
this:

\begin{verbatim}
\ProvidesPackage{minion}
\renewcommand{\rmdefault}{pmn}
\endinput
\end{verbatim}

\subsection{Create a map file for dvips and \pdftex}
\label{mapfile}

Here's what the map file should look like for Minion (regular,
italic, bold, and bold italic):

\begin{verbatim}
pmnr8r Minion-Regular "TeXBase1Encoding ReEncodeFont" <8r.enc <pmnr8a.pfb
pmnri8r Minion-Italic "TeXBase1Encoding ReEncodeFont" <8r.enc <pmnri8a.pfb
pmnb8r Minion-Bold "TeXBase1Encoding ReEncodeFont" <8r.enc <pmnb8a.pfb
pmnbi8r Minion-BoldItalic "TeXBase1Encoding ReEncodeFont" <8r.enc <pmnbi8a.pfb
\end{verbatim}

If you think I'm going to explain each part of this line, you've
got the wrong \acro{FAQ}.  Just make the changes you'd expect for
your own font.  All of the necessary information can be found in
the Berry map file, and you should never change the
\verb+"TexBase1Encoding ReEncodeFont"+ or \verb+8r.enc+.

For example, say you were installing Sabon.  Perusing the
\file{adobe.map} file, you find the following line:

\begin{verbatim}
psbr8a    Sabon-Roman                       A    088    sar_____
\end{verbatim}

This tells you that the short name for Sabon is \file{psb}.  The
full name of the regular variant is Sabon-Roman, and the Berry
name is \file{psbr8a}. Substituting an \file{r} for the \file{a}
at the end of the name gives you \file{psbr8r}, the name of the
virtual font file that \TeX\ is looking for.  Now you have enough
information to generate one line of the Sabon map file
(\file{psb.map}):

\begin{verbatim}
psbr8r Sabon-Roman "TexBase1Encoding ReEncodeFont" <8r.enc <psbr8a.pfb
\end{verbatim}

The Minion map file should be named \file{pmn.map}.  Your map file
should be named (three-letter font name)\file{.map}.  Place it in
the dvips \file{config} directory.  Under MiK\TeX, that's
\file{localtexmf/dvips/config}.  Place another copy (or better, a
link) in the \pdftex \file{config} directory
(\file{localtexmf/pdftex/config}) if you use \pdftex.

Next, you'll need to tell dvips and \pdftex about the new map
file. For dvips, make a copy of \file{config.ps} and drop it into
your local tree.  The file should already have a line showing
dvips where to find its existing map file (often called
\file{psfonts.map}). Right after that line, add the line:

\begin{verbatim}
p +pmn.map
\end{verbatim}

For \pdftex, the config file is called \file{pdftex.cfg}.  Copy it
to your local tree, and add the following line to the end of the
file:

\begin{verbatim}
map +pmn.map
\end{verbatim}

Finally, your \acro{DVI} viewer needs to know about that map file.
For MiK\TeX's yap, edit \file{config.makepk} and add:

\begin{verbatim}
p +pmn.map
\end{verbatim}

Again, this can and should be automated with a script.  Keep
reading for details.

\subsection{Rebuild the hash tables}

Now you have to tell \TeX\ that you've moved files around, or it
won't be able to find any of your new goodies.  Under MiK\TeX:

\begin{verbatim}
C:\>initexmf -u
C:\>initexmf --mkpsres
\end{verbatim}
or use the MiK\TeX\ Options program (figure \ref{mo}).

\begin{figure}
\begin{center}
\includegraphics{mo-cap}
\end{center}
\caption{Using the Mik\TeX\ Options program to rebuild \TeX's hash
tables}\label{mo}
\end{figure}

Under te\TeX:

\begin{verbatim}
% texhash
\end{verbatim}

\subsection{Test out your new font}

That should do it!  Try running the following document through
\LaTeX to see if your new font is working:

\begin{verbatim}
\documentclass{article}
\usepackage{minion} % substitute the name of your font
\begin{document}
How do you like my new font?
\end{document}
\end{verbatim}


\section{Expert sets}
\label{expert}

If you use \TeX, you're probably serious about typesetting. And if
you're serious about typesetting, you should choose a font with an
expert set available.  An expert set includes small caps, text
figures, extra ligatures, and often other treats such as small
punctuation marks and superscript characters.  Again, remember
that an expert set is useless without the base font.  ``Minion
Regular Expert,'' for example, is no good without ``Minion
Regular.''

You can install a font with an expert set using almost exactly the
procedure above. There are only two differences.

\subsection{Text or lining figures?}

Text figures (also known as oldstyle figures, hanging figures, and
in German the delightful \emph{Medi\"{a}valziffern}) are the
``lowercase'' numbers used throughout this document. Some of them
have ascenders and some hang below the baseline, just like
lowercase letters. Text figures are the right choice for most
documents but are not generally used in technical writing with a
lot of mathematics.  So if you have an expert set available,
you'll want to generate two fonts:  one with text figures, one
with lining figures.  It's easy to switch back and forth within a
single document if you like.

\subsection{The \texttt{\textbackslash latinfamily} command}

The \TeX\ jargon for ``expert font with text figures'' is ``j''
and the jargon for ``expert font with lining figures'' is ``x''.
Your \pkg{fontinst} script should look like this:

\begin{verbatim}
\input fontinst.sty
\latinfamily{pmnj}{}  % Minion expert family with text figures
\latinfamily{pmnx}{}  % Minion expert family with lining figures
\bye
\end{verbatim}

\subsection{Create \emph{two} \LaTeX packages}

Because you've created two fonts, you need two \LaTeX packages.
For text figures:

\begin{verbatim}
\ProvidesPackage{minionj}
\renewcommand{\rmdefault}{pmnj}
\endinput
\end{verbatim}

\noindent And for lining figures:

\begin{verbatim}
\ProvidesPackage{minionx}
\renewcommand{\rmdefault}{pmnx}
\endinput
\end{verbatim}

\noindent As above, these may be placed in the same directory as the
\file{*.fd} files.

\subsection{Create a map file for dvips and \pdftex}

Your map file needs to include lines telling the \acro{DVI}
drivers where to find the expert sets.  Your map file should
contain the following lines \emph{in addition} to those explained
in section \ref{mapfile}.

\begin{verbatim}
pmnb8x MinionExp-Bold <pmnb8x.pfb
pmnbi8x MinionExp-BoldItalic <pmnbi8x.pfb
pmnr8x MinionExp-Regular <pmnr8x.pfb
pmnri8x MinionExp-Italic <pmnri8x.pfb
\end{verbatim}

\noindent Note that these are a lot simpler than the lines for the
non-expert parts of the font.

\subsection{Switching between the two fonts}

To switch between oldstyle and lining figures, just switch fonts.
For example, if you're currently using Minion with text figures
(\file{pmnj}: 12345) and wish to switch to Minion with lining
figures (\file{pmnx}: {\fontfamily{pmnx}\selectfont 12345}) use
the following command:

\begin{verbatim}
\fontfamily{pmnx}\selectfont
\end{verbatim}

\appendix
\section{Helpful scripts}

\textbf{Warning:} These scripts are like this \acro{FAQ} as a
whole.  There is no warranty.  Additionally, the scripts are in
the public domain.  Change and improve them however you like;
there are plenty of missed opportunities for error checking and
additional functionality, but they work well enough for me.

\note{I'm currently working to make the script more portable, so I
haven't included it in this draft.  If you know of any existing
scripts for renaming files to the Berry standard, please
\href{mailto:mamster@mamster.net}{email me}.}

\begin{comment}

\subsection{The \file{berry.pl} script}

This script checks your Adobe-named fonts against the
\file{adobe.map} file and automatically renames them according to
the Karl Berry scheme.  Feel free to modify this to work with
other map files.

\begin{verbatim}
#!/usr/bin/perl -w

use File::Copy;
use strict;

my $idx = 'adobe.map';

my %pfbfiles;
while( glob( '*.pfb' ) ) {
   s/\.pfb$//;
   $pfbfiles{$_}++;
}

# Loop to find Adobe numbers and grab AFM files
# from the Adobe FTP site

open IDX, $idx || die "Can't open $idx";

my @matches;
while( <IDX> ) {
   my $adobename = getadobename( $_ );
   if( $pfbfiles{$adobename} ) {
      push @matches, $_;
   }
}
close IDX || die "Trouble closing $idx";

foreach( @matches ) {
   my $adobename = getadobename( $_ );
   my $adobenum = substr( $_, 49, 3 );
   my $range = checkrange( $adobenum );
   my $file = "$adobename.afm";
   if( -e $file ) {
      print "$file already exists--good\n";
   }
   else {
      my $url = "$ftp/$range/$adobenum/$file";
      print "Getting $file\n";
      getstore( $url, $file ) || die "FTP problem";
   }
}

print "Renaming font files to Berry names\n";
# Loop to find Berry names and rename files
my( $fontname, $shortname );
foreach( @matches ) {
   my $adobename = getadobename( $_ );
   my $berryname = substr( $_, 0, 8 );
   $berryname =~ s/\s+$//;
   move( "$adobename.pfb", "$berryname.pfb" );
   move( "$adobename.afm", "$berryname.afm" );

   # if we got this far, snag the name of the font
   unless( $fontname ) {
      $fontname = substr( $_, 10, 33 );
      $fontname =~ s/\s+$//;
      $fontname =~ /^(\w+)-/;
      $fontname = $1;
      $fontname = lc $fontname;
   }
   $shortname ||= substr( $berryname, 0, 3 );
}

print "I identified the font:  $fontname\n";

sub getadobename {
   my $line = shift;
   return substr( $line, 56, 8 );
}
\end{verbatim}

\subsection{The extreme mega-script}

\end{comment}

\section{Acknowledgments}

Thanks to Laurie Amster-Burton, Gunther Schmidl, and Gabriel
Zachmann for looking over drafts of this document, and to Don
Knuth for creating the world's most powerful and maddeningly
satisfying typesetting system.

\section{Copyright}

The 1.0 release of this document will include \LaTeX source and
will be licensed under the \GNU Free Documentation License.  This
draft, however, is \copyright\ 2002 Matthew Amster-Burton and may
not be modified.

\begin{comment}
Copyright \copyright\ 2002 Matthew Amster-Burton. Permission is
granted to copy, distribute and/or modify this document under the
terms of the \GNU Free Documentation License, Version 1.1 or any
later version published by the Free Software Foundation; with the
Invariant Sections being no Invariant Sections, with the
Front-Cover Texts being no Front-Cover Texts, and with the
Back-Cover Texts being no Back-Cover Texts. A copy of the license
is included in the section entitled ``\GNU Free Documentation
License.''
\end{comment}

\begin{comment}
\section{GNU Free Documentation License}

Version 1.1, March 2000\\

\noindent Copyright \textcopyright\ 2000  Free Software Foundation, Inc.\\
     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA\\
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

\subsection*{Preamble}

The purpose of this License is to make a manual, textbook, or
other written document ``free'' in the sense of freedom: to assure
everyone the effective freedom to copy and redistribute it, with
or without modifying it, either commercially or noncommercially.
Secondarily, this License preserves for the author and publisher a
way to get credit for their work, while not being considered
responsible for modifications made by others.

This License is a kind of ``copyleft'', which means that
derivative works of the document must themselves be free in the
same sense.  It complements the \GNU General Public License, which
is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for
free software, because free software needs free documentation: a
free program should come with manuals providing the same freedoms
that the software does.  But this License is not limited to
software manuals; it can be used for any textual work, regardless
of subject matter or whether it is published as a printed book.
We recommend this License principally for works whose purpose is
instruction or reference.

\subsection{Applicability and Definitions}

This License applies to any manual or other work that contains a
notice placed by the copyright holder saying it can be distributed
under the terms of this License.  The ``Document'', below, refers
to any such manual or work.  Any member of the public is a
licensee, and is addressed as ``you''.

A ``Modified Version'' of the Document means any work containing
the Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.

A ``Secondary Section'' is a named appendix or a front-matter
section of the Document that deals exclusively with the
relationship of the publishers or authors of the Document to the
Document's overall subject (or to related matters) and contains
nothing that could fall directly within that overall subject.
(For example, if the Document is in part a textbook of
mathematics, a Secondary Section may not explain any mathematics.)
The relationship could be a matter of historical connection with
the subject or with related matters, or of legal, commercial,
philosophical, ethical or political position regarding them.

The ``Invariant Sections'' are certain Secondary Sections whose
titles are designated, as being those of Invariant Sections, in
the notice that says that the Document is released under this
License.

The ``Cover Texts'' are certain short passages of text that are
listed, as Front-Cover Texts or Back-Cover Texts, in the notice
that says that the Document is released under this License.

A ``Transparent'' copy of the Document means a machine-readable
copy, represented in a format whose specification is available to
the general public, whose contents can be viewed and edited
directly and straightforwardly with generic text editors or (for
images composed of pixels) generic paint programs or (for
drawings) some widely available drawing editor, and that is
suitable for input to text formatters or for automatic translation
to a variety of formats suitable for input to text formatters.  A
copy made in an otherwise Transparent file format whose markup has
been designed to thwart or discourage subsequent modification by
readers is not Transparent.  A copy that is not ``Transparent'' is
called ``Opaque''.

Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, \LaTeX~input format,
\acro{SGML} or \acro{XML} using a publicly available DTD, and
standard-conforming simple \acro{HTML} designed for human
modification. Opaque formats include PostScript, \acro{PDF},
proprietary formats that can be read and edited only by
proprietary word processors, \acro{SGML} or \acro{XML} for which
the \acro{DTD} and/or processing tools are not generally
available, and the machine-generated \acro{HTML} produced by some
word processors for output purposes only.

The ``Title Page'' means, for a printed book, the title page
itself, plus such following pages as are needed to hold, legibly,
the material this License requires to appear in the title page.
For works in formats which do not have any title page as such,
``Title Page'' means the text near the most prominent appearance
of the work's title, preceding the beginning of the body of the
text.


\subsection{Verbatim Copying}

You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License
applies to the Document are reproduced in all copies, and that you
add no other conditions whatsoever to those of this License.  You
may not use technical measures to obstruct or control the reading
or further copying of the copies you make or distribute.  However,
you may accept compensation in exchange for copies.  If you
distribute a large enough number of copies you must also follow
the conditions in section 3.

You may also lend copies, under the same conditions stated above,
and you may publicly display copies.


\subsection{Copying in Quantity}

If you publish printed copies of the Document numbering more than
100, and the Document's license notice requires Cover Texts, you
must enclose the copies in covers that carry, clearly and legibly,
all these Cover Texts: Front-Cover Texts on the front cover, and
Back-Cover Texts on the back cover.  Both covers must also clearly
and legibly identify you as the publisher of these copies.  The
front cover must present the full title with all words of the
title equally prominent and visible.  You may add other material
on the covers in addition. Copying with changes limited to the
covers, as long as they preserve the title of the Document and
satisfy these conditions, can be treated as verbatim copying in
other respects.

If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto
adjacent pages.

If you publish or distribute Opaque copies of the Document
numbering more than 100, you must either include a
machine-readable Transparent copy along with each Opaque copy, or
state in or with each Opaque copy a publicly-accessible
com\-puter-network location containing a complete Transparent copy
of the Document, free of added material, which the general
network-using public has access to download anonymously at no
charge using public-standard network protocols.  If you use the
latter option, you must take reasonably prudent steps, when you
begin distribution of Opaque copies in quantity, to ensure that
this Transparent copy will remain thus accessible at the stated
location until at least one year after the last time you
distribute an Opaque copy (directly or through your agents or
retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of
the Document well before redistributing any large number of
copies, to give them a chance to provide you with an updated
version of the Document.


\subsection{Modifications}

You may copy and distribute a Modified Version of the Document
under the conditions of sections 2 and 3 above, provided that you
release the Modified Version under precisely this License, with
the Modified Version filling the role of the Document, thus
licensing distribution and modification of the Modified Version to
whoever possesses a copy of it.  In addition, you must do these
things in the Modified Version:

\begin{itemize}

\item Use in the Title Page (and on the covers, if any) a title
distinct
   from that of the Document, and from those of previous versions
   (which should, if there were any, be listed in the History section
   of the Document).  You may use the same title as a previous version
   if the original publisher of that version gives permission.
\item List on the Title Page, as authors, one or more persons or
entities
   responsible for authorship of the modifications in the Modified
   Version, together with at least five of the principal authors of the
   Document (all of its principal authors, if it has less than five).
\item State on the Title page the name of the publisher of the
   Modified Version, as the publisher.
\item Preserve all the copyright notices of the Document. \item
Add an appropriate copyright notice for your modifications
   adjacent to the other copyright notices.
\item Include, immediately after the copyright notices, a license
notice
   giving the public permission to use the Modified Version under the
   terms of this License, in the form shown in the Addendum below.
\item Preserve in that license notice the full lists of Invariant
Sections
   and required Cover Texts given in the Document's license notice.
\item Include an unaltered copy of this License. \item Preserve
the section entitled ``History'', and its title, and add to
   it an item stating at least the title, year, new authors, and
   publisher of the Modified Version as given on the Title Page.  If
   there is no section entitled ``History'' in the Document, create one
   stating the title, year, authors, and publisher of the Document as
   given on its Title Page, then add an item describing the Modified
   Version as stated in the previous sentence.
\item Preserve the network location, if any, given in the Document
for
   public access to a Transparent copy of the Document, and likewise
   the network locations given in the Document for previous versions
   it was based on.  These may be placed in the ``History'' section.
   You may omit a network location for a work that was published at
   least four years before the Document itself, or if the original
   publisher of the version it refers to gives permission.
\item In any section entitled ``Acknowledgements'' or
``Dedications'',
   preserve the section's title, and preserve in the section all the
   substance and tone of each of the contributor acknowledgements
   and/or dedications given therein.
\item Preserve all the Invariant Sections of the Document,
   unaltered in their text and in their titles.  Section numbers
   or the equivalent are not considered part of the section titles.
\item Delete any section entitled ``Endorsements''.  Such a
section
   may not be included in the Modified Version.
\item Do not retitle any existing section as ``Endorsements''
   or to conflict in title with any Invariant Section.

\end{itemize}

If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no
material copied from the Document, you may at your option
designate some or all of these sections as invariant.  To do this,
add their titles to the list of Invariant Sections in the Modified
Version's license notice. These titles must be distinct from any
other section titles.

You may add a section entitled ``Endorsements'', provided it
contains nothing but endorsements of your Modified Version by
various parties -- for example, statements of peer review or that
the text has been approved by an organization as the authoritative
definition of a standard.

You may add a passage of up to five words as a Front-Cover Text,
and a passage of up to 25 words as a Back-Cover Text, to the end
of the list of Cover Texts in the Modified Version.  Only one
passage of Front-Cover Text and one of Back-Cover Text may be
added by (or through arrangements made by) any one entity.  If the
Document already includes a cover text for the same cover,
previously added by you or by arrangement made by the same entity
you are acting on behalf of, you may not add another; but you may
replace the old one, on explicit permission from the previous
publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this
License give permission to use their names for publicity for or to
assert or imply endorsement of any Modified Version.


\subsection{Combining Documents}

You may combine the Document with other documents released under
this License, under the terms defined in section 4 above for
modified versions, provided that you include in the combination
all of the Invariant Sections of all of the original documents,
unmodified, and list them all as Invariant Sections of your
combined work in its license notice.

The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a
single copy.  If there are multiple Invariant Sections with the
same name but different contents, make the title of each such
section unique by adding at the end of it, in parentheses, the
name of the original author or publisher of that section if known,
or else a unique number. Make the same adjustment to the section
titles in the list of Invariant Sections in the license notice of
the combined work.

In the combination, you must combine any sections entitled
``History'' in the various original documents, forming one section
entitled ``History''; likewise combine any sections entitled
``Acknowledgements'', and any sections entitled ``Dedications''.
You must delete all sections entitled ``Endorsements.''


\subsection{Collections of Documents}

You may make a collection consisting of the Document and other
documents released under this License, and replace the individual
copies of this License in the various documents with a single copy
that is included in the collection, provided that you follow the
rules of this License for verbatim copying of each of the
documents in all other respects.

You may extract a single document from such a collection, and
distribute it individually under this License, provided you insert
a copy of this License into the extracted document, and follow
this License in all other respects regarding verbatim copying of
that document.



\subsection{Aggregation With Independent Works}

A compilation of the Document or its derivatives with other
separate and independent documents or works, in or on a volume of
a storage or distribution medium, does not as a whole count as a
Modified Version of the Document, provided no compilation
copyright is claimed for the compilation.  Such a compilation is
called an ``aggregate'', and this License does not apply to the
other self-contained works thus compiled with the Document, on
account of their being thus compiled, if they are not themselves
derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one
quarter of the entire aggregate, the Document's Cover Texts may be
placed on covers that surround only the Document within the
aggregate. Otherwise they must appear on covers around the whole
aggregate.


\subsection{Translation}

Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section
4. Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
translations of some or all Invariant Sections in addition to the
original versions of these Invariant Sections.  You may include a
translation of this License provided that you also include the
original English version of this License.  In case of a
disagreement between the translation and the original English
version of this License, the original English version will
prevail.


\subsection{Termination}

You may not copy, modify, sublicense, or distribute the Document
except as expressly provided for under this License.  Any other
attempt to copy, modify, sublicense or distribute the Document is
void, and will automatically terminate your rights under this
License.  However, parties who have received copies, or rights,
from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.


\subsection{Future Revisions of This License}

The Free Software Foundation may publish new, revised versions of
the \GNU Free Documentation License from time to time.  Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
http://www.gnu.org/copyleft/.

Each version of the License is given a distinguishing version
number. If the Document specifies that a particular numbered
version of this License "or any later version" applies to it, you
have the option of following the terms and conditions either of
that specified version or of any later version that has been
published (not as a draft) by the Free Software Foundation.  If
the Document does not specify a version number of this License,
you may choose any version ever published (not as a draft) by the
Free Software Foundation.

\subsection*{ADDENDUM: How to use this License for your documents}

To use this License in a document you have written, include a copy
of the License in the document and put the following copyright and
license notices just after the title page:

\begin{quote}

      Copyright \copyright\ YEAR  YOUR NAME.
      Permission is granted to copy, distribute and/or modify this document
      under the terms of the \GNU Free Documentation License, Version 1.1
      or any later version published by the Free Software Foundation;
      with the Invariant Sections being LIST THEIR TITLES, with the
      Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
      A copy of the license is included in the section entitled ``\GNU
      Free Documentation License''.

\end{quote}

If you have no Invariant Sections, write ``with no Invariant
Sections'' instead of saying which ones are invariant.  If you
have no Front-Cover Texts, write ``no Front-Cover Texts'' instead
of ``Front-Cover Texts being LIST''; likewise for Back-Cover
Texts.

If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice
of free software license, such as the \GNU General Public License,
to permit their use in free software.
\end{comment}
\end{document}
