Roman Character Set can be simulated. The only exception is in case of Symbolic font, which is
not very useful.
• If the font ﬁle name is preceded by a !, the font is not read at all, and is assumed to be available
on the system. This option can be used to create pdf ﬁles which do not contain embedded fonts.
The pdf output then works only on systems where the resource of the used font is available. It’s
not very useful for document exchange, as the pdf is not ‘portable’ at all. On the other hand it is
very useful when you wish to speed up running of pdfT
Xduring interactive work, and only in a
ﬁnal version embed all used fonts. Don’t over--estimate gain in speed and when distributing ﬁles,
always embed the fonts! This feature requires Acrobat Reader to have access to installed fonts
on the system. This has been tested on Win95 and Unix (Solaris).
Note that the standard14 fontsare neverdownloaded, evenwhentheyarespeciﬁed tobedownloaded
in map ﬁles. When one suﬀers from invalid lookups, for instance when pdfT
Xtries to open a .pfa
ﬁle instead of a .pfb one, one can add the suﬃx to the ﬁlename. In this respect, pdfT
relies on the kpathsea libraries.
encoding speciﬁes the name of the ﬁle containing the external encoding vector to be used for the
font. The ﬁle name may be preceded by a <, but the eﬀect is the same. The format of the encoding
vector is identical to that used by dvips. If no encoding is speciﬁed, the font’s built--in default
encoding is used. It may be omitted if you are sure that the font resource has the correct built--in
encoding. Ingeneral this optionishighly preferred and is required when subsettinga TrueType font.
special instructions can be used to manipulate fonts similar to the way dvips does. Currently only
the keyword SlantFont is interpreted, other instructions are just ignored.
If a used font is not present in the map ﬁles, ﬁrst pdfT
Xwill look for a source with suﬃx .pgc,
which is a so--called pgc source (pdf Glyph Container)
.If no pgcsource is available, pdfT
to use pk fonts in a normal way as dvi drivers do, on--the--ﬂy creating pk fonts if needed.
Lines containing nothing apart from texname stand for scalable Type 3 fonts. For scalable fonts as
Type 1, TrueType and scalable Type 3 font, all the fonts loaded from a tfm at various sizes will be
included only once in the pdf output. Thus if a font, let’s say csr10, is described in one of the map
ﬁles, then it will be treated as scalable. As a result the font source for csr10 will be included only
once for csr10, csr10 at 12pt etc. So pdfT
Xtries to do its best to avoid multiple downloading of
identical font sources. Thus vector pgcfonts should be speciﬁed as scalable Type 3 in map ﬁles like:
It doesn’t hurt much if a scalable Type 3 font is not given in map ﬁles, except that the font source
will be downloaded multiple times for various sizes, which causes a much larger pdf output. On the
other hand if a font is in the map ﬁles is deﬁned as scalable Type 3 font and its pgc source is not
scalable or not available, pdfT
Xwill use pk font instead; the pdf output is still valid but some fonts
may look ugly because of the scaled bitmap.
ASlantFont is speciﬁed similarly as for dvips. A SlantFont or ExtendFont must be used with
embedding font ﬁle. Note that the base name, the PostScript name like Symbol or Times--Roman,
cannot be given, as pdfT
Xnever embeds a base font.
Thisis a text ﬁle containing a pdf Type3 font,created by METAPOST using some utilitiesby Hans Hagen. Ingeneralpgc ﬁles
cancontainwhateverallowed inpdfpage description, which maybe used tosupportfontsthat arenot availableinMETAFONT.
At themoment pgc fontsarenot very useful,asvector Type 3fontsarenot displayed very well inAcrobat Reader, but it may
be more usefulwhen Type 3font handling getsbetter.