Ps2pk 1.5 binaries for UNIX platforms ------------------------------------- (Februari 1996) To install ps2pk in combination with mtpk (a configurable PK font generator) the following steps are needed: 1) Install the binaries for your platform and make them executable Some considerations - public cache PK fonts need to be stored in a directory that is shared between users in a safe way. A neat solution is to create the pseudo-user `pkcache' (/bin/false shell) and to give write permission to this user in the cache root directories. Another solution is to create a public read/write cache. But this is unsafe. As superuser: * create the pseudo-user pkcache (or something else) * make the root directories of the cache r/w for this user * change the owner of mtpk to `pkcache' and give it set-UID permission for pkcache (so that mtpk has write permission in the directories where the PK-fonts are stored) - PostScript resource database PostScript names are not restricted to MSDOS limitations. For example `Times-Roman' and `Utopia-Regular' are names of PostScript fonts. In order to locate fonts, AFM files and encoding vectors by their internal name mtpk needs to know the filename containing it. For this purpose mtpk needs a PS resource database (PSres.upr on UNIX). Unfortunately dvips currently uses its own non-standard method for locating the filenames containing the wanted PS resources. You have to add the filename of all relevant PS resources into the psfonts.map file. For example: ptmr8r Times-Roman "TeXBase1Encoding ReEncodeFont" <8r.enc putr8r Utopia-Regular "TeXBase1Encoding ReEncodeFont" <8r.enc <putr8a.pfb (I hope to create patches for dvips in the near future so that dvips will use PS resource databases too and mtpk instead of MakeTeXPK.) * make a PSres.upr database. For example mkpsres $(TEXMF)/dvips If mkpsres discovers multiple occurences of the same resource you get a warning. Because the database is in ASCI you can edit it to fix this problem. * put PSres.upr in your PSRESOURCEPATH (see mtpk.cfg) 2) Install the manual pages from man/{man1,man5} 3) Install ini/mtpk.cfg file on some place (eg $TEXMF/ini/mtpk.cfg) Change the hard-wired place of mtpk.cfg in mtpk with an editor like vi which can edit binary files. Change the string /usr/local/tex-3.1415/ini/mtpk.cfg@@...@@@ by the place you have choosen without changing its length. Edit your mtpk.cfg so that all referenced targets match (consult the manual page from mtpk(1) and mtpk(5) when you are in doubt.) Try if mtpk will generate PK-fonts derived from METAFONT descriptions. For example: mtpk cmr10 [-vd] 300 300 ( -vd for verbose and debugging) 4) If you have PostScript type1 fonts (and not poor quality GhostScript substitutes) then try if mtpk can build PK-fonts out of them. For example: mtpk rptmr 300 300 (first generation PS fonts) mtpk ptmr0 300 300 (second generation LaTeX2e-only fonts) mtpk ptmr8r 300 300 (thirth generation PS fonts) If your UNIX workstation supports DPS (Display PostScript) than you already may have a number of fully hinted type1 fonts. Look in places like: /usr/lib/DPS/outline (SGI), /usr/lib/X11/fonts/Type1Adobe (DEC/OSF alpha) /usr/openwin/lib/X11/fonts/Type1/outline (SUN Solaris) These systems provide the minimal 13 PostScript fonts containing the families Courier, Helvetica and Times in four faces plus Symbol. They are used by LaTeX's times package. The same fonts are also available as part of Adobe's acrobat readersoftware for UNIX systems. Look for the file acroread.tar (on the Adobe Acrobat CD sampler in the directory acro_v1/acrorunix or in pub/adobe/Applications/Acrobat on ftp.adobe.com). 5) I did check mtpk only on my NetBSD system and on our emTeX version. If you encounter any problems on other platforms please report them (preferable with patches). Good luck, --Piet 23 Februari 1996 rcpt@urc.tue.nl