1OTF2BDF(1) General Commands Manual OTF2BDF(1)
2
6 otf2bdf - OpenType to BDF font converter
7
10 otf2bdf [options] font.{ttf,otf}
11
14 otf2bdf will convert an OpenType font to a BDF font using the Freetype2
15 renderer (http://www.freetype.org).
16
19 otf2bdf accepts the following command line arguments:
20 -v print warning messages when the font is converted.
23 -n disable glyph hinting.
25 -p n set the desired point size (see default value by running the
27 program with the -h option).
28 -et display a list of the platforms and encodings available in the
30 font. The default values, compiled into the program, are a
31 platform of 3 (Microsoft) and encoding of 1 (ISO10646). If the
32 font does not contain the default platform and encoding, the
33 fallback will be the Apple ISO10646 encoding.
34 -r n set both the horizontal and the vertical resolution (see
36 default value by running the program with the -h option). The
37 minimum is 10dpi and the maximum is 1200dpi.
38 -rh n set the horizontal resolution (see default value by running the
40 program with the -h option). The minimum is 10dpi and the max‐
41 imum is 1200dpi.
42 -rv n set the vertical resolution (see default value by running the
44 program with the -h option). The minimum is 10dpi and the max‐
45 imum is 1200dpi.
46 -o outfile
48 sets the output filename (default output is to stdout).
49 -pid id set the platform id for selecting the character map (see
51 default value by running the program with the -h option).
52 -eid id set the encoding id for selecting the character map (see
54 default value by running the program with the -h option).
55 -c c set the character spacing. This should be one of `P' for pro‐
57 portional, `M' for monospace, or `C' for character cell. By
58 default, the spacing of a font will be automatically determined
59 to be either `M' or `P' according to values provided in the
60 font.
61 -f name set the foundry name used in the XLFD name. The default value
63 is `Freetype'.
64 -t name set the typeface name used in the XLFD name. By default,
66 otf2bdf will attempt to get a name from the font first and then
67 it will use the name supplied with this command line option,
68 and if all else fails, it will use the name `Unknown'.
69 -w name set the weight name used in the XLFD name. If this value is
71 not supplied, the default value is assumed to be `Medium'.
72 Some common values for this are `Thin', `Delicate', `Extra‐
73 Light', `Light', `Normal', `Medium', `SemiCondensed', `Con‐
74 densed', `SemiBold', `Bold', `Heavy', `ExtraBold', and `Extra‐
75 Heavy'.
76 -s name set the slant name used in the XLFD name. If this value is not
78 supplied, the default value is assumed to be `R', for Roman.
79 Some common values for this are `R' for Roman, `I' for Italic,
80 `O' for Oblique, `RI' for Reverse Italic, and `RO' for Reverse
81 Oblique.
82 -k name set the width name used in the XLFD name. The default is `Nor‐
84 mal'.
85 -d name set the additional style name used in the XLFD name. The
87 default is an empty string.
88 -u char set the character used to replace the dashes/spaces in a font
90 name. The default is the space character.
91 -l subset
93 define a list of character codes which will be used to select a
94 subset of glyphs from the font. The syntax of the subset
95 string is the same as the syntax for selecting subsets in X11
96 XLFD font names. Example:
97 % otf2bdf -l '60 70 80_90' font.ttf -o font.bdf
99 The command above will only generate the glyphs for codes 60,
101 70, and 80 through 90 inclusive. Glyphs that are not in the
102 subset are not generated.
103 -m mapfile
105 specifies a mapping file which will reencode the BDF font when
106 it is generated. Any glyphs with codes that do not have a map‐
107 ping will not be generated.
108 The remapping file should begin with two lines, one which
110 starts with REGISTRY followed by the character set registry and
111 one which starts with ENCODING followed by the encoding. An
112 example from the iso8859.2 file:
113 REGISTRY ISO8859
115 ENCODING 2
116 The remapping data should be two columns of hexadecimal num‐
118 bers, separated by spaces or tabs. The first column should
119 have the code which should be used in the BDF font. The second
120 column should be the hexadecimal code of the glyph in the
121 "cmap" table otf2bdf is using. An example mapping file is pro‐
122 vided which will map fonts from Unicode (the default "cmap" ta‐
123 ble) to ISO8859-2.
124 Unicode is not the only option. If you choose another platform
126 and encoding ID on the command line, then the remapping is
127 assumed to map from the chosen platform and encoding to some
128 other character set.
129
132 gbdfed(1), xfed(1), bdftopcf(1), bdftosnf(1), bdfresize(1)
133 Glyph Bitmap Distribution Format (BDF) Specification, Application Note
134 5005, Adobe System Inc, 1993
135 X Logical Font Description Conventions, X Consortium
136
139 The FreeType project for providing the renderer!
140 Robert Wilhelm <robert@physiol.med.tu-muenchen.de> for pointing out a
141 crucial problem with the pre-1.0 code.
142 Lho Li-Da <ollie@ms1.hinet.net> for problem reports.
143 Adrian Havill <havill@threeweb.ad.jp> for unintentionally pointing out
144 a missing feature.
145 Richard Verhoeven <rcb5@win.tue.nl> for problem reports and patches.
146 Choi Jun Ho <junker@jazz.snu.ac.kr> whose implementation provided some
147 nice new features.
148 Pavel Kankovsky <peak@kerberos.troja.mff.cuni.cz> for providing some
149 critical metrics fixes and other improvements.
150 Matti Koskinen <mjkoskin@sci.fi> for pointing out a problem.
151 Eugene Bobin <gene@ftim.ustu.ru> for mapping tables.
152 Oleg N. Yakovlev <yashka@optima.dnepropetrovsk.ua> for pointing out a
153 problem.
154 Bertrand Petit <elrond@phoe.frmug.org> for additional functionality.
155 Roman Czyborra <czyborra@cs.tu-berlin.de> for pointing out some prob‐
156 lems.
157 Mike Blazer <blazer@mail.nevalink.ru> for some Window's compilation
158 advice.
159 Solofo Ramangalahy <solofo@mpi-sb.mpg.de> for contributing some mapping
160 tables.
161 Antoine Leca <Antoine.Leca@renault.fr> for mapping table suggestions.
162 Patrick Hagglund <patrik.hagglund@bredband.net> for Freetype2 patches.
163 Christos Tountas <cvt@sprynet.com> for finding problems.
164 Nelson Beebe <beebe@math.utah.edu> for finding problems.
165 "Prophet of the Way" <afu@wta.att.ne.jp> for finding a problem.
166
168 Mark Leisher
169 Computing Research Lab
170 New Mexico State University
171 Email: mleisher@crl.nmsu.edu
172Freetype Version 2 22 May 2008 OTF2BDF(1)