07.10.2014 Views

Complete issue 10:1 as one pdf - TUG

Complete issue 10:1 as one pdf - TUG

Complete issue 10:1 as one pdf - TUG

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>TUG</strong>boat, Volume <strong>10</strong> (1989), No. 1<br />

16. PostScript fonts can be extended so that arbitrary<br />

PostScript procedures can be executed in<br />

place of certain character codes.<br />

17. The inclusion of PostScript figures in 7&X<br />

documents is possible with macros of the psfig<br />

macro package.<br />

18. Figures generated with tpic can be included<br />

into a document.<br />

19. X Window screen dumps (X11.3) can be included<br />

into a rn document.<br />

An Overview<br />

The data flow diagram contains an overview of the<br />

T)QQS Software Package. Observe that this figure<br />

contains <strong>as</strong> subdiagram the flow of information when<br />

generating fonts with METAFONT and processing a<br />

document by rn using METAFONT b<strong>as</strong>ed fonts.<br />

The left side of the figure shows the programs<br />

added by 7JJKpS. The pfd2tfm program generates<br />

TFM files from AFM files and PFD files. PFD files<br />

contain, for instance, encoding vector specifications.<br />

The resulting TFM files are read in by rn to<br />

produce a document with PostScript fonts.<br />

The<br />

pfd2tfm program may read in TFM files itself for the<br />

purpose of font emulation. The pfd2tfm program<br />

also produces PDR files which are read in by dvitps.<br />

These PDR files contain width information and<br />

encoding vector information which is needed by<br />

dvitps.<br />

Observe also that tpic can be used with our<br />

dvitps. tpic generates a TEX source code file which<br />

in turn generates \specials which are included into<br />

the DVI file.<br />

Finally with the help of the psfig macros, Post-<br />

Script b<strong>as</strong>ed figures generated by some program<br />

X.. . PS can be included into a rn document.<br />

Such a program should but does not need to<br />

generate a bounding box comment in its Postscript<br />

output which is read in by the psfig macros to<br />

reserve the proper space in the TkX document. The<br />

rest of the PostScript file is discarded by W, and<br />

only read in by dvitps.<br />

PRO files menti<strong>one</strong>d in the figure are prologue<br />

files which contain certain standard PostScript definitions<br />

read in by dvitps.<br />

Availability<br />

The software of the TEX@~ package consists of the<br />

following parts:<br />

1. Source code for the three b<strong>as</strong>ic programs dvitps,<br />

pfd2tfm and printpdr.<br />

2. The I4m source of a 150 page document<br />

describing the software.<br />

3. Manual pages.<br />

4. The b<strong>as</strong>ic set of AFM files needed to produce<br />

the corresponding TFM and PDR files.<br />

5. The sources of pltotf (needed by pfd2tfm) and<br />

of maketd, a program to compute dependencies<br />

of C program sources.<br />

The software is made available in the following two<br />

ways:<br />

1. Use ftp to the machine csseq. tamu. edu and<br />

retrieve the file dvitps. tar. Z from there.<br />

2. Send $80.00 ($1<strong>10</strong>.00 outside the continental<br />

US, shipped air mail) to Stephan v. Bechtolsheim,<br />

2119 Old Oak Drive, West Lafayette, IN<br />

47906 and you will receive a SUN cartridge<br />

plus a complete set of the documentation.<br />

Acknowledgements<br />

The software w<strong>as</strong> developed by the author <strong>as</strong> part of<br />

a consulting contract with the Menil Foundation in<br />

Houston, Tex<strong>as</strong>. It w<strong>as</strong> a combined decision by the<br />

author of this software and the Menil Foundation to<br />

make this software available to the community<br />

at large.<br />

My email address is svb@cssun . t amu . edu. Feel<br />

free to contact me for further information.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!