Font entries

If you do not use the Type Manager, the fonts must be included as driver file font entries in the device drivers used by StreamServer when processing the documents. If you are using Type1 fonts, you must also import the font from the Windows Fonts directory to a resource set connected to the Message where the font is used.

Driver file font entries

A driver file can contain readfont entries and font entries with character width tables.

Example 48

Readfont entry

Font "Century" ReadFont "CENTURY.TTF" 
SelectPrefix "Century" Codepage "Ansi"

 

Example 49

Font entry with character width table

// Century - regular, italic

WidthTable 1 Size 7200
7200  5400  5400  5400  5400  5400  5400  5400  5400  5400...
...
End

Font "Century" WidthTable 1 
SelectPrefix "Century" CodePage "Ansi"

 

A driver file can also include mapfont entries where fonts are mapped to other fonts. In the example below, the font Times_New_Roman_bold_underline is mapped to Arial_bold. This means that if StreamServer finds the font Times_New_Roman_bold_underline, it will use Arial_bold in the output.

Example 50

Mapfont entry

mapfont "Times_New_Roman_bold_underline" "Arial_bold"

 

Adding font entries to driver files

If the driver file does not include entries for all fonts you are using, you must add the missing font entries to the driver file. See Adding font entries to driver files for information on how to add font entries.

Making fonts available to the printer

All fonts included in the output from the StreamServer must be available to the printer (or equivalent) that receives the output. If there are fonts that are not installed on the printer, you must make them available to the printer. See Making fonts available to the printer.