Short: Use Postscript font with PasTeX1.4 and more Author: Piet Tutelaers (rcpt@urc.tue.nl) (Original author) Type: text/tex Architecture: m68k-amigaos Reinhard Katzmann (suamor@student.uni-tuebingen.de) (Amiga Port) UPLOADER: Reinhard Katzmann (suamor@student.uni-tuebingen.de) When do you need ps2pk? ---------------------- Ps2pk is a tool that converts a PostScript type1 font into a corres- ponding TeX PK font. The tool is especially interesting if you want to use fully hinted type1 fonts in your DVI previewer (instead of the unhinted type1 fonts currently used in GhostScript) or on a printer that has no PostScript interpreter. In order to use the ps2pk generated fonts your driver and previewer need to support virtual fonts. The reason is that PostScript fonts and TeX fonts do have a different font encoding and handle ligatures in a different way. With virtual fonts the PostScript world (encoding + ligatures) can be mapped to the old style TeX world on which the current plain macro packages still are based (despite the fact that TeX3.0 can handle 8bits). It is also possible to use the ps2pk generated PK fonts directly (without virtual fonts) but in that case you need modified plain TeX macros in order to acces the new (changed) font features. To make TeX really 8bits (the reason TeX3.0 was released) TUG has proposed a new font standard supporting the full 8bit range (in stead of the 7bit). The 128 extra characters in this new TUG standard are filled up with characters for 17 different European languages (see: TUGboat #10 vol. 4 1990). With ps2pk it is possible to generate PK fonts from PostScript fonts according to this new TUG font standard. Notes ----- The main documentation is in the /ps2pk15 directory (/ps2pk15/ps2pk.guide). There are informations on both versions (14 and 15) in it. I've not included the source to keep the archive size down. It is avalaible on CTAN in the fonts/utilities/ps2pk/... directory. I've included the SAS-Makefile though. Known problems (as mentioned in the guide, too) are that sometimes I have problems with pathes (instead of seeking tex:ps/ f.e he seeks tex:ps/tex:ps) but if you don't use assigns (or devices (?)) there seem to be no problems. Another problem is that wrong checksums are shown in the showdvi or dviprint logs. This is a general ps2pk problem and has nothing to do with my port. type1 directory from ps2pk15 directory is identical to ps2pk14 so I did not include it in here.