Font Handling

Here are some guidelines for font handling:

  • The set of fonts in Designer is determined from the fonts on the computer and fonts that are enumerated in the Designer.xdc file.

  • It is important that the fonts used to design the form in Designer are also available when the form is output from Output. For example, when Output renders a PDF file that uses unavailable fonts, the missing fonts are substituted. The font substitution can cause the layout of the form to change from the original design in Designer. Similarly, rendering documents in PostScript, Printer Control Language (PCL), or one of the supported label formats produces unexpected results when missing fonts are substituted.

  • Output can embed or reference additional fonts in the generated output.

  • For PDF forms, you can select the Embed Fonts option in the Form Properties (Save As tab) dialog box to embed the fonts. (See Designer Help.)

  • When output is generated for either PCL or PostScript, preference is given to fonts known to be standard fonts included on the printer. These fonts are known as printer-resident fonts. Printer-resident fonts are stored in a printer’s memory or on a hard drive that is connected to the printer.

  • Consult with your network printer administrator and test printing a few sample forms from Output to determine which fonts are available.

  • Forms that result in a smaller file size are rendered more quickly and transferred to the printer more efficiently. To minimize the file size, use printer-resident fonts and keep the number of embedded fonts used to a minimum.

  • To ensure that a form design looks the same across PDF, PCL, and PostScript output devices, use these fonts, which are resident in most computers:

    • Courier

    • Arial

    • Times New Roman

  • Alternatively, you can choose to embed a font. The embedded font looks the same across all devices as well, but a larger output file is produced.

  • For form designs that are rendered only as PDF forms, use any of the following fonts, which are included with Adobe Reader to optimize performance:

    • Courier Std, Courier Std Bold, Courier Std Bold Oblique, Courier Std Oblique

    • Minion® Pro Bold, Minion Pro Bold It, Minion Pro It, Minion Pro Regular

    • Myriad® Pro Bold, Myriad Pro Bold It, Myriad Pro It, Myriad Pro Regular

    • Symbol (Type 1)

Specifying printer-resident fonts in Designer

The fonts you use in your form design do not need to be present on the computer hosting Designer. Usually, you select a font from the Font list in the Font palette; however, Designer also permits you to enter a font name. The font name you enter must be identical to the network printer’s printer-resident font name. (See Wordbench Help.)

Font mapping

Designer and Output provide font mapping to accommodate the unique font requirements of printers. In the Designer installation directory, the Designer.xci file contains the default set of font mappings. This configuration file can be extended to accommodate additional font mappings. However, this file affects only Designer. The font mappings used for processing the form, in concert with a particular XDC device profile, must also be in the target XDC file. For information about adding a new mapping to the font-mapping table, see Designer Help.

The following excerpt is from the Designer.xci file. It shows the XML markup describing font-mapping statements that map requests for various Helvetica fonts to similar Arial fonts.

<equate from="Helvetica Black_*_*" to="Arial Black_*_*" force="0"/> 
<equate from="HelveticaBlack_*_*" to="Arial Black_*_*" force="0"/> 
<equate from="Helvetica-Black_*_*" to="Arial Black_*_*" force="0"/> 
<equate from="Helvetica_*_*" to="Arial_*_*" force="0"/> 
<equate from="Helv_*_*" to="Arial_*_*" force="0"/>

The font-mapping capabilities provide for strict control over mapping. You can map whole typefaces or an individual typeface with a particular weight and posture. The force attribute denotes whether a font is always mapped or only when the requested font is not available.

The equate font-mapping statements are evaluated in order until a matching statement is encountered.

(See “Adding a new mapping to the font-mapping table in Designer” in Designer Help.)