⟦a0e1d28f1⟧

TextFile

% ==============
\chapter{Basics}
% ==============
	This report describes the \TeXPS{} Software package dealing with \TeX{}
and \PS.  Familiarity with \TeX{} and \PS{} is assumed. For more 
information on \TeX{} see [Knuth 86a]. For more information about \PS{} see
[\PS{} 85a], [\PS{} 85b] and [\PS{} 88].

	Part of the following text (starting with the next section and ending
before \SectionRef{s-copyright}, \page) is stored in a separate file.
This separate file can be processed independently to derive a concise
description of the \TeXPS{} software.

\input es.tex

\section{The Copyright for this Software Package}
% ===============================================
\label{s-copyright}

\subsection{Introduction}
% =======================
	I hope that this software package are found to be useful, convenient to
use, reliable and all the other good things.  On the other hand, there
are some rules to observe.
So here is the text of the copyright, which applies to \TeXPS.

	Before I discuss the copyright let me give you some of the history of
the development of this software. \TeXPS{} was developed by me
under contract with the Menil Foundation in Houston, Texas. After
its initial development I personally felt responsible improving it. The
Menil Foundation finally decided to allow me to put the driver into the
public domain.

	The expression ``public domain'' is not quite right. There are some
restrictions. To make long story short: we, the Menil Foundation and me,
decided to follow the rules of the Free Software Foundation, Inc., in Cambridge, MA,
which produces the GNU software. The copyright rules can be summarized as follows:
\begin{enumerate}
	\item You are encouraged to share and pass on this software.
	\item If you do so, you {\it must\/} pass it along completely. This
		in particular means that all sources must be included. You {\it must not\/}
		modify the copyright.
	\item The cost for distributing the driver must be minimal. You are
		allowed to charge a small amount fo cover media, packaging, shipping,
		documentation, but not more.
	\item All people receiving this software from you have the same rights
		and the same obligations. This, in particular, applies
		when you port the software to a new system.  You should
		report your results back to me so I can pass along the
		information when this software was ported.
	\item There is no implied or explicit warranty. Nobody can be held
		responsible for any damages. I will try to fix all bugs reported
		to me.
\end{enumerate}

\subsection{Version Numbers and Release Dates}
% ============================================
In general programs have version numbers and dates. More importantly though
there is a version number for the whole release. The version number can
be found in the file {\tt IMakefile}, subdirectory {\tt release}. This version
number, referred to as the ``\TeXPS{} release version number'' is also printed
on the cover page of this report.

\subsection{Copyright Exceptions}
% ===============================
	While almost all parts of the software carry the copyright just
outlined, there are exceptions. There are three different copyright categories
applicable to \TeXPS.
\begin{enumerate}
	\item There is the standard copyright outlined in the previous
		section, which applies to 95\% of the software.
	\item There is a special copyright for the psfig macros (see
		\ChapterRef{c-psfig}, \page). The only difference between the
		standard copyright and this copyright is that a different person (Trevor
		Darrell) holds the copyright.  Other than that there are no differences.
\end{enumerate}

\subsection{The Complete Copyright Text}
% ======================================
	Here is the complete copyright text (Category~1 of the above listing).
\ListVerb{CopyrightLong.tex}

\subsection{The Short Form of the Copyright}
% ==========================================
	A short form of this copyright is prepended to most of the C~code
source code files. This short form of the copyright reads as follows:
\ListVerb{CopyrightSources.tex}

\subsection{A Note Regarding Some of the \TeX{} Macros}
% ==================================================
Some of the \TeX{} macros included with this software are from my book ``\TeX{}
in Practice'' (Springer-Verlag), which I try to desparately finish as I
am writing these sentences. Please do {\it under no circumstances use these
macros for any other purpose\/} besides printing this documentation. These
macros are not done yet. I will remove this statement as soon as the macros
are finished and out in the public doman.

The macros can be easily identified, because all files of this class have
the file extension {\tt tip}.

\section{Comments, Maintenance, Fixing Bugs, Reporting Bugs}
% ==========================================================
	I would like to indicate my willingness to fix bugs,
and also to extend the driver and the associated programs within
reasons. Let me know if something should be added or could be
improved. You find my complete address on the front cover of this report.
I also can be reached at {\tt svb@cssun.tamu.edu}.

	May be some of you working in some commercial environment can follow
into the footsteps of the Menil Foundation and pay me for making extensions,
making these extensions later available free of charge.

	Because of my willingness to fix bugs {\it I urge you to report
these bugs to me instead of fixing them yourselves}.
The advantages of reporting bugs to me are the following:
\begin{enumerate}
	\item The spread of millionns of different versions of this software is avoided. There
		will be, at all times, always one, and only one, up-to-date and correct
		version of the software.
	\item When you report a bug a correction of the bug will profit other
		people.  These ``other people'' include you, when a bug you have
		not found, is reported to me and then passed on to you.
\end{enumerate}

	Because of the low cost of the software I will only send out complete
updates of this software package when you order a tape. There will be no
``update'' or ``bug fix'' releases.

	I suggest that you send me your email address regardless of how you
acquired this software.  This way I can and will contact you when the
next major release of this software package is ready.

\section{Trademarks}
% ==================
	\TeX{} and \MF{} are trademarks of the American Mathematical
