1GSFTOPK(1) General Commands Manual GSFTOPK(1)
3
7 gsftopk - render a ghostscript font in TeX pk form
8
10 gsftopk [-i path] [-q] [-t] [--debug=n] [--dosnames] [--inter‐
11 preter=path] [--mapline=line] [--mapfile=file] [--quiet] [--test]
12 [--help] [--version] font dpi
13
15 font Name of the font to be created.
16 dpi Desired resolution of the font to be created, in dots per inch.
18 This may be a real number.
19
21 gsftopk is a program which calls up the ghostscript program gs(1) to
22 render a given font at a given resolution. It packs the resulting
23 characters into the pk file format and writes them to a file whose name
24 is formed from the font name and the resolution (rounded to the nearest
25 integer). The font may be in any format acceptable to Ghostscript,
26 including .pfa, .pfb, .gsf, and .ttf files.
27 This program should normally be called by a script, such as mktexpk, to
29 create fonts on demand.
30 gsftopk obtains the character widths from the .tfm file, which must
32 exist in the standard search path. It also must be able to find the
33 font in a map file (such as psfonts.map), formatted as in dvips(1)),
34 unless the --mapline option is used. The set of map files is given by
35 the --mapfile option, or in the files config.ps, $HOME/.dvipsrc, and
36 config.gsftopk (as would be used by dvips -Pgsftopk).
37 The following pk "specials" are added at the end of the output file, to
39 provide an internal check on the contents of the file: "jobname=font",
40 "mag=1", "mode=modeless", and "pixels_per_inch=dpi". This is in accor‐
41 dance with the TeX Directory Standard (TDS).
42
44 --debug=n
45 Set the Kpathsea debug flags according to the integer n.
46 --dosnames
48 Use a name of the form font.pk instead of font.dpipk.
49 -h, --help
51 Print a brief help synopsis and exit.
52 -i path, --interpreter=path
54 Use path as the Ghostscript interpreter.
55 --mapfile=file
57 Use file to look for the map information for font. This should
58 be the full name of the file (in other words, no path searching
59 algorithms are applied).
60 --mapline=line
62 Use line instead of looking for an entry in a map file. The
63 first word of line must match font.
64 -q, --quiet
66 Operate quietly; i.e., without writing any messages to the stan‐
67 dard output.
68 -t, --test
70 Test run: return zero status if the font can be found in the
71 map file(s), and nonzero status if it cannot. If this option is
72 specified, then the dpi argument is optional (since the font
73 will not be generated).
74 -v, --version
76 Print the version number and exit.
77
79 DVIPSRC Name of file to read instead of $HOME/.dvipsrc. This
80 should be the full name of the file (in other words, no
81 path searching algorithms are applied).
82 GSFTOPKFONTS See TFMFONTS.
84 GSFTOPKHEADERS See TEXPSHEADERS.
86 PSHEADERS See TEXPSHEADERS.
88 TEXCONFIG Colon-separated list of paths to search for map files.
90 An extra colon in the list will include the compiled-in
91 default paths at that point. A double slash will
92 enable recursive subdirectory searching at that point
93 in the path.
94 TFMFONTS Colon-separated list of paths to search for the .tfm
96 file associated with the font. Double slashes and
97 extra colons behave as with TEXCONFIG. This informa‐
98 tion may also be supplied by using the environment
99 variables TFMFONTS or GSFTOPKFONTS. These environment
100 variables are checked in the order GSFTOPKFONTS, TFM‐
101 FONTS, TFMFONTS; the first one (if any) having a value
102 is used.
103 TEXPSHEADERS Colon-separated list of paths to search for the Ghost‐
105 script driver file render.ps and for any PostScript
106 header or font files (.enc, .pfa, .pfb, .gsf, or .ttf
107 files). Double slashes and extra colons behave as with
108 TEXCONFIG. This information may also be supplied by
109 using the environment variables PSHEADERS or GSFTOP‐
110 KHEADERS. These environment variables are checked in
111 the order GSFTOPKHEADERS, TEXPSHEADERS, PSHEADERS; the
112 first one (if any) having a value is used.
113 TFMFONTS See TFMFONTS.
115
117 In order to determine the set of map files to be used and the path for
118 finding PostScript files, gsftopk reads, in order, the files config.ps,
119 .dvipsrc, and config.gsftopk. The files config.ps and config.gsftopk
120 are searched for using the environment variable TEXCONFIG, the Kpathsea
121 configuration file, or the compiled-in default paths. The file .dvip‐
122 src is searched for in the user's home directory.
123 These files are in the same format as for dvips (as well as being in
125 the same locations). The entries used by gsftopk are as follows.
126 H path Indicates that the Ghostscript driver file render.ps and the
128 PostScript header and font files are to be searched for using
129 path.
130 p file Indicates that the list of map files is to be erased and
132 replaced by file.
133 p +file
135 Indicates that file is to be added to the list of map files.
136 All other entries are ignored.
138 This is similar to the handling of these options when running dvips
140 -Pgsftopk. For more details, see the Kpathsea manual.
141
143 gsftopk sometimes has trouble with fonts with very complicated charac‐
144 ters (such as the Seal of the University of California). This is
145 because gsftopk uses the charpath operator to determine the bounding
146 box of each character. If the character is too complicated, then old
147 versions of Ghostscript fail, causing gsftopk to terminate with an
148 error message
149 Call to gs stopped by signal 10
151 (The number may vary from system to system; it corresponds to a bus
153 error or a segmentation fault.) The best way to fix this bug is to
154 install a current version of ghostscript. As an alternative, gsftopk
155 can be instructed to use the bounding box provided with the font (if
156 one exists) instead of finding a bounding box for each character. To
157 do this, include the string
158 /usefontbbox true def
160 in the font map file; e.g.,
162 ucseal "/usefontbbox true def"
164 This will not affect use of the font by dvips.
166
168 gs(1), gftopk(1), tex(1), xdvi(1), dvips(1)
169
171 Written by Paul Vojta. This program was inspired by Karl Berry's
172 gsrenderfont.
173
175 Modified by Yves Arrouye to use Karl Berry's Kpathsea library.
176 28 November 1998 GSFTOPK(1)