Livecycle

Adding a new mapping to the font-mapping table in LiveCycle Designer ES

LiveCycle Designer ES uses the font-mapping table stored in the Designer.xci file to speed up the substitution of an unavailable font with one of the fonts on your computer. It contains several default entries for font mapping.

The Designer.xci file is located in the installation directory. However, as soon as LiveCycle Designer ES starts, the XCI file is copied to the user directory.

You can modify the default entries font-mapping table in the Designer.xci file.

Syntax

<equate from=’input_font_*_*’ to=’LiveCycle Designer ES_font_*_*’ force=”0″/>

Parameters

input_font

The name of the font used in the input PDF file.

LiveCycle Designer ES_font

The name of the font that is installed on your computer.

Asterisk (*)

Wildcard character. For example, the string *Cour* refers to all font names that contain the Cour string.

Question mark (?)

A single-character wildcard.

_*_*

Bold and italic attributes. Valid values after the first underscore are: *, normal, and bold. Valid values after the second underscore are *, normal, and italic.

force=”0″

Instructs LiveCycle Designer ES to search for the font on the system and use font mapping only if the font is unavailable.

force=”1″

Instructs LiveCycle Designer ES to map the font whether it is installed or not.

Example

The following line instructs LiveCycle Designer ES to map Courier font to Courier New when Courier is not available:

<equate from=’Courier_*_*’ to=’Courier New_*_*’ force=”0″/>

See also 

To import PDF files

How LiveCycle Designer ES converts PDF objects

Font-mapping table in ConvertPDF_FontMap.txt

Character-mapping table in ConvertPDF_CharMap.txt

Adding a new mapping to the font-mapping table in LiveCycle Designer ES