Skip to main content
Skip table of contents

(v13) PostScript language configuration of the pluggable font interface

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

The setpfinparams operator takes a dictionary containing configuration options for PFIN and individual PFIN modules. An example configuration is:

                        /FontType <<
                          42 [ /Foo /Bar ]
                        /Foo <<
                          /PassOnError false
                          /PassOnUnsupported true
                      >> setpfinparams

This example sends Type1 and Type2 PostScript fonts to PFIN modules “Foo” and “Bar” respectively, and TrueTypes to “Foo” falling back to “Bar” only if the font is of an unsupported construction. All other font types are supported directly by the Harlequin RIP except those defined by PFIN modules, which are always handled by their owner (with no possible fallback). It also configures the “Foo” module’s default instance.

Configuration for a particular module instance is passed in the call to configure. This is called whenever setpfinparams is invoked.

As well as sending all fonts of a particular type to a module or a list of modules, individual fonts can be marshalled explicitly, for example:

                        /Exceptions <<
                          /Pragmata-* /Foo % note wildcarded font name match
                          /CaflischScriptPro-Regular [ /Bar /Foo ]
                      >> setpfinparams

NOTE:  The current version does not contain a “SW” PFIN module to allow the Harlequin RIP itself to act as the fallback for a font or fonttype.

JavaScript errors detected

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

If this problem persists, please contact our support.