PDFlib 8 Windows COM/.NET Tutorial

The font will be registered in PDFlib, and its name can be supplied to load_font( ) along
with an encoding which contains the names of the glyphs in the Type 3 font. Please note
the following when working with Type 3 fonts:
> Similar to patterns and templates, images cannot be opened within a glyph description.
However, they can be opened before starting a glyph description, and placed
within the glyph description. Alternatively, inline images may be used for small bitmaps
to overcome this restriction.
> Due to restrictions in PDF consumers all characters used in text output must actually
be defined in the font: if character code x is to be displayed with any text output
function, and the encoding contains glyphname at position x, then glyphname must
have been defined via begin_glyph( ).
> Some PDF consumers require a glyph named .notdef if codes will be used for which
the corresponding glyph names are not defined in the font. Acrobat 8 may even
crash if a .notdef glyph is not present. The .notdef glyph must be present, but it may
simply contain an empty glyph description.
> When normal bitmap data is used to define characters, unused pixels in the bitmap
will print as white, regardless of the background. In order to avoid this and have the
original background color shine through, use the mask parameter for constructing
the bitmap image.
> The interpolate option for images may be useful for enhancing the screen and print
appearance of Type 3 bitmap fonts.
> Type 3 fonts do not contain any typographic properties such as ascender, descender,
etc. However, these can be set by using the corresponding options in load_font( ).
120 Chapter 5: Font Handling (Edition for COM, .NET, and REALbasic)