SECTION 5.5
419
Simple Fonts
Example 5.8
17 0 obj
<< /Type /Font
/Subtype /TrueType
/BaseFont /NewYork , Bold
/FirstChar 0
/LastChar 255
/Widths 23 0 R
/FontDescriptor 7 0 R
/Encoding /MacRomanEncoding
>>
endobj
23 0 obj
[ 0 333 333 333 333 333 333 333 0 333 333 333 333 333 333 333 333 333
…
Omitted data
…
803 790 803 780 780 780 340 636 636 636 636 636 636 636 636 636 636
]
endobj
Note that for CJK (Chinese, Japanese, and Korean) fonts, the host font system’s
font name is often encoded in the host operating system’s script. For instance, a
Japanese font may have a name that is written in Japanese using some (unidenti-
fied) Japanese encoding. Thus, TrueType font names may contain multiple-byte
character codes, each of which requires multiple characters to represent in a PDF
name object (using the
#
notation to quote special characters as needed).
5.5.3 Font Subsets
PDF 1.1 permits documents to include subsets of Type 1 and TrueType fonts.
The font and font descriptor that describe a font subset are slightly different
from those of ordinary fonts. These differences allow an application to recog-
nize font subsets and to merge documents containing different subsets of the
same font. (For more information on font descriptors, see Section 5.7, “Font De-
For a font subset, the PostScript name of the font—the value of the font’s
BaseFont
entry and the font descriptor’s
FontName
entry—begins with a
tag
followed by a plus sign (
+
). The tag consists of exactly six uppercase letters; the
choice of letters is arbitrary, but different subsets in the same PDF file must have
different tags. For example,
EOODIA+Poetica
is the name of a subset of Poetica
®
, a
Type 1 font. (See implementation note 63 in Appendix H.)