DataMuseum.dk

top - metrics - download

    Length: 4847 (0x12ef)
    Types: TextFile
    Names: »usage.tex«

└─⟦52210d11f⟧ Bits:30007239 EUUGD2: TeX 3 1992-12
    └─⟦af5ba6c8e⟧ »unix3.0/DVIWARE.tar.Z« 
        └─⟦ca79c7339⟧ 
            └─⟦this⟧ »DVIware/laser-setters/dvi-to-ps/TeXPS/doc/usage.tex« 

TextFile

% Psfig macros are needed to include the manual pages.
\InputD{../psfig/psfig.tex}

\chapter{Usage, Manual Pages}
% ===========================
\label{c-usage}
	In this chapter I will provide a brief summary of the usage of all the
programs. If you are lucky and you have TranScript available, then the
manual pages are included here. The {\tt troff} source of these manual
pages was converted into \PS{} with the help of TranScript, and the
resulting \PS{} code was included into this document using the psfig
macros of \ChapterRef{c-psfig}, \page{}.

	Observe that the manual pages contain installation dependent data:
all defaults listed in the manual pages depend on your installation. You
therefore have to reprocess all manual pages if you change any of the
defaults in {\tt local-defs}.

	The manual pages can be found in directory {\tt man}.

\section{Options}
% ===============
	All programs handed options the same way. Assume a program has
two options~{\tt -a} and~{\tt -b} without argument, then you can write {\tt
-a~-b} or~{\tt -ab}.

	Assume option~{\tt -c} takes one argument, a number. Then you can write~{\tt
-c20} (without space between the option and the argument to the option) or
\verb*+-c 20+ (with space between the option and its argument).

\section{The Usage of {\tt dvitps}}
% =================================
\label{s-dvitps-man}
	I recommend that you read the later following manual page about the
driver carefully. It explains:
\begin{enumerate}
	\item Which environment variables are understood by the driver. For
		instance, these environment variables allow you to specify search paths
		individually for each of the font file types.
	\item How you determine which font file types the driver will
		look for and in which order.
	\item How certain options can be automatically added each time the
		driver is invoked.
\end{enumerate}

\subsection{{\tt -Q} Option}
% ==========================
The {\tt -Q} option of the driver is used to invoke various testing features. This
option is always followed by a number which specifies which testing
option is invoked.  Here is a list of those numbers and which testing
option they invoke.
\begin{enumerate}
	\item Generate statistcs oriented output. The output will be split up
		into three separate files: one containing the prologue parts, one
		containing the parts generated by pass~0 and one generated by
		pass~1. These output files cannot be used to print the document.
		They are only generated to be able to determine how long the
		various parts of a \PS{} file generated by the driver really are.
	\item All movements are absolute. Rounding occurs to the nearest
		pixel, no maxdrift control in particular.
	\item Debugging output of the input and output routines (from and to
		files) contained in the library is generated.
	\item File caching debugging output is generated.
	\item Warnings are generated if the difference between the to pixel
		rounded {\tt tfm} width and the pixel width of characters exceeds
		a certain threshold value.
\end{enumerate}

\section{Usage of {\tt pfd2tfm}}
% ==============================
\label{s-pfd2tfm-man}
	The details of the usage of this program is explained in the later
following manual page.

	Let me quickly explain here that it is {\it not\/} mandatory to use
a {\tt PFD} file to generate a {\tt TFM} and {\tt PDR} file. Instead an {\tt AFM} file can
be used directly. IF this is done as in {\tt pfd2tfm Helvetica.afm}, then
the file extension {\tt .afm} must be specified ({\tt pfd2tfm Helvetica}
would cause {\tt pfd2tfm} to look for {\tt Helvetica.pfd}). Note that {\tt
pfd2tfm Helvetica} is equivalent to {\tt pfd2tfm PS-Helvetica.pfd}, where
{\tt PS-Helvetica.pfd} reads as follows:
\btex
StartPfd;
BaseFontName "Helvetica";
EndPfd;
\etex

\section{Usage of {\tt printpdr}}
% =================================
\label{s-printpdr-man}
	Again see the later following manual pages for details.

\section{The Manual Pages}
% ========================
	Now I will reprint the manual pages of the \TeXPS{} software.
If you go to directory {\tt man} and run {\tt make install}, then these manual
pages will also be installed.

% The dimensions in the following macro to include the manual pages
% of the various programs were found by trial and error.
%
% \ManualPageInclude
% ==================
% #1: file name of the file to be included.
\def\ManPageInclude #1{% 
	\clearpage
	\vbox to 1.75in{}
	\vbox{
			\psfig{figure=../man/#1.ps,% 
				bbllx=0pt,% 
				bblly=0pt,% 
				bburx=6.0in,% 
				bbury=8.0in,% 
				width=5.0in,% 
				height=6.6666in}
		\vskip -1.75in
		}
	\clearpage
}

% The file "../mac/docman.tex" can be either of the following:
% 1. It can be a bunch of calls to \ManPageInclude.
% 2. It can be a bunch of verbatim listings of the manual pages.
% 3. It can be empty.
\input ../man/docman.tex