Printing Postscript-files:
--------------------------
Postscript files are usually ending in .ps and are plain ascii-files.
The first line always begins with %! and usually looks like

%!PS-Adobe-2.0

The file foo.ps can then be printed saying
   gspr foo.ps
CAVEAT: To save space, no fonts are provided with ghostscript. They
are not needed to print converted DVI files. If you print something
containing non DVI-converted text, everythin gets printed in the
same (ugly) standard font.

Of course if you do have a Postscript printer, you can delete the
/usr/local/bin and /usr/local/lib/ghostscript part of the package
and simply pipe the .ps files to your printer in the way you prefer
(and they look nice too, of course).

Printing Unix (i.e. troff) manpages:
------------------------------------
Manpages usually end in .1 .2 , ..., .8, .n  or .man. You need to convert
them to Postscript or DVI (see later on these) using groff.
Groff is NOT part of this package (would make it too big and most
people have it anyway).
The man-page foo.1 can be converted to DVI by:
  groff -Tdvi -man foo.1 > foo.dvi
The man-page foo.1 can be converted to Postscript by:
  groff -Tps -man foo.1 > foo.ps
(For the second one you need to have ps support in your groff,
which standard SLS distribution does not have, and if you dont have
a real Postscript-printer, it won't be of any use with this distribution
anyway because ghostscript fonts are not supplied).


Printing DVI-files:
-------------------
DVI-files usually end in .dvi. They can be recognized by the file
command if you have the appropriate entry in /etc/magic.
Put the lines
#
# magic.tex:
#
0       short   0173402 DVI File
>16     string  >\0     (%s)
0       short   0173531 Packed TeX Font
>4      string  >\0     (%s)
2       string  \000\022        Metafont Font Metric
>34     string  >\0     (%s)
somewhere in your /etc/magic file if they aren't already there. Then
   file foo.dvi
should output
   DVI File
if that one is a DVI file.
To print them you have to convert them to Postscript using dvips. To
convert foo.dvi to Postscript just say:
   dvips foo
producing foo.ps
The other method to print them is using dvilj2 or dvilj2p, which is what
you must do if you have a HP-Laserjet (or HP-Laserjet 2+) compatible
laserprinter with limited ( < say 1 MB) memory which can't store a full
bitmap of a page. Just say
   dvilj2 foo
producing foo.lj which can be sent directly to the printer (No NL->CR/NL
conversion needed) e.g. by saying
   cat foo.lj > /dev/lp1
With either method it may (and will in the beginning) happen, that some
fonts TeX requests are not found. In this case Metafont is automatically
called, rasterizing the requested font in the requested size for your
printer. This takes some time (1/2 min per font on a 486/33) but only
occurs the very first time a specific font in a specific size is requested.
Printing the same document later is much quicker.


Printing TeX-files:
-------------------
TeX-files usually end in .tex. They are plain ascii-files usually
with a header of some cryptic looking commands starting with backslashes
and some quite legible text with occasional commands later.
You first need to convert foo.tex to a DVI File saying
   tex foo
(If some error occurs, simply type return on every question, often
TeX is able to produce something useful even on erroneous input.
If TeX can't find a file it will prompt you for a substitution
Simply typing return will not help here, so type  null  in response
making TeX happy with a provided (empty) dummy file.)
This may produce a lot of foo.* files (at least foo.log and foo.dvi)
of which only the .dvi file is needed for printing. See above.

Printing LaTeX-files:
---------------------
LaTeX-files end in .tex like TeX-files and can be distinguished from
TeX-files by searching for the string "\\documentstyle"
which should appear somewhere in the first lines or following an initial
comment (=lines starting with %). foo.tex can be converted to a DVI file saying
   latex foo
To resolve cross-references, it is often necessary to give this command
a second time. You will get a message at the end of the first run, telling
you that, if necessary. If the document produces an index automatically,
you have to make a second run and between the two runs issue the command
   makeindex foo
to produce the sorted and merged index.
Every other thing said for TeX applies to LaTeX too which is no surprise
because it's the same program.

Printing Texinfo files:
-----------------------
Texinfo files usually end in .texi or .texinfo. They can be distinguished by
searching for the string "\\input texinfo" which should appear somewhere
in the first lines. They can be treated exactly like TeX-files, i.e.
   tex foo.texinfo
will produce foo.dvi and a lot of other files. To produce an index here,
you have to use the texindex saying e.g.
   texindex foo.cp
producing foo.cps, and so on for every file foo.??s you got a message telling
it couldn't be found. (most common are foo.cp, foo.fn, foo.ky)
