Archive for August, 2009

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

Issue

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.

Reason

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.

Solution

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:

<fontInfo>
<alwaysEmbed>[fontName1],[fontName2]</alwaysEmbed>
...
</fontInfo>

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

&XCIURI=file://D/custom.xci

or on some platforms:

&XCIURI=D/custom.xci

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)

Acrobat/Reader: “Too few operands” error printing a PDF

Issue

 If you are trying to print a PDF with Reader/Acrobat you may receive the error message “Too few operands”.

Reason

 You may need to strip down the original XDP file in Designer object-by-object, re-generate, and try to print the PDF to find the offending object. Drop-down list boxes that contain a blank entry in their lists has been known to cause this issue in previous versions.

Once you identify which object is causing the problem you should analyze this object and all related script to isolate the root cause of the issue.

reference: (1-19885739)

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

LiveCycle 7: “Directory Exception javax.servlet.jsp.JspException” accessing webservice portal

Issue

When you try to access the web service portal in JBoss (http://localhost:8080/services/) using LiveCycle 7, you may receive the following error:

Web Service Directory Services
Directory Exception javax.servlet.jsp.JspException: 
An error occurred while evaluating custom action attribute "items" with value "${directoryBean.deployedServices}": 
An error occurred while getting property "deployedServices" from an instance of 
class com.adobe.workflow.service.WorkflowServiceDirectoryBean (java.lang.NullPointerException)

Solution

 Add the following lines to the service XML file: [appserver root]/server/all/conf/jboss-service.xml:

_____________________________________

<-- Isolate all ears in their own classloader space -->
<attribute name="Isolated">true</attribute>
<-- Enforce call by value to all remote interfaces -->
<attribute name="CallByValue">true</attribute>

_____________________________________

reference: (180009712)

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

Acrobat/Reader: how to enable Javascript debugger in PDF forms

When you use Javascript in PDF forms, you can enable the Javascript debugger to be able to analyze the Javascript output in Acrobat or Designer.

Use the following approaches to enable Javascript debugging using Acrobat or Designer:

  • Use message box output to display dialog boxes with Javascript values (using the xfa.host.messagebox method).
  • Use the Javascript Debugger console in Acrobat. Open it by pressing Ctrl+J or select
    Edit > Preferences > Javascript > Javascript Debugger > Enable Javascript Debugger
    Restart Acrobat to view the Debugger console when using the Preferences option.
  • From Designer, save the form as PDF, open it in Acrobat, and press CTRL+J to open the debugger.
  • Launch Acrobat in the background, open the form in Designer, and goto PDF Preview. This approach uses the Acrobat plug-in, from where pressing Ctrl+J calls up the Javascript debugger.

To execute Javascript expressions directly in the console window, enter the statement and highlight the entire statement using the cursor. (Optionally, highlight multiple lines to execute multiple lines of Javascript code.) Press Ctrl+Enter.

reference: (180009803)

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

Acrobat/Reader: how to disable the Setup Files folder during installation

When Reader or Acrobat is installed, it creates a Setup Files folder:

  • Reader: C:\Program Files\Adobe\Reader 9.0\Setup Files\…
  • Acrobat: C:\Program Files\Adobe\Acrobat 9.0\Setup Files\…

This folder is used as an installer cache containing the actual installer file. The installer file is used to repair the Reader or Acrobat installation. However, some companies keep the installer available on a network share, and therefore do not want the installer cache created, as it takes up space.

You can disable this folder during installation by using the Adobe Customization wizard to transform the standard MSI installer file.  Disable the option “Enable Caching of installer files on local hard drive” under Installation Options.

To download and get more information on the Customization wizard, visit this link:

http://www.adobe.com/devnet/acrobat/enterprise_deployment.html

reference: (181025487)

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

Acrobat/Reader 8+: how to disable tabbing for read-only fields

Issue

If you have upgraded from Adobe Reader 7 to a later version and your forms contain read-only fields, you may have noticed that you can now tab into those fields in Reader 8+.  This was not possible in Reader 7 and earlier.

Solution

As a workaround, change the access property value for the fields you want to remove from the tabbing order from “readOnly” to “protected” in your XDP forms. Fields marked as “protected” do not participate in the tabbing order.

Alternately, write a script to change the access property from “readOnly” to “protected” in your XDP XML source code.

Additional Information

The tabbing feature has been documented for read-only fields since Designer 7.1 but has only been enforced in Acrobat/Reader since version 8. The necessity for tabbing into read-only fields comes from the Accessibility standards. Screen readers must be able to read the read only fields on the page, and screen readers work off the tabbing order.

This is the correct behaviour for read-only fields.

The “protected” option is not available in Designer 7.1 but is available in later versions. If you require this option in Designer 7.1, contact Adobe support to request a patch for Designer (you need a valid M&S contract to request this patch).

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