1This ps2pk program (all versions) is available under the same 2permissive license as the Type 1 interpreter code that it is based on 3(and incorporates). For the exact wording, see, for example, the type1.c 4source file. 5--Piet Tutelaers and Pierre MacKay, May 2011. 6 7ps2pk is currently maintained as part of TeX Live (http://tug.org/texlive), 8and distributed through TL and CTAN. 9 10 Ps2pk-1.4 available 11 ------------------- 12 (January 1994) 13 14Version 1.4 of ps2pk is now available on: 15 ftp.urc.tue.nl (address: 131.155.2.79) 16 directory: /pub/tex 17 files: ps2pk14.README ( 9k) This file 18 ps2pk14.tar.gz (237k) Sources 19 20 For MSDOS people having difficulties in handling UNIX `.tar.gz' 21 format I have made some UNIX tools (only executables) available 22 in directories: 23 /pub/unixtools/dos 24 25 See the system specific TARGZ file for some help. 26 27 Ftp.urc.tue.nl can not handle E-mail requests. But sites are free 28 to put the ps2pk14 stuff on any server that can. 29 30 I have made read-to-go 1.4 executables for MSDOS available in: 31 pub/tex/ps2pk14x/msdos/djgpp (created with DJGPP/gcc) 32 msdos/emx (created with EMX/gcc) 33 34When do you need ps2pk? 35---------------------- 36Ps2pk is a tool that converts a PostScript type1 font into a corres- 37ponding TeX PK font. The tool is especially interesting if you want 38to use fully hinted type1 fonts in your DVI previewer (instead of the 39unhinted type1 fonts currently used in GhostScript) or on a printer 40that has no PostScript interpreter. 41 42In order to use the ps2pk generated fonts your driver and previewer need 43to support virtual fonts. The reason is that PostScript fonts and TeX 44fonts do have a different font encoding and handle ligatures in a 45different way. With virtual fonts the PostScript world (encoding + 46ligatures) can be mapped to the old style TeX world on which the current 47plain macro packages still are based (despite the fact that TeX3.0 can 48handle 8bits). 49 50It is also possible to use the ps2pk generated PK fonts directly 51(without virtual fonts) but in that case you need modified plain TeX 52macros in order to acces the new (changed) font features. To make TeX 53really 8bits (the reason TeX3.0 was released) TUG has proposed a new 54font standard supporting the full 8bit range (in stead of the 7bit). 55The 128 extra characters in this new TUG standard are filled up with 56characters for 17 different European languages (see: TUGboat #10 vol. 574 1990). With ps2pk it is possible to generate PK fonts from 58PostScript fonts according to this new TUG font standard. 59 60Ps2pk and virtual fonts. 61------------------------ 62In order to use ps2pk in combination with virtal fonts you need afm2tfm 63(the version belonging to dvips5.487 or newer), dvips and a previewer 64supporting virtual fonts (ex.: xdvi on UNIX). 65 66PS: the latest version of dvips can be retrieved from 67 labrea.stanford.edu:pub and xdvi from export.lcs.mit.edu:contrib 68 69Ps2pk without virtual fonts. 70---------------------------- 71This road in not a paved one even for experienced TeX users! So be 72prepared that you need to build some bridges and other improvements to 73reach your goal. Or simply wait until the TeX community has switched to 74the new TUG font standard. 75 76Dvips (5.487 and higher) supports different TeX and PostScript 77encodings. If you choose for the new TUG fontstandard defined in the 78Cork meeting, as the TeX and PostScript encoding, you have to: 79 - generate a set of TFM/VF fonts for the `EC' (Extended Computer 80 Modern Font encoding) using afm2tfm and vptovf, 81 - install the new encoding vector EC.enc so it will also be used for 82 the resident/downloaded PostScript fonts 83 - install a modified version of NFSS (New Font Selection Scheme) using 84 this encoding scheme. 85 86Type1 PostScript text fonts. 87---------------------------- 88Fully hinted type1 fonts are generally not PD. You have to buy them 89unless you are satisfied with the PD available GhostScript versions 90(which are currently not hinted). You don't need to be an expert to 91see the difference between hinted and unhinted fonts. If you are 92using MSDOS or MacIntosh computers you probably use Adobe Type Manager 93(ATM) a program that can render type1 fonts dynamically. With this 94program or with other programs using ATM (for example Lotus) you 95receive fully hinted type1 fonts. On MSDOS they have funny names like 96tmr______.pfb. To save space on MSDOS type1 fonts are binary encoded 97(.pfb). On UNIX you can use this .pfb format too or the .pfa format 98(which occupies about double the space of a .pfb format). 99 100If your UNIX workstation supports DPS (Display PostScript) than 101you already may have a number of fully hinted type1 fonts. Look in 102places like /usr/lib/dps. 103 104 If you are satisfied with PK fonts derived from unhinted type1 105 fonts just for previewing then you can ftp (thanks to Karl Berry): 106 ftp.cs.umb.edu (file: pub/tex/psfonts.tar). 107 108 This set contains PK files for the standard 35 PostScript fonts in 109 various sizes, generated by `gsrenderfont' in the GNU font utilities 110 (on prep.ai.mit.edu et al.). 111 112Adobe has donated their Utopia font family to the X-consortium and IBM 113their Courier font. Both families are available on ftp.urc.tue.nl. The 114Courier font from IBM does have a rich set of accented characters not 115found in other Adobe fonts. Both fonts are fully hinted. 116 117Lee Hetherington has written a set of type1 conversion utilities. These 118allow to convert from binary (PFB) to ASCII (PFA) and back. Or to 119convert a type1 font into readable PostScript (disassemble) with the 120possibility to edit it and to convert it back (assemble) to some type1 121encoded form. They are now maintained by Eddie Kohler and available at 122http://www.lcdf.org/type (and as part of TeX Live). 123 124Type1 PostScript math fonts. 125---------------------------- 126The PostScript type1 symbol fonts do not have the same rich set of math 127symbols as the TeX fonts. There are two exceptions: the Lucida fonts 128and the MathTime package. I have no experience with the Lucida fonts. 129The MathTime package from Michael Spivak has the disadvantage that it is 130too much MacIntosh/AMSTeX oriented. There are people who are working on 131LaTeX support based upon NFSS. Another disadvantage of MathTime is that 132it is built on top of TimesRoman-Italic (not delivered with the package) 133and lacks bold-italic symbols. 134 135Acknowledgements. 136----------------- 137Ps2pk uses the type1 rendering software IBM has donated to the 138X-consortium. This rendering package is used by ps2pk as pure as 139possible. But in order to support user specified encoding schemes, to 140generate extended and/or slanted font variations, to uncouple it from the 141X protocol and to fix some bugs I needed to change some of the sources. 142 143I also want to thank the `ps2pk discussion forum' who helped me to make 144ps2pk as it is now. Especially Tom Rokicki for enhancing his dvips/afm2tfm. 145 146I wish you a lot of fun with type1 fonts, 147 148--Piet 149 150internet: rcpt@urc.tue.nl | Piet Tutelaers 151bitnet: rcpt@heitue5.BITNET | Computer Center Room RC 1.90 152phone: +31 (0)40 474541 | Eindhoven University of Technology 153fax: +31 (0)40 434438 | P.O. Box 513, 5600 MB Eindhoven, NL 154 155 156For those who have used earlier versions of ps2pk next differences may be 157of interest (only major differences are mentioned): 158 159Ps2pk 1.4 release (94-01) 160------------------------- 1611) Memory allocation made dynamically 162 1.1 in computing runlengths (needed to build PK fonts) 163 1.2 in scanning type1 fonts (to overcome `fixed' virtual memory) 1642) Problem with handling Lucida font (negative widths) solved 1653) Improved error handling in scanning AFM files 1664) Provided hooks to handle non 32-bit platforms 1675) Some cleanups 1686) Improved Makefiles. 169 170Ps2pk 1.3 release (92-09) 171------------------------- 1721) Official X11R5 patches included in type1 library. 1732) The -a<AFMfile> option added to ps2pk. 1743) Problem with rendering of Obique fonts solved. 175 176Ps2pk 1.2 release (92-06) 177------------------------- 1781) Ps2pk now computes the same checksum as afm2tfm (dvips5.487 or 179 higher). This means that you have to update your VF and TFM files 180 with the new dvips5487lib files. 1812) Bug fixes: 182 - the MSDOS version now correctly reads PFB font files 183 - a segmentation fault error removed (capri.pfa font) 184 - an out of memory problem fixed (davysrib.pfa font) 1853) Added Makefile for MSDOS/DJGPP (Delorie's GCC for 386 systems) 186 187Ps2pk 1.1 release (92-04) 188------------------------- 1891) Ps2pk uses now the same encoding scheme as introduced by afm2tfm 7.0 190 (dvips5485). But default (for all English/American writing TeX-friends) 191 the program uses the same encoding as is in the AFM-file belonging to 192 the type1 PostScript font (normally AdobeStandard). So the program does 193 not longer need re-encode to create a .cmi file containing the encoding 194 vector and the WX values. These are read directly from the AFM file. 195 196 Typical usage for standard encoding: 197 ps2pk -X329 Utopia-Regular rputr.329pk 198 199 or with EC.enc encoding: 200 ps2pk -eEC.enc -X329 Utopia-Regular rputr.329pk 201 2022) I have added a -E<expansion> and -S<slant> option to ps2pk thanks to 203 the patches I got from Lee Hetherington. 204 2053) I have added a MakeTeXPK script so that dvips and xdvi can use it. 206 2074) I have added manual pages and some documentation (README + INSTALLATION). 208 2095) Some inconveniences for MSDOS users are removed. 210 211Ps2pk 1.0 release (92-03) 212------------------------- 213