PDFlib 8 Windows COM/.NET Tutorial

exclam 33 0x0021
...
If no Unicode value has been specified PDFlib will search for a suitable Unicode value in
its internal tables. A Unicode value can be specified instead of a glyph name:
% Code page definition for PDFlib, based on Unicode values
% Unicode code
0x0020 32
0x0021 33
...
More formally, the contents of an encoding or code page file are governed by the following
rules:
> Comments are introduced by a percent ’%’ character, and terminated by the end of
the line.
> The first entry in each line is either a PostScript glyph name or a hexadecimal Unicode
value composed of a 0x prefix and four hex digits (upper or lower case). This is
followed by whitespace and a hexadecimal (0xoo–0xFF) or decimal (0–255) character
code. Optionally, name-based encoding files may contain a third column with the
corresponding Unicode value.
> Character codes which are not mentioned in the encoding file are assumed to be undefined.
Alternatively, a Unicode value of 0x0000 or the character name .notdef can
be provided for unused slots.
> All Unicode values in an encoding or codepage file must be smaller than U+FFFF.
As a naming convention we refer to name-based tables as encoding files (*.enc), and Unicode-based
tables as code page files (*.cpg), although PDFlib treats both kinds in the
same way.
4.2 Single-Byte (8-Bit) Encodings 103