DataMuseum.dk

Presents historical artifacts from the history of:

DKUUG/EUUG Conference tapes

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about DKUUG/EUUG Conference tapes

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - metrics - download
Index: T a

⟦cf6fd8aa7⟧ TextFile

    Length: 3279 (0xccf)
    Types: TextFile
    Names: »appendix.tex«

Derivation

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

TextFile

\chapter{File Extensions}
% =======================
	Here is a brief summary of the important file extensions
in the context of these programs:
\begin{enumerate}
	\item {\tt afm}. Adobe font metric files. These are text files,
		which contain the font metric information of each of the \PS\
		fonts.
	\item {\tt dvi}. (Output) device independent files. Generated by
		\TeX, these files contain the typeset product in a format
		independent of the final output device.
	\item {\tt gf}. Generic font files. These files are the pixel
		files as generated by \MF.
	\item {\tt pfd}. \PS{} font description files. These text files
		contain a description of what version of the \PS\ fonts
		is to be produced, like for instance what encoding vector
		is to be used. These files together with the
		{\tt afm} file for the
		corresponding font allow the computation of the {\tt pdr}
		and the {\tt tfm} file of the font.
	\item {\tt pdr}. \PS{} Driver files: these files contain
		the information needed by a driver to generate the \PS\ code
		for the \PS\ fonts.
	\item {\tt pk}. Packed files, a more compact and also slightly
		less general form of {\tt gf} files.
	\item {\tt pxl}. Pixel files, an old format of pixel files.
	\item {\tt tex}. \TeX{} source files.
	\item {\tt tfm}. \TeX{} Font Metric files. These files contain
		the font metric information as needed by \TeX.
\end{enumerate}

\chapter{{\tt dvitype} Notes}
\label{c-dvitype-notes}
	Here a brief summary of the most important sections in {\tt
dvitype}:
\begin{itemize}
	\item {\tt [14]}. The $h,u,v,x,z$ etc. business.
	\item {\tt [17]}. $num$, $den$ and $mag$ definitions
	\item {\tt [18]}. {\tt FNT\_DEF} stuff
	\item {\tt [30]}. Font width stuff
	\item {\tt [37]}. Most important part of the font width computation.
	\item {\tt [39]}. {\tt tfm} width versus pixel width.
	\item {\tt [40]}. Compute the pixel width. {\tt dvitype} computes
		the pixel width, because it does not read any pixel files
	\item {\tt [61]}. Read {\tt FNT\_DEF} command
	\item {\tt [63]}. Load font\_space. It's $s\over6$.
	\item {\tt [81]}. The multiway switch, where branching
		takes place interpreting the various {\tt dvi} commands.
	\item {\tt [83]}. {\tt PUSH} or {\tt POP} besides other instructions.
	\item {\tt [84]}. defines {\it out\_space}, a routine to do
		horizontal movements which incorporates
		a threshold based on the current font to decide whether
		a relative or absolute movement should be executed. Absolute
		movements always incorporate accumulated rounding errors
		which at that point are reduced to zero.
	\item {\tt [85]}. similar to {\tt [84]}, but defines
		{\it out\_vmove}, a routine to do
		vertical movements. Again a threshold based on
		the current font is used to decide whether an absolute
		or a relative movement should be performed.
	\item {\tt [88]}. {\tt SETCHAR} stuff.
	\item {\tt [89]}. Finish a command that either sets or puts a
		character, then goes to {\it move\_right}.
	\item {\tt [90]}. Finish a command that either sets or puts a
		rule, then goes to {\it move\_right}.
	\item {\tt [91]}. Takes care of the {\tt maxdrift} business
		in the case of horizontal movements.
	\item {\tt [92]}. Takes care of the {\tt maxdrift} business
		in the case of vertical movements.
\end{itemize}