Assuming you've installed everything, double-click on the
application file to get the program started.
After a brief pause you should see a window with the title ``''
and a couple of messages showing the current version of and
the path name of the Default configuration file just loaded.
The Default file's list of PostScript fonts contains references
to an encoding file, so it will also be loaded. If you made a mistake during installation, or when editing
the Default file, then you might also get one or more error messages.
The messages should give you some idea of how to fix the problem.
The window is always present; note that it has no close box
in the top left corner.
This window provides a terminal-like interface for .
It cannot be edited, but you can copy its contents to the Clipboard
or save it to a text file.
You can also start up by double-clicking on any -created file
ending in .xxx
; e.g., foo.log
or foo.dvi
.
The advantage of this start up method is that foo.tex
will appear in
the TEX menu and foo.dvi
will appear in the Print and View menus.
Also, if foo.log
exists and contains a known format then will
automatically make this the current format so you can immediately typeset
foo.tex
by hitting Command-T.
If foo.tex
can't be found then will look for foo.ltx
(this is a popular file naming scheme used to distinguish LATEX input files).
Under System 7, you can drag-and-drop foo.tex
or foo.ltx
onto the icon and will immediately typeset the file.
The production of a TEX document typically involves a number of iterations
through the following cycle: edit, typeset, preview and print.
(People concerned about our dwindling forests will hopefully preview
many more times than they print.)
Let's go through this cycle step by step.