⟦bd7f71df1⟧

TextFile

\hyphenation{Bech-tols-heim}
\hyphenation{dri-ver}
\hyphenation{dri-vers}
\hyphenation{ex-e-cu-ted}
\hyphenation{test-bed}
\font\MetafontLogoFont = logo10 scaled \magstep0
\def\MF{{\MetafontLogoFont METAFONT}}
\font\sc = cmcsc10
\def\PS{{\sc Post\-Script}}
\def\TeXPS{\TeX\kern-.1667em\raise-.5ex\hbox{P}\kern-.125emS}

\section{Introduction}
% ====================
	I will now describe the basics of the \TeXPS{} Software Package. \TeXPS{} stands for
\TeX{}--\PS{}. This package contains, among other things, a new {\tt DVI} to \PS{}
driver, and the facility to use \PS{} fonts in \TeX.

	The software's copyright is in the GNU spirit (Free Software
Foundation, Cambridge, MA). The software is free except for a nominal distribution
charge for those of you who order the software because you have no access
to ftp. The software must be passed on according to the same
terms: the sofware must essentially be free.  This is also true if you
port this software to a different operating system.

\section{Features of the \TeXPS{} Software Package}
% =================================================
	Here is a list of features of the \TeXPS{} Software Package. The main
emphasis in this list will be on {\tt dvitps}, the {\tt DVI} to \PS{}
driver, because it forms the central part of this software package. It is
also the most frequently used program of this package.
\begin{enumerate}
	\item The software runs under UNIX (currently tes\-ted on VAXes and
		SUNs (BSD 4.x)); ports to other flavors of UNIX should be straight forward. 
	\item The software is {\it very easy to install}. A central file
		contains all necessary setup data and a shell script is used to
		generate the proper makefiles.
	\item The software comes with a {\it 160~page manual\/} explaining
		the software very thoroughly.  The manual contains numerous examples intended to
		be a testbed for the software.
	\item {\it Manual pages\/} (done in {\it troff \dots\/}) for all
		programs are provided.
	\item The software was {\it tested carefully\/} at various places.
		It  therefore should perform according to its specification. 
		Continuous support by the author of the software will be provided.
	\item The driver {\tt dvitps} supports all three pixel based font file types ({\tt PXL}, {\tt GF},
		{\tt PK}). Pixel based fonts may have up to 256 characters.
	\item The software allows using  {\it\PS{} fonts with \TeX\/}! For
		that purpose the program {\tt pfd2tfm} was included with the
		following two purposes.
		\begin{enumerate}
			\item The {\tt pfd2tfm} program converts {\tt AFM} files into {\tt TFM}
				files, which containt the necessary font metric
				information for \TeX. Ligature and kerning information
				from {\tt AFM} files is also used by {\tt pfd2tfm}.
			\item This program also generates {\tt PDR} files which are
				accessed by the driver {\tt dvitps} to print documents using \PS{}
				fonts.
		\end{enumerate}
	\item \PS{} fonts can be {\it tilted}, {\it stretched}, and {\it modified\/} in various other
		ways.
	\item \PS{} fonts can be used at any size, not only the standard
		\verb+\magstep+s. This, of course, follows from the fact that
		\PS{} fonts do not require using pixel files.
	\item The {\it encoding vector\/} of the \PS{} fonts can be specified
		by the user. Every character of a \PS{} font can be mapped to any
		character code. Defaults are provided making the encoding vector of
		\PS{} fonts to look as closely as possible to the ``encoding vectors'' of
		regular \TeX{} fonts.  This encoding vector is among the
		information stored in the previously mentioned {\tt PDR} files.
	\item Encoding vectors can be printed out using the program {\tt
		printpdr}. This program generates \TeX{} output so encoding
		vectors can be easily printed inside \TeX{} documents.
	\item It is {\tt dvitps} (not the \PS{} interpreter inside the
		printer used for printing) which is ``in charge of positioning.'' {\tt dvitps} generates only
		integer position coordinates and movements. The term ``integer''
		refers here to the resolution of the \PS{} printer.
		As a consequence it was possible to make {\tt dvitps}
		follow the rules of {\it dvitype}, the model device driver,
		precisely. {\tt dvitps} includes, for instance, a maxdrift
		control according to the rules of {\tt dvitype}.
	\item {\tt dvitps} has an option to {\it reset the virtual memory of the
		\PS{} printer\/} every~$n$ pages.
	\item {\tt dvitps} has an option to {\it show all attempts to locate font
		files}. This allows the user to clearly see the driver's attempt
		to locate font files.
	\item {\tt dvitps} has an option to {\it generate ``conforming
		documents,''} i.e., \PS{} files conforming to the standard defined by Adobe, Inc. 
		Such \PS{} files  can then be included into other \PS{} documents. Therefore it
		also possible to include one \TeX{} document within another \TeX{} document.
	\item {\tt dvitps} is equipped with a sophisticated font substitution
		algorithm which makes {\tt dvitps} to look for replacement pixel
		files in case a requested pixel file cannot be found.
	\item {\it Font emulation\/} is provided. In font emulation the
		spacing and positioning of characters within \TeX{} refers to one
		{\tt TFM} file but printing by {\tt dvitps} is done using a different
		font, in particular using a font with a different {\tt TFM} file.
		This feature can be used to reprint a document which was
		generated with fonts and {\tt TFM} files for which no
		pixel files are available.

			This situation occurs when native
		fonts of phototypesetters are used and when the manufacturer of the phototypesetter
		fonts makes no pixel files available for those fonts. It is then
		not possible to generate proofs of such documents on laser
		printers. Font emulation allows one to reprint the text without
		distorting the linebreaks and pagebreaks.
	\item \PS{} fonts can be extended so that {\it arbitrary \PS{} procedures
		can be executed\/} for certain characters.
	\item The {\it inclusion of \PS{} figures in \TeX{} documents\/} is possible
		with macros of the psfig macro package. Concerning the psfig
		macros please note:
		\begin{enumerate}
			\item The version number of psfig as released with software
				is 1.4.
			\item A parameter {\tt scale} was added to the \verb+\psfig+
				macro which allows uniform scaling of an included figure in horizontal and vertical
				direction.
			\item A patch to the {\tt xpr} utility of X~Windows 11.3 is
				included. When this patch is applied {\tt xpr} generates
				a conforming \PS{} file which includes a ``bounding box
				comment.'' This makes such file usable by \verb+\psfig+,
				and therefore it is possible to include X~Window screen dumps into a document.
		\end{enumerate}
	\item {\it Figures generated with the tpic\/} can be included into a \TeX{} document.
