perm filename TEX.INS[CLS,LSP] blob sn#859601
filedate 1988-07-18 generic text, type C, neo UTF8
COMMENT ⊗ VALID 00002 PAGES
C REC PAGE DESCRIPTION
C00002 00002 How to TEX the CLOS Specification
How to TEX the CLOS Specification
There are 2 source files and 2 macro/font files that you need to
TEX the CLOS specification (I use upper case for file names and for TEX):
CONCEP.TEX ;source file
FUNCTI.TEX ;source file
MACROS.TEX ;macros file
These files are on SAIL.STANFORD.EDU, and the full name of the first
You will need only one of the two fonts files, but that depends on the
status of the TEX at your site. Your best bet for determining which to use
is to take them both and try TEXing one of the source files and seeing
whether it works.
In MACROS.TEX there are two lines:
If your site supports the up-to-date Computer Modern family of fonts,
this configuration of these two lines will work. Otherwise, your site supports
the older Almost Modern family, and you should edit MACROS.TEX so that those
two lines look like this:
``%'' is the comment character in TEX.
The TEX macros produce a table of contents, but in a peculiar way.
You will need to create three files, one for each of the source files:
When TEX runs, it inputs the .TC file from the previous TEX run to produce
the table of contents. TEX outputs a .TOC file, which is the table of
contents for the current run of TEX. Therefore, after you run TEX the
first time over CONCEP.TEX, you will see a new file:
Because there was no previous TEXing on CONCEP before this, you will need
to TEX CONCEPT.TEX twice to produce a reasonable table of contents for
CONCEP with that table of contents in place in the document.
In any event, here's what you do to TEX CONCEP:
<create a CONCEP.TC> ;do this only the very first time you TEX
<replace CONCEP.TC with CONCEP.TOC> ; for example, in UNIX
; cp concep.toc concep.tc
You do a similar operation for FUNCTI.
There is one last adjustment you might have to do. Suppose that you TEX
a file and your printer places some of it off of the page, but otherwise
it looks good. There are two lines in MACROS.TEX that help with this,
but they are commented out:
These are commented out because TEX on SAIL does not need non-zero
offsets to work, while at Lucid we do need such an offset. You will
simply have to look at the output to decide.
If you don't believe that the table of contents will have changed
from the previous TEX run, you can omit the replacement and second TEX
There might be a fair number of underfull and overfull box warnings, which
you can ignore.