TTF2BDF(1)

NAME
ttf2bdf - TrueType to BDF font converter

SYNOPSIS
ttf2bdf [options] [font.ttf]

DESCRIPTION
ttf2bdf will convert a TrueType font to a BDF font using the FreeType renderer.

OPTIONS
ttf2bdf accepts the following command line arguments:

-v  print warning messages when the font is converted.

-p n
    set the desired point size (see default value by running the program with the -h option).

-r n
    set both the horizontal and the vertical resolution (see default value by running the program with the -h option).

-rh n
    set the horizontal resolution (see default value by running the program with the -h option).

-rv n
    set the vertical resolution (see default value by running the program with the -h option).

-o outfile
    sets the output filename (default output is to stdout).

-pid id
    set the platform id for selecting the character map (see default value by running the program with the -h option).

-eid id
    set the encoding id for selecting the character map (see default value by running the program with the -h option).

-c c
    set the character spacing. This should be one of `P' for proportional, `M' for monospace, or `C' for character cell. By default, the spacing of a font will be automatically determined to be either `M' or `P' according to values provided in the font.

-t name
    set the typeface name used in the XLFD name. By default, ttf2bdf will attempt to get a name from the font first and then it will use the name supplied with this command line option, and if all else fails, it will use the name `Unknown'.

-w name
    set the weight name used in the XLFD name. If this value is not supplied, the default value is assumed to be `Medium'. Some common values for this are `Thin', `Delicate', `ExtraLight', `Light', `Normal', `Medium', `SemiCondensed', `Condensed', `SemiBold', `Bold', `Heavy', `ExtraBold', and `ExtraHeavy'.

-s name
    set the slant name used in the XLFD name. If this value is not supplied, the default value is assumed to be `R', for Roman. Some common values for this are `R' for Roman, `I' for Italic, `O' for Oblique, `RI' for Reverse Italic, and `RO' for Reverse Oblique.

-l subset
    define a list of character codes which will be used to select a subset of glyphs from the font. The syntax of the subset string is the same as the syntax for selecting subsets in X11 XLFD font names. Example:

    % ttf2bdf -l '60 70 80_90' font.ttf -o font.bdf

    The command above will only generate the glyphs for codes 60, 70, and 80 through 90 inclusive. Glyphs that are not in the subset are not generated.

-m mapfile
    specifies a mapping file which will reencode the BDF font when it is generated. Any glyphs with codes that do not have a mapping will not be generated.

    The remapping file should begin with two lines, one which starts with REGISTRY followed by the character set registry and one which starts with ENCODING followed by the encoding. An example from the iso8859.2 file:

    REGISTRY ISO8859
    ENCODING 2

    The remapping data should be two columns of hexadecimal numbers, separated by spaces or tabs. The first column should be the hexadecimal code of the glyph in the "cmap" table ttf2bdf is using. The second column should have the code which should be used in the BDF font. An example mapping file is provided which will map fonts from Unicode (default cmap table) to ISO8859-2.

    Unicode is not the only option. If you choose another platform and encoding ID on the command line, then the remapping is assumed to map from the chosen platform and encoding to some other character set.

SEE ALSO
xmbdfed(1), xfed(1), bdftopcf(1), bdftosnf(1)
Glyph Bitmap Distribution Format (BDF) Specification, Application Note 5005, Adobe System Inc, 1993
X Logical Font Description Conventions, X Consortium

ACKNOWLEDGMENTS
The FreeType project for providing the renderer!
Robert Wilhelm <robert@physiol.med.tu-muenchen.de> for pointing out a crucial problem with the pre-1.0 code.
Lho Li-Da <ollie@ms1.hinet.net> for problem reports.
Adrian Havill <havill@threeweb.ad.jp> for unintentionally pointing out a missing feature.
Richard Verhoeven <rcb5@win.tue.nl> for problem reports and patches.
Choi Jun Ho <junker@jazz.snu.ac.kr> whose implementation provided some nice new features.
Pavel Kankovsky <peak@kerberos.troja.mff.cuni.cz> for providing some critical metrics fixes and other improvements.
Matti Koskinen <mjkoskin@sci.fi> for pointing out a problem.

AUTHOR
Mark Leisher
Computing Research Lab
New Mexico State University
Email: mleisher@crl.nmsu.edu