Society; \PS{} and Transcript are trademarks of
Adobe Systems Inc, Palo Alto; UNIX is a trademark of Bell
Laboratories. Apple and LaserWriter are trademarks of Apple, Inc; SUN is
a trademark of SUN Microsystems, Inc.
I hope I did not forget any trademark. Let me know if I did.

\section{About This Report}
% =========================
	Let me make a few remarks about this report now.

\subsection{Larger Version of \protect\LaTeX{} is Needed}
% =======================================================
	To print this report you have
to build a version of \LaTeX{} with an increased pool size.  In other
words, you have to create a new {\it initex\/} and {\it
virtex}, and subsequently \LaTeX{} with an increased poolsize.

\subsection{One More Remark}
% ==========================
	Originally this report came in two versions, a long and a short one. I
eliminated this. You are expected to install the whole software. After
you have done this you always can remove those parts you don't use.

\section{Definitions}
% ===================
	Here is a list of definitions of terms which will be used in the
description of this software.
\begin{enumerate}
	\item {\it \PS{} font}. A font with the character
		definitions stored inside a \PS{} printer in an outline
		format. One of the advantages of these fonts is that
		they can be printed at any size. One is not restricted to
		printing characters only at sizes for which the corresponding
		pixel files are available.
	\item {\it Pixel based fonts}. Fonts in \TeX{} which require pixel files
		to be used to print the characters of the font. \TeX{} normally relies
		on this type of fonts.  Pixel files are normally generated by
		\MF.
	\item {\it {\tt TFM} width}. The width of a character according to
		the {\tt TFM} file of the font the character belongs to.
	\item {\it Pixel width}. The width of a character in pixels,
		when the character is printed. It is normally computed from the
		{\tt TFM} width rounded to the nearest pixel.
	\item {\it Octal numbers\/} in this report are given in the \TeX{} notation,
		i.e., the number is preceded by a~'. Inside {\tt PFD}
		files the \PS{} notation for octal number (the number is preceded
		by~\verb+8#+) is used.
	\item {\it Characters with recommended character codes}.
		Characters which have a specific character code proposed
		in the {\tt AFM} file. Whether this character code is actually
		used or not is a different question. This ``proposed encoding'' in {\tt AFM} files
		follows the ASCII encoding.
	\item {\it Characters without recommended character
		codes}. Characters with ``proposed character code $-1$'' 
		in the {\tt AFM} file. Such character definitions start with
		{\tt C~-1} in the {\tt AFM} file. It means that the user should
		assign the character code, if he plans to use this character.
	\item {\it \PS{} procedure character}. These are characters, for which a particular
		\PS{} procedure, defined by the user, is invoked.
	\item {\it Encoding vectors}. A vector, which maps character codes
		to \PS{} character names. Note that in \PS{} fonts characters
		are really identified by names and not by character codes. The
		encoding vectors maps character codes to character names.
	\item {\it Default character code vector}. Default
		encoding information is used by {\tt pfd2tfm} to establish
		encoding vectors if no specific mappings are established by the
		user.
\end{enumerate}

\section{Acknowledgements, History}
% =================================
	There are tons of versions of {\tt DVI} to \PS{} drivers floating
around in the world. This driver was not written from scratch, but it was
modified so heavily, that I do claim it to be my own product.

	There are some people though who helped and who should be mentioned
here: Mark Senn of the Statistics Department of Purdue University helped
was willing to test the driver.
So did Jean-Francois Lamy from the University of Toronto, Canada, who was a constant
supporter of this project. Thomas Rokicki (Stanford University) had
some nice ideas in his public domain driver which I ``borrowed''.
A.~C.~Conrad of the Menil Foundation always had another
feature he wanted me to add. Even that is appreciated!
Psfig was contributed by Trevor Darrell. He allowed me to make the psfig
documentation part of this document.

\section{A Little Advertising}
% ============================
\label{s-advertising}
This software is made available to the \TeX{} community free of charge.
Let me reprint the flyer I normally give to people who ask me what I am
doing for a living.

{
	\let\bye = \par
	\let\nopagenumbers = \relax
	\leftskip = 0.5in
	\rightskip = 0.5in
	\def\hang{% 
		\hangindent = \parindent
		\hangafter = 1
	}
	\def\item{
		\par
		\hang
		\textindent
	}
	\def\itemitem{
		\par
		\indent
		\hangindent = 2\parindent
		\textindent
	}
	\def\textindent #1{%
		\indent
		\llap{#1\enspace}%
		\ignorespaces
	}
	\input profile.tex
}

\section{For People Who Hate To Read Manuals}
% ===========================================
	You have all my sympathies if you don't like to read manuals. I am
one of them. Still manuals contain a lot of useful information, this is
one of them.

	Let's be brief and to the point:
the software consists of a {\tt DVI} to \PS{} driver on one side and a
set of programs to use \PS{} fonts in \TeX{} on the other side.
You should install everything, and then remove later what you don't need.

	Then go to \SectionRef{s-makefiles}, \page, which
contains all the important information about how the driver software is
installed, etc. More important than anything else is to define all
installation dependent parameters in the file {\tt setup/local-defs} correctly.
You should pay a lot of attention to the definitions in this file. From
thereon it should be all downhill.

	That should do it. You should try to reprint this document because
this document serves a testbed.

	The software (as it comes from the tape) is less than 2~MB long. You
need about 8~MB while you compile it and generate the documentation.
DataMuseum.dk

DKUUG/EUUG Conference tapes

⟦a0e1d28f1⟧ TextFile

Derivation

TextFile
