ttf2tfm.1

字体缩放显示

KS X 1001 (Wansung)	5
.br
KS X 1001 (Johab)	6
.br
UCS-4	10
.PP
The program will abort if you specify an invalid platform/encoding ID
pair.
It will then show the possible pid/eid pairs.
Please note that most fonts have at most two or three cmaps, usually
corresponding to the pid/eid pairs (1,0), (3,0), or (3,1) in case of
Latin based fonts.
Valid Microsoft fonts should have a (3,1) mapping table, but some
fonts exist (mostly Asian fonts) which have a (3,1) cmap not encoded
in Unicode.
The reason for this strange behavior is the fact that some old
MS\ Windows versions will reject fonts having a non-(3,1) cmap (since
all non-Unicode Microsoft encoding IDs are for Asian MS\ Windows
versions).
.PP
The
.B \-P
and
.B \-E
options of
.B ttf2tfm
must be equally specified for
.BR ttf2pk ;
the corresponding parameters in a map file are `Pid' and `Eid',
respectively.
.PP
The default pid/eid pair is (3,1).
.PP
Similarly, an
.B \-f
option must be specified as `Fontindex' parameter in a map file.
.PP
If you use the
.B \-N
switch, all cmaps are ignored, using only the PostScript names in the
TrueType font.
The corresponding option in a map file is \%`PS=Only'.
If you use the
.B \-n
switch, the default glyph names built into
.B ttf2tfm
are replaced with the PS glyph names found in the font.
In many cases this is not what you want because the glyph names in the
font are often incorrect or non-standard.
The corresponding option in a map file is \%`PS=Yes'.
.PP
Single replacement glyph names specified with
.B \-r
must be given directly as `\c
.IR "old-glyphname new-glyphname" '
in a map file;
.B \-R
is equivalent to the `Replacement' option.
.
.
.SH INPUT AND OUTPUT ENCODINGS
You must specify the encoding vectors from the TrueType font to the
raw \*(TX
font and from the raw \*(TX
font to the virtual \*(TX
font exactly as with
.BR afm2tfm ,
but you have more possibilities to address the character codes.
[With `encoding vector' a mapping table with 256\ entries in form of a
PostScript vector is meant; see the file
.C \%T1-WGL4.enc
of this package for an example.]
With
.BR afm2tfm ,
you must access each glyph with its Adobe glyph name, e.g.\ \c
\%`/quotedsingle' or \%`/Acircumflex'.
This has been extended with
.BR ttf2tfm ;
now you can (and sometimes must) access the code points and/or glyphs
directly, using the following syntax for specifying the character position
in decimal, octal, or hexadecimal notation:
`/.c\c
.IR <decimal-number> ',
`/.c0\c
.IR <octal-number> ',
or `/.c0x\c
.IR <hexadecimal-number> '.
Examples: \%`/.c72', \%`/.c0646', \%`/.c0x48'.
To access a glyph index directly, use the character `g' instead of `c' in
the just introduced notation.
Example: \%`/.g0x32'.
[Note: The `.cXXX' notation makes no sense if
.B \-N
is used.]
.PP
For pid/eid pairs (1,0) and (3,1), both
.B ttf2tfm
and
.B ttf2pk
recognize built-in default Adobe glyph names; the former follows the names
given in Appendix\ E of the book `Inside Macintosh', volume\ 6, the latter
uses the names given in the TrueType Specification (WGL4, a Unicode subset).
Note that Adobe names for a given glyph are often not unique and do
sometimes differ, e.g., many PS fonts have the glyph `mu', whereas this
glyph is called `mu1' in the WGL4 character set to distinguish it from the
real Greek letter mu.
Be also aware that OpenType (i.e. TrueType\ 2.0) fonts use an updated WGL4
table; we use the data from the latest published TrueType specification
(1.66).
You can find those mapping tables in the source code file
.C \%ttfenc.c .
.PP
On the other hand, the switches
.B \-n
and
.B \-N
makes
.B ttf2tfm
read in and use the PostScript names in the TrueType font itself (stored
in the `post' table) instead of the default Adobe glyph names.
.PP
Use the
.B \-r
switch to remap single glyph names and
.B \-R
to specify a file containing replacement glyph name pairs.
.PP
If you don't select an input encoding, the first 256\ glyphs of the
TrueType font with a valid entry in the selected cmap will be mapped
to the \*(TX
raw font (without the
.B \-q
option,
.B ttf2tfm
prints this mapping table to standard output), followed by all glyphs
not yet addressed in the selected cmap.
However, some code points for the (1,0) pid/eid pair are omitted since
they do not represent glyphs useful for \*(TX:
0x00 (null), 0x08 (backspace), 0x09 (horizontal tabulation), 0x0d
(carriage return), and 0x1d (group separator).
The `invalid character' with glyph index\ 0 will be omitted too.
.PP
If you select the
.B \-N
switch, the first 256\ glyphs of the TrueType font with a valid PostScript
name will be used in case no input encoding is specified.
Again, some glyphs are omitted:  `.notdef', `.null', and
`nonmarkingreturn'.
.PP
If you don't select an  output encoding,
.B ttf2tfm
uses the same mapping table as
.B afm2tfm
would use (you can find it in the source code file
.C \%texenc.c );
it corresponds to \*(TX
typewriter text.
Unused positions (either caused by empty code points in the mapping
table or missing glyphs in the TrueType font) will be filled (rather
arbitrarily) with characters present in the input encoding but not
specified in the output encoding (without the
.B \-q
option
.B ttf2tfm
prints the final output encoding to standard output).
Use the
.B \-u
option if you want only glyphs in the virtual font which are defined
in the output encoding file, and nothing more.
.PP
One feature missing in
.B afm2tfm
has been added which is needed by \*(LX's T1 encoding:
.B ttf2tfm
will construct the glyph `Germandbls' (by simply concatenating two `S'
glyphs) even for normal fonts if possible.
It appears in the glyph list as the last item, marked with an asterisk.
Since this isn't a real glyph it will be available only in the virtual
font.
.PP
For both input and output encoding, an empty code position is
represented by the glyph name \%`/.notdef'.
.PP
In encoding files, you can use `\\' as the final character of a line to
indicate that the input is continued on the next line.
The backslash and the following newline character will be removed.
.PP
.
.
.SH SUBFONT DEFINITION FILES
CJKV (Chinese/Japanese/Korean/old Vietnamese) fonts usually contain
several thousand glyphs; to use them with \*(TX
it is necessary to split such large fonts into subfonts.
Subfont definition files (usually having the extension `\c
.C \&.sfd ')
are a simple means to do this smoothly.
.PP
A subfont file name usually consists of a prefix, a subfont infix, and
a postfix (which is empty in most cases), e.g.
.PP
.in +2m
ntukai23 \(-> prefix: ntukai, infix: 23, postfix: (empty)
.PP
Here the syntax of a line in an
.C SFD
file, describing one subfont.
The hash character `#' starts a comment; the remainder of the current line
is ignored.
.in +2m
.TP
.I <whitespace> <infix> <whitespace> <ranges> <whitespace>
.sp
.TP
.IR <infix> \ :=
anything except whitespace.
It is best to use only alphanumerical characters.
.TP
.IR <whitespace> \ :=
space, formfeed, carriage return, horizontal and vertical tabs -- no
newline characters.
.TP
.IR <ranges> \ :=
.IR "<ranges> <whitespace> <codepoint>" \ |
.br
.IR "<ranges> <whitespace> <range>" \ |
.br
.I <ranges> <whitespace> <offset> <whitespace> <range>
.TP
.IR <codepoint> \ :=
.I <number>
.br
.TP
.IR <range> \ :=
.IR <number> \ `_' \ <number>
.br
.TP
.IR <offset> \ :=
.IR <number> \ `:'
.TP
.IR <number> \ :=
hexadecimal (prefix `0x'), decimal, or octal (prefix `0')
.PP
A line can be continued on the next line with a backslash ending the line.
The ranges must not overlap; offsets have to be in the range 0-255.
.PP
Example:
.PP
.in +2m
The line
.PP
.in +4m
.C "03   10: 0x2349 0x2345_0x2347"
.PP
.in +2m
assigns to the code positions 10, 11, 12, and\ 13 of the subfont
having the infix `03' the character codes 0x2349, 0x2345, 0x2346, and
0x2347 respectively.
.PP
The
.C SFD
files in the distribution are customized for the CJK package for
\*(LX.
.PP
You have to embed the
.C SFD
file name into the
.C TFM
font name (at the place where the infix will appear) surrounded by two
`@' signs, on the command line resp.\ a map file;
both
.B ttf2tfm
and
.B ttf2pk
switch then to subfont mode.
.PP
It is possible to use more than a single
.C SFD
file by separating them with commata and no whitespace; for a given
subfont, the first file is scanned for an entry, then the next file,
and so on.
Later entries override entries found earlier (possibly only partially).
For example, the first
.C SFD
file sets up range 0x10-0xA0, and the next one modifies entries
0x12 and 0x25.
As can be easily seen, this algorithm allows for adding and replacing,
but not for removing entries.
.PP
Subfont mode disables the options 
.BR \-n , " \-N" , " \-p" ,
.BR \-r , " \-R" , " \-t" ,
.BR \-T , " \-u" , " \-v" , " \-V"
and
.B \-w
for
.BR ttf2tfm ;
similarly, no `Encoding' or `Replacement' parameter is allowed in
a map file.
Single replacement glyph names are ignored too.
.PP
.B ttf2tfm
will create all subfont
.C TFM
files specified in the
.C SFD
files (provided the subfont contains glyphs) in one run.
.PP
Example:
.PP
.in +2m
The call
.PP
.in +4m
.C "ttf2tfm ntukai.ttf ntukai@Big5,Big5-supp@"
.PP
.in +2m
will use
.C Big5.sfd
and
.C Big5-supp.sfd ,
producing
.I all
subfont files
.C ntukai01.tfm ,
.C ntukai02.tfm ,
etc.
.
.
.SH "RETURN VALUE"
ttf2tfm returns 0 on success and 1 on error; warning and error
messages are written to standard error.
.
.
.SH "SOME NOTES ON FILE SEARCHING"
Both
.B ttf2pk
and
.B ttf2tfm
use either the
.BR kpathsea ,
.BR emtexdir ,
or
.B MiK\*(TX
library for searching files 
.RB ( emtexdir
will work only on operating systems which have an MS-DOSish background, i.e.
MS-DOS, OS/2, Windows;
.B Mik\*(TX
is specific to MS Windows).
.PP
As a last resort, both programs can be compiled without a search library;
the searched files must be then in the current directory or specified with a
path.
Default extensions will be appended also (with the exception that only `\c
.C \&.ttf '
is appended and not `\c
.C \&.ttc ').
.
.
.SS kpathsea
Please note that older versions of
.B kpathsea
(<3.2) have no special means to seach for TrueType fonts and related
files, thus we use the paths for PostScript related stuff.
The actual version of kpathsea is displayed on screen if you call
either
.B ttf2pk
or
.B ttf2tfm
with the
.B \-\^\-version
command line switch.
.PP
Here is a table of the file type and the corresponding
.B kpathsea
variables.
.C TTF2PKINPUTS
and
.C TTF2TFMINPUTS
are program specific environment variables introduced in
.B kpathsea
version\ 3.2:
.PP
.in +4m
.ta 2i
.br
.C \&.ttf \ and "\ .ttc	TTFONTS"
.br
.C "ttf2pk.cfg	TTF2PKINPUTS"
.br
.C "\&.map	TTF2PKINPUTS"
.br
.C "\&.enc	TTF2PKINPUTS, TTF2TFMINPUTS"
.br
.C "\&.rpl	TTF2PKINPUTS, TTF2TFMINPUTS"
.br
.C "\&.tfm	TFMFONTS"
.br
.C "\&.sfd	TTF2PKINPUTS, TTF2TFMINPUTS"
.PP
And here the same for pre-3.2-versions of
.B kpathsea:
.PP
.in +4m
.ta 2i
.br
.C \&.ttf \ and "\ .ttc	T1FONTS"
.br
.C "ttf2pk.cfg	TEXCONFIG"
.br
.C "\&.map	TEXCONFIG"
.br
.C "\&.enc	TEXPSHEADERS"
.br
.C "\&.rpl	TEXPSHEADERS"
.br
.C "\&.tfm	TFMFONTS"
.br
.C "\&.sfd	TEXPSHEADERS"
.PP
Finally, the same for pre-3.0-versions (as used e.g. in te\*(TX\ 0.4):
.PP
.in +4m
.ta 2i
.br
.C \&.ttf \ and "\ .ttc	DVIPSHEADERS"
.br
.C "ttf2pk.cfg	TEXCONFIG"
.br
.C "\&.map	TEXCONFIG"
.br
.C "\&.enc	DVIPSHEADERS"
.br
.C "\&.rpl	DVIPSHEADERS"
.br
.C "\&.tfm	TFMFONTS"
.br
.C "\&.sfd	DVIPSHEADERS"
.PP
Please consult the info files of
.B kpathsea
for details on these variables.
The decision whether to use the old or the new scheme will be done
during compilation.
.PP
You should set the
.C TEXMFCNF
variable to the directory where your
.C texmf.cnf
configuration file resides.
.PP
Here is the proper command to find out to which value a
.B kpathsea
variable is set (we use
.C TTFONTS
as an example).
This is especially useful if a variable isn't set in
.C texmf.cnf
or in the environment, thus pointing to the default value which is
hard-coded into the
.B kpathsea
library.
.PP
.in +2m
.C "kpsewhich -progname=ttf2tfm -expand-var='$TTFONTS'"
.PP
We select the program name also since it is possible to specify
variables which are searched only for a certain program -- in our
example it would be
.C TTFONTS.ttf2tfm .
.PP
A similar but not identical method is to say
.PP
.in +2m
.C "kpsewhich -progname=ttf2tfm -show-path='truetype fonts'"
.PP
[A full list of format types can be obtained by saying `\c
.C "kpsewhich --help" '
on the command line prompt.]
This is exactly how
.B ttf2tfm
(and
.BR ttf2pk )
searches for files; the disadvantage is that all variables are expanded
which can cause very long strings.
.
.
.SS emtexdir
Here the list of suffixes and their related environment variables to be
set in
.C autoexec.bat
(resp. in
.C config.sys
for OS/2):
.PP
.in +4m
.ta 2i
.br
.C \&.ttf \ and "\ .ttc	TTFONTS"
.br
.C "ttf2pk.cfg	TTFCFG"
.br
.C "\&.map	TTFCFG"
.br
.C "\&.enc	TTFCFG"
.br
.C "\&.rpl	TTFCFG"
.br
.C "\&.tfm	TEXTFM"
.br
.C "\&.sfd	TTFCFG"
.PP
If one of the variables isn't set, a warning message is emitted.
The current directory will always  be searched.
As usual, one exclamation mark appended to a directory path causes
subdirectories one level deep to be searched, two exclamation marks cause
all subdirectories to be searched.
Example:
.PP
.in +2m
.C TTFONTS=c:\\\\fonts\\\\truetype!!;d:\\\\myfonts\\\\truetype!
.PP
Constructions like `\c
.C c:\\\\fonts!!\\\\truetype '
aren't possible.
.
.
.SS MiK\*(TX
Both
.B ttf2tfm
and
.B ttf2pk
have been fully integrated into
.BR MiK\*(TX .
Please refer to the documentation of
.B MiK\*(TX
for more details on file searching.
.
.
.SH PROBLEMS
Many
.B vptovf
implementations allow only 100\ bytes for the
.C TFM
header (the limit is 1024 in the
.C TFM
file format itself): 8\ bytes for checksum and design size, 40\ bytes for the
family name, 20\ bytes for the encoding, and 4\ bytes for a face byte.
There remain only 28\ bytes for some additional information which is used by
.B ttf2tfm
for an identification string (which is essentially a copy of the command
line), and this limit is always exceeded.

The optimal solution is to increase the value of
.I \%max_header_bytes
in the file
.C vptovf.web
(and probably
.C pltotf.web
too) to, say,\ 400
and recompile
.B vptovf
(and
.BR pltotf ).
Otherwise you'll get some (harmless) error messages like
.PP
.in +2m
.C "This HEADER index is too big for my present table size"
.PP
which can be safely ignored.
.
.
.SH "SEE ALSO"
.BR ttf2pk (1),
.BR afm2tfm (1),
.BR vptovf (1),
.br
the info pages for
.B dvips
and
.B kpathsea
.
.
.SH AVAILABILITY
.B ttf2tfm
is part of the FreeType\ 1 package, a high quality TrueType rendering
library.
.
.
.SH AUTHORS
Werner LEMBERG
.C <[e-mail]>
.br
Fr\('ed\('eric LOYER
.C <[e-mail]>