
		   PS2PK installation summary
		   --------------------------
		       (November 1995)

The ps2pk directory contains the sources to build the following programs:
  - ps2pk	a program to build PK fonts from PostScript type1 fonts
  - pk2bm	a program that allows to look at a PK character.
 		
To install and use these programs follow next steps:
 1) - Go to the ./ps2pk directory.  

      Select a Makefile.xxx
	 System    xxx
	 ------------------------------------------------------------
	 UNIX      unx  A universal UNIX makefile using cc.
	                This makefile is tailored to BSD like UNIX-es. On
	                SYS5 UNIX systems some small changes may be
	                necessary.

	 MSDOS     emx  Eberhard Mattes port of GCC with an extender that
			can be used on MSDOS and OS2. Only 386 and higher.

      Copy the selected Makefile.xxx to Makefile.

      Edit the Makefile to adapt the defaults for the T1INPUTS and
      PSRESOURCEPATH paths and the BINDIR and MANDIR directories.
      
    - Do a `make'. This will create the tools above.
      The master Makefile calls the appropriate Makefile.xxx in the
      ./type1 and ./common directories to install the type1 and
      common libraries. If your compiler has problems in compiling
      them you possibly have to adapt those Makefile's to your needs.
      Things to check:
	 RANLIB		not used on SYSV systems (make RANLIB = echo)
	 INSTALL	not available on SYSV (get a PD BSD install).

    - Do a `make install'.
      This will install the above programs.

    - Do a `make install.man'.
      This will install manual pages for the above programs.

 2) Testing ps2pk from ./ps2pk directory. 
    The directory ../PSources contains the Utopia-Regular font donated by
    Adobe. To make from this type1 font a PKfile next steps are needed:
         setenv T1INPUTS ../PSources 		  (C-shell)
         ./ps2pk -v Utopia-Regular.pfa

    This will create the Utopia-Regular10.300pk font with the default
    AdobeStandard characters derived from ../PSources/Utopia-Regular.afm.
    (The -v flag will show what the program is doing and which character
    codes are generated.)

    To see how for example the `Q' is rendered by ps2pk (using the IBM
    type1 rendering software) you can use:
         pk2bm -bcQ Utopia-Regular10.300pk

    MSDOS has problems with such long names as Utopia-Regular10.300pk. That
    is the reason that dvips uses abreviations for the PostScript names. The
    short name for TeX's virtual font needed to use Utopia-Regular is `putr'.
    The short name for its raw counterpart is `rputr'. To generate rputr.pk 
    the equivalent of Utopia-Regular10.300pk in directory 300dpi you have to 
    use (on MSDOS):
         ps2pk -v Utopia-Regular 300dpi\rputr.pk
    
    Ps2pk has some extra options. All options are explained in the manual
    page (ps2pk.1). Here are the most important:
       -X<xres>	     the desired X-resolution (ex: 300, 329, 360, 432, etc)
       -E<expansion> the factor to expand a font
       -S<slant>     to get a slanted font.
    
 3) Automatic font generation

    This version of ps2pk comes with mtpk(1) an automatic PK font
    generator written in C (derived from an earlier perl script)
    and pkfonts(1) a front-end that can generate missing fonts from
    DVI files. Both programs use the same configuration file
    (mtpk.cfg). The following steps can be used to test and install
    these programs. See the manual pages of mtpk(1) and mtpk(5) for
    more details.

      3.1) go to the mtpk directory, adapt the configuration file
	   mtpk.cfg to your TeX defaults and try `make test'. The test
	   expects the new version of ps2pk in your PATH.

           This should install a test version of mtpk and pkfonts.
	   These versions are then used to create a TeX font for
	   Utopia-Regular which is available in PSources.

      3.2) Test if mtpk works with METAFONT (check the value of
	   MFINPUTS in mtpk.cfg) by trying to make cmr10.331pk

		./mtpk -v cmr10 331 300

      3.3) Test gsftopk (check gsfontmap in mtpk.cfg) and try

		./mtpk ptmr0 331 300
	
      3.4) If you install ps2pk you probably have good quality
	   type1 fonts. To use them with mtpk you need to install
	   a PSres.upr resource database on the place defined in
	   the Makefile with mkpsres (directory PSres). All type1
	   fonts, AFM files and encoding vectors available on your
	   system should be added to this resource database. If
	   your workstation comes with Display PostScript (DPS)
	   a good place to install your PostScript resources is in
	   the directory used by DPS (see manual of mkpsres(1)).

	   Try to make ptmr0.332pk with ps2pk

		./mtpk ptmr0 332 300

      3.5) install mtpk and pkfonts

	   Change the path for MTPKCFG in the Makefile to its final
	   destination BEFORE installing.

	   Adapt the definitions in mtpk.cfg to its final values.

	   Decide what pseudo-user you want to use for installing PK
	   fonts in public directories. Create this usercode and change
	   all PK directories to this new owner (you need superuser
	   priviledges). You can also make the public directories world
	   writable if you prefer.

           Do now a `make install' (superuser?) and `make install.man'.

      3.6) Recompile your DVI drivers (dvips and xdvi) so that they will
	   use mtpk automatically. You can also use pkfonts to generate PK
	   fonts from a DVI file.

	   Add \usepackage{times} to a copy of sample2e.tex and make
	   all missing PK fonts with:

		pkfonts sample2e[.dvi]

           Or just check which fonts are used

		pkfonts -a sample2e

           or are missing

		pkfonts -m sample2e

Good luck!

--Piet
November 1995
