These are the Installation instructions for dvi2ps version 3.1.

The main task is to decide which of the compile-time options you want
to support. Then edit the DFLAGS variable in the Makefile to include these
options. Here is a brief description of the available flags:

 Your copy of dvi2ps can be customized by implementing various global
 definitions via the variable DFLAGS defined below. These options are:

 (i) By default, dvi2ps uses PK format files.  If you want to use PXL or GF
 format in addition, then include -DUSEPXL and/or -DUSEGF. If you do not want
 to use PK fonts, then include -DNO_PK. The use of PXL files is strongly
 discouraged; the use of PK files is strongly preferred. See the discussion
 of FONTAREA below.

 (ii) To use the builtin PostScript fonts, include -DBUILTIN. See the
 discussion of TFMAREA below, and the discussion of the HDRFILE.
 
 (iii) To enable users to specify a global magnification (in the texfile or)
 at runtime via the -m option, include -DUSEGLOBALMAG. This is recommended.

 (iv) To enable the users to create output files via the -c option, include
 -DCREOPT in the DFLAGS variable.

 (v) To allow this program to run as an lpd spooler (and take input from
 stdin), include -DSPOOLING in the DFLAGS variable. These routines use
 the ``standard'' library function  tmpfile()  which is not known by some
 operating systems.

 (vi) To process command line arguments with  getopt(), include
 -DUSEGETOPT in the DFLAGS variable.

 (vii) To use the routines which monitor virtual memory, include -DBUDGET
 in the DFLAGS variable. This is strongly recommended.

 (viii) If you want to enable the printing of extensive debugging information
 via the -D option, then add -DDEBUG to the DFLAGS.

 (ix) To enable users to get various statistics via the -S option, include
  -DSTATS in the DFLAGS variable.

 (x) To enable users to alter the default pixel density with the -d option,
 include -DDENSITY in the DFLAGS variable.

 (xi) For various apollo-specific modifications, which forces -DCREOPT as well,
 include -Dapollo in the DFLAGS variable.

You should modify the Makefile so that the desired list of options is
contained in the definition of the variable DFLAGS. There are also a number
of site-dependent paths which must be set. Defaults for these are defined 
in ``site.h'', just in case you forget to define any of them in the Makefile.
It shouldn't be necessary to change ``site.h'', in spite of the name, provided
you make the necessary changes to the Makefile. These paths are

 (i) FONTAREA. This is the directory which contains the bitmaps for the fonts,
 in one of the forms PK, GF, or PXL. The program is set up so that it will also
 look in subdirectories with any of the following names: pk, pk300, gf, gf300,
 or pxl. Moreover, the various magnifications (like cmr10.300pk) of cmr10, for
 example, are allowed to be located in a subdirectory also called cmr10,
 provided that a file named SUBDIR is located in the parent directory. The
 value of FONTAREA can be a colon-separated list of directories; this value
 can be overridden at run-time by the environment variable DVIFONTS or by the
 command line option -a.

 (ii) TFMAREA. This is the directory which contains the tfm files for any
 builtin PostScript fonts. This must contain the same tfm files used by TeX
 when processing the document originally. The value of TFMAREA may be overridden
 at run-time by the environment variable TEXFONTS (this is also used by the
 program TeX itself) or by the command line option -b. If you intend to use
 the tfm files provided with this distribution, you must move them to the
 appropriate directory. You must also properly install the FONTMAP; see below.

 (iii) HDRFILE. This is the full path name of the file which contains the 
 PostScript prologue code necessary for dvi2ps to work; it is included at the
 beginning of every document unless the -h command line option is used.
 There are four possible pieces to this file. The basic piece assumes that you
 are only using fonts in PK, GF, or PXL format and are only using raw
 PostScript specials which you have included by hand. A second piece provides
 support for builtin fonts. A third piece is the ``psfig.pro'' PostScript code
 written by Trevor Darrell to automate the including of PostScript graphics
 into TeX documents. A fourth piece is the ``mac.pro'' code written by Ned
 Batchelder to allow the inclusion of Macintosh generated figures. You 
 should look in the directory ``dvi2ps/postscript'' of this distribution
 and follow the instructions there for producing the appropriate HDRFILE.
 The value of HDRFILE can be overridden at run-time by the environment
 variable PSHEADER, or by combined use of the -h and -i command line
 options. The recommended procedure is to make the small basic prologue
 the system-wide default, and allow users to alter this individually by
 environment variables or the STARTUPFILE (see below).

 (iv) STARTUPFILE. This is the name of the file which contains the user's
 customising information. Any command line option can be entered in this
 file, which is read each time the program starts up. The program looks in
 the current directory and the user's home directory for this file, which
 is called, by default, ``.dvi2ps''.

 (v) FONTMAP. In order to use the builtin fonts, dvi2ps needs to be able to
 translate between the TeX names and the PostScript names of fonts. FONTMAP
 contains the fullpathname of the file which stores this information. Its
 value is NOT overridden by an environment variable nor by a command line
 option (the latter is probably a bug). The reason is that this file can
 also contain information about other downloaded fonts, or special font
 prefixes like Jing-bai Wang's ``chfont'' or the Japan TeX User's Group
 ``jis'' which are probably (?) better known to the system administrator
 than to the user. The included FONTMAP contains a list of all the tfm
 files of resident fonts included with the distribution.

 (vi) A couple of installation paths specifying the final destinations
 of binaries and manual pages should also be defined.

After these values have been defined, you should be able to type ``make''
to build the program, ``make install'' to install it, and ``make veryclean''
to get rid of the stuff that can be regenerated easily. Good luck!

Kevin Coombes
<kevin@math.lsa.umich.edu>
<Kevin_Coombes@ub.cc.umich.edu>
