DLI Implementation and Reference Guide - Datalogics

5.4 DLI Implementation and Reference Guide
array be allocated to hold a sufficient number of entries to prevent this. In practice,
a dozen ASAtom entries should be sufficient.
Concepts and Facilities: Guide to the DL Pager Composition System
The dlpdfttload function returns the number of fonts loaded from the font file.
An exception may be raised for invalid parameters, if the font file could not be
opened, or if there was a problem invoking the font loader.
NOTE: If a given font file has already been loaded, dlpdfttload returns a -1,
and does not re-parse the font file (for performance reasons).
Once loaded, the font may then be created using the dlpdffontcreate calls (see
“Font Creation Calls” on page 4.6). The easiest means of creating the DLPDFFONT
structure is to call dlpdffontcreateembedded, supplying the DLPDFDOC in which
to use the font, the name of the font loaded (use the ASAtomGetString call to
obtain a C-string representation of the font name), and a NULL or "Type0" for the
third parameter. The fourth parameter must be True, since it is illegal to embed
Type0 fonts without subsetting.
Because the DLPDFINSTANCE font cache is searched for fonts before the system is
searched, a font loaded with dlpdfttload will be found before the system is
examined, unless a more specific font creation call is used. If both single-byte and
multibyte versions of a font are required for a DLI document, use the
dlpdffontcreatewithmetrics calls, specifying Type0 as the font type for
multibyte fonts, and either Type1 or TrueType as appropriate for the single-byte
font.
An easier alternative is to create the single-byte versions of the required fonts before
loading the fonts into the DLPDFINSTANCE. However, it is recommended that you
use the multibyte font for all text output if possible, to ensure optimal PDF file
viewing performance and file size.