[comp.text.tex] Pre-processed version of the TeX Primer Now Available

JOE@OREGON.BITNET (03/05/91)

I've been sorry to hear that a number of people have had problems
building copies of my TeX Primer on some platforms....
 
To eliminate that problem, I've built a ready-to-copy-and-print PostScript
version of the TeX Primer that is now available for anonymous FTP from
DECOY.CC.UOREGON.EDU (128.223.32.19); login using userid anonymous (all
lowercase) and anything you want for the password. You can then cd to
pub/tex/processed to get a processed PostScript version of the TeX Primer.
 
The files you'll want to retrieve are:
 
    (1) cover.ps         (724 bytes)
    (2) tex_primer.ps    (371449 bytes)
    (3) app_a.ps         (89536 bytes)
    (4) app_b.ps         (22064 bytes)
    (5) app_c.ps         (66301 bytes)
    (6) app_d.ps         (58196 bytes)
    (7) app_e.ps         (45876 bytes)
    (8) app_f.ps         (32857 bytes)
    (9) app_f_a.ps       (9399 bytes)
   (10) app_g.ps         (201214 bytes)
   (11) myindex2.ps      (97877 bytes)
                         --------------
                         (995493 total bytes)
 
The .dvi files were built on our VAX 8800 running Northlake Software's TeX
2.991a under VMS 5.3-1, and then transferred in binary mode to DECOY. They
check out okay there using Tom Rokicki's NeXT TeXView previewer.
 
The .ps files were built directly on DECOY using Rokicki's dvips 5.396.
[I built them there because the version of dvips we run on our 8800 is set
up to use thickened fonts which are appropriate for our Xerox 4045/160,
but which would yield output that'd appear to be too thick when printed on
a typical Apple LaserWriter.] Depending on how your FTP implementation
handles line breaks, you may be able to transfer the PostScript files in
ASCII mode, or you may need to transfer them in binary mode to avoid having
weird spaces crop up where your FTP implementation adds CR/LF's to longish
lines.
 
I've also left the .dvi files in pub/tex/processed so that those of you
who'd like to build versions of the Primer for non-PostScript devices can
do so. Note that some parts of the Primer simply aren't going to print
if you aren't working in a PostScript environment (i.e., you won't be able
to print the cover or appendices f and g).
 
Naturally, if you elect to go with a pre-processed version of the TeX
Primer, you also won't be able to replace Oregon-specific references to
something that makes sense for your site, but at least you'll have a copy
of the Primer without having to go through major contortions.
 
Regards,
 
Joe St Sauver (JOE@OREGON.UOREGON.EDU or JOE@OREGON)