\end{enumerate}

\section{An Overview}
% ===================
	Fig.~\ref{f-data-flow}, p.~\pageref{f-data-flow}, contains an overview of the
\TeXPS{} Software Package. Observe that this figure contains
as subdiagram the flow of information generating font files with \MF{},
and also the information of processing a document by \TeX{} using \MF{}
based fonts.

\begin{figure}
\setlength{\unitlength}{0.8mm}
\begin{picture}(185,200)(0,0)
\def\MyCircle(#1,#2)#3{% 
	\put(#1,#2){\circle{10}}% 
	\put(#1,#2){\makebox(0,0){#3}}
}
\put(25,160){\framebox(30,15){{\tt pfd2tfm}}}
\put(105,160){\framebox(30,15){\MF}}
\put(45,30){\framebox(30,15){{\tt dvitps}}}
\put(10,100){\framebox(15,10){{\tt tpic}}}
\put(155,140){\framebox(30,15){{\tt X\dots PS}}}
\put(115,110){\framebox(30,15){{\tt gftopk}}}
\put(45,85){\framebox(30,15){\TeX}}
\put(65,140){\framebox(20,10){{\tt pltotf}}}
\put(50,160){\vector(0,-1){10}}
\MyCircle(50,145){{\tt TFM}}
\put(50,140){\vector(0,-1){40}}
\put(110,160){\vector(0,-1){10}}
\MyCircle(110,145){{\tt TFM}}
\put(110,140){\line(0,-1){10}}
\put(110,130){\vector(-1,0){60}}
\put(30,185){\vector(0,-1){10}} % AFM
\MyCircle(30,190){{\tt AFM}}
\put(50,185){\vector(0,-1){10}} % pfd
\MyCircle(50,190){{\tt PFD}}
\put(30,160){\vector(0,-1){10}}
\MyCircle(30,145){{\tt PDR}}
\put(30,140){\line(0,-1){102.5}}
\put(30,37.5){\vector(1,0){15}}
\MyCircle(120,190){{\tt MF}}
\put(120,185){\vector(0,-1){10}}
\put(130,160){\vector(0,-1){10}}
\MyCircle(130,145){{\tt GF}}
\put(130,140){\vector(0,-1){15}}
\put(130,110){\vector(0,-1){25}}
\MyCircle(130,80){{\tt PK}}
\put(130,75){\line(0,-1){20}}
\put(130,55){\line(-1,0){65}}
\put(65,55){\vector(0,-1){10}}
\put(60,85){\vector(0,-1){10}}
\MyCircle(60,70){{\tt DVI}}
\put(60,65){\vector(0,-1){20}}
\put(60,155){\vector(-1,1){5}} % pltotf and pfd2tfm
\put(60,155){\vector(1,-1){5}}
\MyCircle(10,167.5){{\tt TFM}}
\put(15,167.5){\vector(1,0){10}}
\put(25,105){\vector(1,0){45}}% from tpic to TeX
\MyCircle(70,115){{\tt TEX}}
\put(70,110){\vector(0,-1){10}}
\put(135,167.5){\line(1,0){10}}% from metafont (pxl)
\put(137,170){{(old \MF)}}
\put(145,167.5){\vector(0,-1){17.5}}
\MyCircle(145,145){{\tt PXL}}
\put(145,140){\line(0,-1){5}}
\put(145,135){\line(1,0){15}}
\put(160,135){\line(0,-1){95}}
\put(160,40){\vector(-1,0){85}}
\put(60,30){\vector(0,-1){10}}
\MyCircle(60,15){{\tt PS}}
\put(130,130){\line(1,0){20}}% gf line
\put(150,130){\line(0,-1){80}}
\put(150,50){\line(-1,0){80}}
\put(70,50){\vector(0,-1){5}}
\put(170,140){\vector(0,-1){10}}% line from X...ps
\MyCircle(170,125){{\tt PS}}
\put(170,120){\line(0,-1){85}}
\put(170,35){\vector(-1,0){95}}
\put(170,92.5){\vector(-1,0){95}}
\MyCircle(45,65){{\tt PRO}}	% .pro file
\put(45,60){\line(0,-1){5}}
\put(45,55){\line(1,0){5}}
\put(50,55){\vector(0,-1){10}}
\end{picture}
	\caption{A data flow diagram explaining the connection between \TeXPS{}, \TeX{} and \MF}
	\label{f-data-flow}
\end{figure}

	The left side of the figure shows the programs added by \TeXPS{}. {\tt pfd2tfm}
generates {\tt TFM} files from {\tt AFM} files and {\tt PFD} files.
The resulting {\tt TFM} files are read in by \TeX{} to produce a document with
\PS{} fonts.  The {\tt pfd2tfm} program may read in {\tt TFM} files
itself for the purpose of font emulation.
The {\tt pfd2tfm} program also produces {\tt PDR} files
which are read in by {\tt dvitps}. These {\tt PDR} files
contain width and encoding vector information which is needed by {\tt dvitps}.

	Observe also that {\tt tpic} can be used with {\tt dvitps}.
{\tt tpic} generates a \TeX{} source code file which in turn causes
{\tt\string\special}s written to the {\tt DVI} file. These {\tt
\string\special}s are then used by the driver to generate the figure.

	Finally, with the help of the psfig macros, \PS{} based figures and diagrams, generated by
some program {\tt X\dots PS} can be included into a \TeX{} document. Such program should, but does
not need to generate a bounding box comment (in its \PS{} output) which is read in
by \TeX{} to reserve the proper amount of space in the \TeX{} document. The rest of the \PS{}
file is discarded by \TeX, and only read in by {\tt dvitps}.

	{\tt PRO} files are prologue files, which contain certain standard \PS{}
definitions which are assumed to be be present when the \PS{} output of {\tt
dvitps} is printed. These prologue files are read in by the driver and
are made part of the output generated by it.

\section{Availability}
% ====================
\label{s-availability}

\subsection{Retrieving the Software}
% ==================================
The software can be accessed in two ways:
\begin{enumerate}
	\item Use anonymous ftp to  {\tt arthur.cs.purdue.edu}.
		\begin{enumerate}
			\item Enter {\tt tenex} mode (8-bit mode).
			\item Go to directory {\tt pub/TeXPS}.
			\item Get {\tt TeXPS-3.0.tar.Z}.
			\item Get patches {\tt TeXPS-Patch-3.0-3.1}, \ldots, from this
				machine.
		\end{enumerate}

		Now uncompress the software (\verb+uncompress TeXPS-R1.tar.Z+),
		which replaces file {\tt TeXPS-R1.tar.Z} with {\tt TeXPS-R1.tar}.
	\item Send \$80.00 (\$110.00 outside the continental US, shipped
		air mail) to Stephan v.~Bechtolsheim, 2119 Old Oak Drive,
		West Lafayette, IN 47906.
		You will will receive a SUN 1/4" cartridge with the complete
		software and  a complete set of the documentation.

			Once you receive the tape use \verb+tar xvf /dev/rst8+ to extract
		the information from the tape.
\end{enumerate}

\subsection{Untaring the Software}
% ================================
Whatever way you have accessed the software, here is how you now get all
the source files. Create a separate subdirectory; you probably will call
it {\tt TeXPS}.

\subsection{Main Directories of the Tape}
% =======================================
	After you untared the software you will find that the following
directories where generated:
\begin{enumerate}
	\item {\tt TeXPS}. The directory containing the \TeXPS{} software itself.
		This directory contains, among other directories, the following
		directories:
		\begin{enumerate}
			\item {\tt dvitps}. The driver software.
			\item {\tt pfd2tfm}. The conversion program reading {\tt PFD}
				and {\tt AFM} files to generate {\tt TFM} and {\tt PDR}
				files.
			\item {\tt doc}. The directory containing the 160 page long
				\LaTeX{} manual describing the software.
			\item {\tt man}. The directory containin the manual pages of
				the software.
			\item Other directories containing library functions and
				support programs.
		\end{enumerate}
	\item {\tt afm}. The basic set of {\tt AFM} files for all fonts of a
		Laser Writer~II type of printer. You might already have those files.
	\item {\tt pltotf}. The source code of {\tt pltotf}. You might
		already have the source files of this program.
	\item {\tt maketd}. The source code of {\tt maketd}, a
		program to compute dependencies of C~program sources.
\end{enumerate}
Note that a {\tt README} file on the top level will provide you with
further information.

\subsection{How to Contact Me}
% ============================
In case you want to get in touch with me as far as this software is
concerned, here is the necessary information. My email address is {\tt
svb@cssun.tamu.edu}.
My postal address is 2119 Old Oak Drive, West Lafayette, IN 47906.
My phone number is (317) 463 0162.

\section{Acknowledgements}
% ========================
	The software was developed by the author as part of a consulting contract
with the Menil Foundation in Houston, Texas.  It was a combined decision
by me and the Menil Foundation in Texas to make
this software available to the \TeX{} community at large.
DataMuseum.dk

DKUUG/EUUG Conference tapes

⟦bd7f71df1⟧ TextFile

Derivation

TextFile
