Skip to main content
Skip table of contents

(v13) PFIN-handled fonts

This page applies to Harlequin v13.1r0 and later; both Harlequin Core and Harlequin MultiRIP

In addition to new font formats, a PFIN module may replace the built-in handling for existing font types, such as TrueType. Consequently, a PFIN module must examine the font dictionary passed to it during the metrics and outline calls, first looking for a PFID that specifies the native font source, or at FontType or CIDFontType to establish the type of standard font to be accessed. The font dictionary is delivered as a sw_datum ,. All standard fonts (whether embedded in a job or a font or CIDfont resource, whether memory-resident or stored on disk), are accessed by the PFIN module through the font dictionary. In some cases the font data will be memory-resident and accessible entirely through the sw_data_api interface. In others there is a data stream, accessed through the sw_blob_api interface.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.