DLI Implementation and Reference Guide - Datalogics

Fonts 4.11
recommends that encoding vectors not be supplied for TrueType fonts. Please see the
PDF Reference Manual for further details.
dlpdffontcreatewithmetricsembedded
This method behaves the same as dlpdffontcreatewithmetrics, but with the
following exception: all fonts created with this method will be embedded (if possible),
regardless of the setting of the document's embed fonts flag; if subset is TRUE the
embedded font will be subset, if it is FALSE, the font will be fully embedded,
regardless of the document's font embedding settings. If the requested font is not
found by DLI, or the font is not embeddable due to license restrictions, an exception
will be raised.
By manipulating the font calls within the hellodli.c sample program, you can
compare results of using font references, embedded fonts and multi-master fonts.
Predefined Font Encodings
Use of an ASAtomNull for a font encoding will yield a font which uses its "Built-In"
encoding; this is recommended for symbol (e.g. Pi) fonts where a named encoding is
not desired. DLI recognizes a number of strings that, when used to create ASAtoms
and passed into DLI functions requiring a font encoding, serve to denote certain
predefined encodings for a font.
Setting the document encoding via dlpdfdocsetencoding does not affect the
encoding used for symbol fonts, to prevent these from becoming inadvertently
invalidated. Named encodings passed into the font creation calls above, however, will
be reflected in symbol fonts.
The strings, and the font types they are valid for, are enumerated below: