DLI Implementation and Reference Guide - Datalogics

Fonts 4.9
fields (and the font name given, if the font returned has a different name), will be used
to change the characteristics of the font if these are set.
CAUTION: It is not difficult to create an invalid font by setting these values
incorrectly. Therefore, the application should set only the fields that it is
concerned with affecting in the returned font, and leave the rest as NULL values.
The dlpdffontcreatewithmetrics function will match system fonts based on
the parameters in the PDEFontAttrs structure:
• If a system font is found, it will be altered to reflect the values in the
PDEFontAttrs structure (with the exceptions noted above).
• If no system font is found, a font will be created if a valid width table and set of
PDEFontAttrs are passed into this function.
• If no system font is found and an invalid width table or set of font attributes is
passed to this function, an exception will be raised.
The encoding field in the PDEFontAttrs font attributes structure is an ASAtom
containing one of the significant strings listed in "Predefined Font Encodings," or the
name of a predefined encoding or CMap file (as given in the PDF Reference manual).
This should correspond to the encoding format in which the font’s text is to be
typeset.
NOTE: Not all the predefined encodings may be used with all fonts. Details on
which types will accept which values are given in the section on predefined font
encodings later in this chapter.
The type field in the PDEFontAttrs font attributes structure should be filled in by
the user. If it is not (i.e. currently ASAtomNull), then any type of font (Type1,
TrueType, etc.) may be used. Otherwise, a font of the matching type will be selected if
present. If no font of the matching type is found, any suitably-named font will be
returned.
The charSet field in the PDEFontAttrs font attributes structure may be set to
"Roman" or ASAtomNull. With an ASAtom value of "Roman," only a font