Name of the font to be created.
Desired resolution of the font to be created, in dots per inch. This may be a real number.
This program should normally be called by a script, such as xdvimakepk, to create fonts on demand.
gsftopk obtains the character widths from the .tfm file, which must exist in the standard search path. It also must be able to find a file psfonts.map (formatted as in dvips(1)), listing the available fonts.
Colon-separated list of directories to search for the .tfm file associated with the font. An extra colon in the list will include the system default path at that point. A double slash will enable recursive subdirectory searching at that point in the path.
Colon-separated list of directories to search for the ghostscript driver file render.ps and for any PostScript font files (.pfa or .pfb files). An extra colon in the list behaves as with
Path to search for the file psfonts.map. Only the first such file will be used.
Call to gs stopped by signal 10
(The number may vary from system to system; it corresponds to a bus error or a segmentation fault.) This is actually a design limitation in PostScript, exacerbated by a bug in ghostscript, rather than a bug in gsftopk itself. To work around this bug, gsftopk can be instructed to use the bounding box provided with the font (if one exists) instead of finding a bounding box for each character. To do this, include the string
in the psfonts.map file; e.g.,
This will not affect use of the font by dvips.