Font mapping

If a font is installed on a client computer, it is available in the drop-down list in Designer. If the font is not installed, it is necessary to specify the font name manually. The “Permanently replace unavailable fonts” option in Designer can be off. Otherwise, when the XDP file is saved in Designer, the substitution font name is written to the XDP file. This means that the printer-resident font is not used.

To design a form that uses printer-resident fonts, choose a typeface name in Designer that matches the fonts that are available on the printer. A list of fonts that are supported for PCL or PostScript are located in the corresponding device profiles (XDC files). Alternatively, font mapping can be created to map nonprinter-resident fonts to printer-resident fonts of a different typeface name. For example, in a PostScript scenario, references to the Arial font can be mapped to the printer-resident Helvetica typeface.

Two types of OpenType fonts exist. One type is a TrueType OpenType font that PCL supports. The other is CFF OpenType. PDF and PostScript output supports embedded Type-1, TrueType, and OpenType fonts. PCL output supports embedded TrueType fonts.

Type-1 and OpenType fonts are not embedded in PCL output. Content that is formatted with Type-1 and OpenType fonts is rasterized and generated as a bitmap image that can be large and slower to generate.

Downloaded or embedded fonts are automatically substituted when generating PostScript, PCL, or PDF output. This means that only the subset of the font glyphs that are required to properly render the generated document is included in the generated output.

For information about creating form designs for the Output service, including handling fonts, see Designing Forms for LiveCycle Output.

// Ethnio survey code removed