1TTF2PT1_CONVERT(1)          TTF2PT1 Font Converter          TTF2PT1_CONVERT(1)
2
3
4

NAME

6       ttf2pt1_convert - convenience font conversion script
7

SYNOPSIS

9       ttf2pt1_convert [config-file]
10

DESCRIPTION

12       Ttf2pt1_Convert' is the master conversion script provided with ttf2pt1.
13
14       If the configuration file is not specified as an argument then the file
15       `"convert.cfg"' in the current directory is used. This file contains a
16       set of configuration variables. The distribution contains a sample file
17       file `"convert.cfg.sample"'. Please copy it to `"convert.cfg"', look
18       inside it and change the configuration variables. The more stable
19       configuration variables, such as the path names of the scripts and
20       encoding files are located in `"ttf2pt1_convert"' itself, they are
21       automatically updated when installing ttf2pt1.
22
23       Put all the TTF fonts you want to convert into some directory (this may
24       be just the directory that already contains all the Windows fonts on a
25       mounted FAT filesystem). If you have fonts in different source encoding
26       then put the fonts in each of the encodings into a separate directory.
27       Up to 10 source directories are supported. If you (in a rather unlikely
28       case) have more source directories then you can make two separate runs
29       of the converter, converting up to 10 directories at a time.
30
31       The variables in the configuration file are:
32
33"SRCDIRS" - the list of directories (with absolute paths) with TTF
34         fonts. Each line contains at least 3 fields: the name of the
35         directory, the language of the fonts in it (if you have fonts for
36         different languages you have to put them into the separate
37         directories) and the encoding of the fonts. Again, if you have some
38         of the TTF typefaces in one encoding, and some in another (say,
39         CP-1251 and KOI-8), you have to put them into the separate source
40         directories. Some lines may contain 4 fields. Then the fourth field
41         is the name of the external map to convert the Unicode fonts into the
42         desirable encoding. This map is used instead of the built-in map for
43         the specified language.
44
45         *8* An interesting thing is that some languages have more than one
46         widely used character encodings. For example, the widely used
47         encodings for Russian are IBM CP-866 (MS-DOS and Unix), KOI-8 (Unix
48         and VAX, also the standard Internet encoding), IBM CP-1251 (MS
49         Windows).  That's why I have provided the means to generate the
50         converted fonts in more than one encoding. See the file
51         encodings/README for details about the encoding tables. Actually, if
52         you plan to use these fonts with Netscape Navigator better use the
53         aliases cp-866 instead of ibm-866 and windows-1251 instead of
54         ibm-1251 because that's what Netscape wants.
55
56"DSTDIR" - directory for the resulting Type1 fonts. Be careful!  This
57         directory gets completely wiped out before conversion, so don't use
58         any already existing directory for this purpose.
59
60"DSTENC{language}" - the list of encodings in which the destination
61         fonts will be generated for each language. Each font of that language
62         will be generated in each of the specified encodings. If you don't
63         want any translation, just specify both "SRCENC" and "DSTENC" as
64         iso8859-1 (or if you want any other encoding specified in the
65         fonts.dir, copy the description of 8859-1 with new name and use this
66         new name for "SRCENC" and "DSTENC").
67
68"FOUNDRY" - the foundry name to be used in the fonts.dir file. I have
69         set it to `fromttf' to avoid name conflicts with any existing font
70         for sure. But this foundry name is not registered in X11 standards
71         and if you want to get the full standard compliance or have a font
72         server that enforces such a compliance, use `misc'.
73
74       The next few parameters control the general behavior of the converter.
75       They default values are set to something reasonable.
76
77"CORRECTWIDTH" - if the value is set to "YES" then use the converter
78         option "-w", otherwise don't use it. See the description of this
79         option in the README file.
80
81"REMOVET1A" - if the value is set to "YES" then after conversion
82         remove the un-encoded ".t1a" font files and the intermediate ".xpfa"
83         font metric files.
84
85"INSTALLFONTMAP" - a Ghostscript parameter, if the value is set to
86         "YES" then install the entries for the new fonts right into the main
87         "Fontmap" file. Otherwise just leave the file "Fontmap.ttf" in the
88         Ghostscript configuration directory.
89
90"HINTSUBST" - if the value is set to "YES" use the option "-H",
91         otherwise don't use it. This option enables the hint substitution
92         technique. If you have not installed the X11 patch described above,
93         use this option with great caution. See further description of this
94         option in the README file.
95
96"ENFORCEISO" - if the value is set to "YES" then disguise the
97         resulting fonts as the fonts in ISOLatin1 encoding. Historically this
98         was neccessary due to the way the installer scripts created the X11
99         font configuration files. It is not neccessary any more for this
100         purpose. But if you plan to use these fonts with some other
101         application that expects ISOLatin1 encoding then better enable this
102         option.
103
104"ALLGLYPHS" - if the value is set to "YES" then include all the
105         glyphs from the source fonts into the resulting fonts, even if these
106         glyphs are inaccessible. If it's set to "NO" then include only the
107         glyphs which have codes assigned to them. The glyphs without codes
108         can not be used directly. But some clever programs, such as the Type
109         1 library from XFree86 3.9 and higher can change the encoding on the
110         fly and use another set of glyphs. If you have not installed the X11
111         patch described above, use this option with great caution. See
112         further description of the option option "-a" in the README file.
113
114"GENUID" - if the value is set to "YES" then use the option "-uA" of
115         the converter to generate UniqueIDs for the converted fonts. The
116         standard X11 Type 1 library does not use this ID, so it may only be
117         neccessary for the other applications.  The script is clever enough
118         to generate different UniqueID for the same font converted to
119         multiple encodings. Also after conversion it checks all the fonts
120         generacted during the session for duplicated UniqueID and shows
121         those. Still, this does not quarantee that these UniqueIDs won't
122         overlap with some other fonts. The UniqueIDs are generated as hash
123         values from the font names, so it's guaranteed that if the
124         `"ttf2pt1_convert"' script runs multiple times it will generate the
125         same UniqueIDs during each run. See further description of this
126         option in the README file.
127
128"GENUID" - if the value is set to "YES" then create the ".pfb" files,
129         otherwise the ".pfa" files. The ".pfb" files are more compact but
130         contain binary data, so you may experience some troubles when
131         transferring them through the network.
132
133       The following parameters are used to locate the other scripts and
134       configuration files. By default the scripts do a bit of guessing for
135       them: they search in the ttf2pt1 installation directory if ttf2pt1 was
136       installed or otherwise suppose that you are running `"ttf2pt1_convert"'
137       with `"scripts"' subdirectory being the current directory.
138
139"ENCDIR" - directory containing the descriptions of encodings
140
141"MAPDIR" - directory containing the external map files
142
143       Besides that a few parameters are built into the `"ttf2pt1_convert"'
144       script itself.  You probably won't need to change them:
145
146       • "T1ASM", "TTF2PT1", "TRANS", "T1FDIR", "FORCEISO" - paths to the
147         other script
148
149       Also there are a few parameters controlling the installation of fonts
150       for Ghostscript. Please look at their description in the Ghostscript
151       section of documentation or in the ttf2pt1_x2gs(1) manual page before
152       running `"ttf2pt1_convert"'. If these parameters are set,
153       `"ttf2pt1_convert"' will call the `"x2gs"' script automatically to
154       install the newly converted fonts in Ghostscript.
155
156       After creating the configuration file run the `"ttf2pt1_convert"'
157       script. Look at the result and the log file in "DSTDIR".
158
159       Add the directory with newly converted fonts to the configuration of X
160       server or font server. For most of the systems this step is very
161       straightforward. For HP-UX it's rather tricky and poorly documented, so
162       the file FONTS.hpux gives a short description.
163
164       If you don't have the privileges of the root user, you still can
165       configure your private font server. Just use some non-standard port
166       number (see FONTS.hpux for an example, exept that you won't need all
167       the HP-related stuff on any other system).
168

FILES

170       • /usr/share/doc/ttf2pt1-3.4.4/convert.cfg.sample
171
172       • /usr/share/ttf2pt1/scripts/*
173
174       • /usr/share/doc/ttf2pt1-3.4.4/README
175
176       • /usr/share/doc/ttf2pt1-3.4.4/FONTS
177
178       • /usr/share/ttf2pt1/*
179
180       • /usr/bin/ttf2pt1
181

SEE ALSO

183ttf2pt1(1)
184
185ttf2pt1_x2gs(1)
186
187t1asm(1)
188

BUGS

190   Known problems
191       •   The "fonts.scale" files created by the older versions of the
192           "ttf2pt1" installation program (up to release 3.1) have conflicted
193           with the language definitions of the "Xfsft" font server and parts
194           of it included into XFree86. To overcome this incompatibility the
195           never versions creats the "fonts.scale" file describing all the
196           fonts as belonging to the "adobe-fontspecific" encoding and the
197           "fonts.alias" file with the proper names. The drawback of this
198           solution is that "xlsfonts" gives the list of twice more fonts. But
199           as a side effect the option "ENFORCEISO" in `"convert.cfg"' is not
200           required for X11 any more.
201
202       •   The conversion script has no support for Eastern multi-plane fonts.
203           Contribution of such a support would be welcome.
204
205
206
207version 3.4.4                  December 31, 2003            TTF2PT1_CONVERT(1)
Impressum