The bdftopcf(1) utility is the release 5 font compiler.
Fonts in Portable Compiled Format can be read by any architecture,
although the file is structured to allow one particular
architecture to read them directly without reformatting. This
allows fast reading on the appropriate computer, but the files are
still portable (but read more slowly) on other computers.
Sets the font glyph padding. Each glyph in the font will have
each scanline padded in to a multiple of n bytes, where
n is 1, 2, 4 or 8.
Sets the font scanline unit. When the font bit order is
different from the font byte order, the scanline unit n
describes which unit of data (in bytes) is to be swapped; the unit
i can be 1, 2 or 4 bytes.
Sets the font bit order to MSB (most significant bit) first.
Bits for each glyph will be placed in this order; that is, the left
most bit on the screen will be in the highest valued bit in each
Sets the font bit order to LSB (least significant bit) first.
The left most bit on the screen will be in the lowest valued bit in
Sets the font byte order to MSB first. All multibyte data in
the file (metrics, bitmaps and everything else) will be written
most significant byte first.
Sets the font byte order to LSB first. All multibyte data in
the file (metrics, bitmaps, and so on) will be written least
significant byte first.
When this option is specified, bdftopcf(1) will convert
fonts into "terminal" fonts when possible. A terminal font has each
glyph image padded to the same size; the X server can usually
render these types of fonts more quickly.
This option inhibits the normal computation of ink metrics.
When a font has glyph images that do not fill the bitmap image
(that is, the "on" pixels do not extend to the edges of the
metrics) bdftopcf(1) computes the actual ink metrics and
places them in the .pcf file. The -t option inhibits this
By default bdftopcf(1) writes the pcf file to standard
output; this option gives the name of a file to be used