Posts tagged "Font"

Acrobat/Reader X: how to set the default font and font size in the Typewriter tool


If you are using the Typewriter tool in Acrobat/Reader you may notice that the default font and font size changes according to the font style already used in the PDF document.  The default font for the Typewriter tool should be set each time you finish using the tool and close Acrobat/Reader.  You may wish to reset/set the default font and font size to some custom value.


You can set the commenting font and font size in the “Commenting” section in the Preferences.

You can also select the “Comment” Tab between “Tool” and “Share”, right-click on the comment in the “Comments List” that has your desired font setting, and then select “Properties…”.  Check the box that says “Make properties default” and click OK.


If this still does not work, then you can set the default font and font size in the registry.  Please note that editing the registry can lead to corruption on your system and should only be attempted by experienced users or administrators.

We cannot provide support for any issues that may occur due to editing the registry, so we would recommend to do a full registry backup before making any changes.

To change the font:

1. Close Acrobat/Reader
2. Start—>Run—>Regedit
3. Navigate to: HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\10.0\Annots\cAnnots\cFreeText_003aFreeTextTypewriter\crichDefaults\cfontFamily
4. Click the cfontFamily key on the left.
5. Double-click the a0 key on the right.
6. Change the a0 value to the font name you require.
7. Save

To change the font size:

1. Close Acrobat/Reader
2. Start—>Run—>Regedit
3. Navigate to: HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\10.0\Annots\cAnnots\cFreeText_003aFreeTextTypewriter\crichDefaults
4. Double-click the dtextSize key on the right.
5. Change the dtextSize value to the font size value you require.
6. Save

Additional information

In Adobe Acrobat, if you want instructions to enable the Typewriter tool you should refer to the following post:

In Adobe Reader, if you cannot find the Typewriter tool you should refer to the following post:

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 3.7/10 (41 votes cast)

LiveCycle ES2: “The embedded font program ‘PZSWZL+CustomSymbol’ cannot be read.”


When you convert PDF files to PDF/A using LiveCycle ES2, and then validate the files with a PDF validator, you receive the following error:

The embedded font program ‘PZSWZL+CustomSymbol’ cannot be read.

The font PZSWZL+CustomSymbol must be embedded.

Validation in LiveCycle ES2 and Acrobat 8 or 9 validates the PDF/A without errors.  Validation with current validators such as Acrobat X Preflight, or 3 Heights PDF Validator produce the error above.


This issue is a problem in LiveCycle ES2 (,, and as it should also return an error that the PDF/A is invalid.  This issue is fixed in LiveCycle ES3 (LC10) and later.  There is a patch available for ES2 SP1 and SP2, so contact enterprise support if you require one of these patches.

Additional information

PDF 1.4 recognizes only the following cmaps for TrueType fonts:

  • cmap subtable with platform ID 3 and encoding ID 1 (Microsoft Unicode, also called  [3,1])
  • cmap subtable with platform ID 1 and encoding 0 (Macintosh Roman, also called [1,0])

In this case, the PDF file was using a custom font CustomSymbol that contained a (3, 0) cmap subtable, which PDF 1.4 doesn’t recognize.  Therefore, Acrobat X and other PDF/A validators correctly reported an error when checking for PDF/A-1b compliance (As PDF/A-1b is based upon PDF 1.4).

reference: (181779161/2714061)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 6.0/10 (3 votes cast)

LiveCycle Designer: Bad value ‘#f1′ of the ‘use’ attribute of ‘font’ element


When you are working with Designer to edit form you may see the following warning in the report palette:

"Bad value '#f1' of the 'use' attribute of 'font' element - Default will be used."


You may see this error if you delete the “Referenced Objects” node in the Designer hierarchy.

Referenced Objects refer to any repeating objects in the form, fonts, images etc… You can define an object and its properties in the <proto> node in the XML and then just call it many times using its ID through the “use” attribute.

If you delete the Referenced Objects object, the <proto> tag will be deleted, and so the object definitions along with it. The “use” attributes will not be mapped to any object definition and so will result in this warning.


Refer to the XFA 2.4 specification, where, on page 194 it describes how to define these objects in the proto node.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 1.0/10 (1 vote cast)

LiveCycle Forms ES: Select which fonts get embedded at render-time


If you would like to control which fonts should be embedded in the final PDF when rendered using LiveCycle Forms ES, then please follow the steps below.


This could be a common requirement if you are producing PDF documents for multiple environments:

  1. the internal environment, where the user’s systems have all of the fonts available already
  2. the external environment, where you would need the additional fonts to be embedded

At render-time, you know which environment is making the call, but do not know how to control the fonts which are getting embedded.


The XCI file, or XCI options string in FormsIVS, is what controls the render options used by Forms. To control what fonts are embedded, you must create your own custom XCI file, and pass that as a parameter to the renderPDFForm method, or as an option to FormsIVS. There are two options which you can use in the XCI file to control what fonts get embedded (alwaysEmbed), or what fonts do not get embedded (neverEmbed).

1. Copy the default pa.xci file and create a custom.xci file (for the purposes of this example, we will assume you create the custom.xci file on the root of the D drive)

2. Set the value for alwaysEmbed/neverEmbed as follows in the custom.xci file:


3. Call the renderPDFForm method setting the XCIURI property, or FormsIVS with the following parameter in the options String:


or on some platforms:


By editing the custom.xci file manually you will be able to generate PDF files controlling the fonts which are embedded. You could generate multiple XCI files for various environments and just call the respective XCI file to use for each document.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 9.0/10 (1 vote cast)