Previous Next

                                        431
SECTION 5.5                                                            Simple Fonts



• If the Encoding entry is a dictionary, the table is initialized with the entries
  from the dictionary’s BaseEncoding entry (see Table 5.11). Any entries in the
  Differences array are used to update the table. Finally, any undefined entries in
  the table are filled using StandardEncoding.

If a (3, 1) “cmap” subtable (Microsoft Unicode) is present:

• A character code is first mapped to a glyph name using the table described
  above.
• The glyph name is then mapped to a Unicode value by consulting the Adobe
  Glyph List (see the Bibliography).
• Finally, the Unicode value is mapped to a glyph description according to the
  (3, 1) subtable.

If no (3, 1) subtable is present but a (1, 0) subtable (Macintosh Roman) is present:

• A character code is first mapped to a glyph name using the table described
  above.
• The glyph name is then mapped back to a character code according to the stan-
  dard Roman encoding used on Mac OS (see note below).
• Finally, the code is mapped to a glyph description according to the (1, 0) sub-
  table.

In either of the cases above, if the glyph name cannot be mapped as specified, the
glyph name is looked up in the font program’s “post” table (if one is present) and
the associated glyph description is used.

Note: The standard Roman encoding that is used on Mac OS is the same as the
MacRomanEncoding described in Appendix D, with the addition of following 15 en-
tries and the replacement of the currency glyph with the Euro glyph, as shown in Ta-
ble 5.12.

 TABLE 5.12 Differences between MacRomanEncoding and Mac OS Roman encoding
NAME                        CODE (OCTAL)                 CODE (DECIMAL)

notequal                    255                          173

infinity                    260                          176

Previous Next