bdftopcf(X1M)

Synopsis

Description

PCF fonts 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 machine, but the files are still portable (but read more slowly) on other machines.

Options

-i

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 computes the actual ink metrics and places them in the .pcf file; the -t option inhibits this behavior.

-l

sets the font bit order to least significant bit first. The leftmost bit on the screen will be in the lowest valued bit in each unit.

-L

sets the font byte order to least significant byte first. All multi-byte data in the file (metrics, bitmaps, and so forth) will be written least significant byte first.

-m

sets the font bit order to most significant bit first. Bits for each glyph will be placed in this order; that is, the leftmost bit on the screen will be in the highest valued bit in each unit.

-M

sets the font byte order most significant byte first. All multi-byte data in the file (metrics, bitmaps, and so forth) will be written most significant byte first.

-p#

sets the font glyph padding. Each glyph in the font will have each scanline padded into a multiple of # bytes, where # is 1, 2, 4, or 8.

-t

converts 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.

-u#

sets the font scanline unit. When the font bit order is different from the font byte order, the scanline unit # describes what unit of data (in bytes) are to be swapped; the unit # can be 1, 2, or 4 bytes.

-o bdf file

specifies the BDF font filename that should be compiled to a PCF font. If a filename is not specified, standard input is read.

References