Posts tagged "Postscript"

LiveCycle ES2: barcode visible in PDF file converted to Postscript

Issue

When you use the ConvertPDFService toPS2() operation to convert PDF documents to Postscript in LiveCycle ES2, barcodes are appearing in the PostScript file which were hidden in the original PDF. This issue can occur especially if you used the legacyToSimplePSFlag to convert static documents directly, without flattening them first.

Solution

This issue is a bug in LiveCycle ES2 SP1 and SP2 and has been resolved in a patch.  Contact Enterprise Support if you require this patch for ES2 SP1 or SP2.  Adobe plans to fix this issue in the ES2 SP3, later versions.

You need to set GenerateServerAppearances=true to in the Form render settings when rendering the PDF forms and use the legacyToSimplePSFlag in the PSOptionsSpec for the Postscript conversion to work.

Additional information

 The problem only occurs for pre-generated PDF files which are then merged with XML data on the server side.  The document flow is as follows:

  1. XDP template gets rendered to PDF.
  2. The PDF can then be merged with data on the server, filled and signed by the user.
  3. The PDF is converted to PostScript.

In the input PDF, the barcode value is empty and hidden as expected. When the PDF is converted to Postscript with ES2 SP1, the barcode gets assigned a default value of “123456789…” Therefore, the barcode becomes visible on the resulting PostScript file.  The Postscript file from LC7 works correctly and the barcode remains hidden.

reference: (181754483/2702011)

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

LiveCycle ES2: Field spacing changes after conversion to Postscript with toPS2()

Issue

When you use the toPS2() method in LiveCycle ES2 to convert PDF files to PostScript, the spacing between fields is incorrect in the resulting PostScript files. In the examples below there are many differences,  for example the space following the last set of “nnn” characters is larger in the PostScript file than in the PDF file.

PDF file:

PostScript file:

Solution

This issue has been addressed in LiveCycle ES2 SP1 and later versions.

reference: (181434404/2553226)

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

LiveCycle ES2: text-shifts after conversion to Postscript using toPS2()

Issue

When you use the toPS2() method in LiveCycle ES2 to convert PDF files to PostScript, some text-shifting occurs in the resulting Postscript file.

Here is an example where the text is shifted upwards and starts to overlap the border:

PDF file:

PostScript file:

Reason

A bug in how the server handles the field placement during conversion causes this issue, and can lead to data-loss in extreme circumstances.

Solution

This issue has been addressed in LiveCycle ES2 SP1 and later versions.

reference: (181423968/2552257)

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

LiveCycle ES2: Checkbox marks changed after conversion to Postscript using toPS2()

Issue

When you use the toPS2() method from LiveCycle ES2 to convert PDF files to PostScript, checkbox marks are rendered differently in the resulting PostScript. For example, the checkbox marks are larger in the PostScript file than in the PDF file.

PDF file:

PostScript file:

Solution

This issue has been addressed in LiveCycle ES2 SP1 and later versions.

Additional information

A bug in the rendering functionality during the PostScript conversion causes this error. This problem causes issues for customers who convert legally binding documents, and must guarantee that they haven’t changed since they were completed or signed.

reference: (181435838/2571942)

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