ActivePDF

Bug

Description

Resolution

12180

File specific: When these EPS files were converted, the output PDF had blank pages.

General updates to the code base resolved this issue.

12204

File specific: When this PostScript® file that included text with text shadows was converted, the text shadows in the output PDF were not as sharp as expected.

A change to the image resolution (to 300 ppi) resolved this issue.

12205

File specific: When this PostScript file was converted, some objects in the output PDF did not line up as expected.

General updates to the code base resolved this issue.

12206

File specific: When this PostScript file containing a logo was converted, the logo did not display as expected in the output file.

General changes to the default resolution resolved this issue.

12207

When a backward slash ("\") was added to the beginning of an output filename, after conversion the output PDF was placed in the root of the C drive ("c:\").

Changes to the code related to how filepaths are handled resolved this issue.

12139

When using ConvertPSToPDF to convert a PostScript file that contained dimensions for a page size that was smaller than letter size, the smaller page size dimensions were ignored, and the output PDF was letter sized.

You can now edit the PostScriptProfiles.xml file to cause the conversion process to respect any non-standard page sizes found in a PostScript source file.

See the KB article: Enabling Non-Standard Page Sizes for PostScript Conversions for full instructions.

13373
13374

File specific: When the PostScript files were converted, most of the data was missing from the output PDF.

Changes to the code related to how page dimensions are handled during conversions resolved these issues.

File specific: After this PostScript file was converted, when the output PDF was opened in a reader, text was overlapping, data was missing, and an error message displayed.

General updates to the code base resolved these issues.

13514

File specific: When this PostScript file that includes a certain combination of width, height, and embedded font settings was converted, the output PDF displayed an "invalid output" message and the file did open.

General updates to the code base resolved these issues.

14311

File specific: After this PostScript file was converted, when the output PDF was opened in a reader, data was missing and an error message displayed.

General updates to the code base resolved these issues.

Bug

Description

Solution

2531

File and font specific: When this PostScript™ file using CID- (character ID) keyed CJK fonts was converted, the output had garbled characters.

CID map files provide the encoding for CID-keyed CJK fonts.

Placing a CID map file for the CJK font you are using into this folder may solve the issue of garbled characters:

[Common Application Data]\ActivePDF\Include.

Server will pick up the CID map file at runtime and determine the proper font substitution.