https://issues.apache.org/bugzilla/show_bug.cgi?id=53766
Priority: P2 Bug ID: 53766 Assignee: fop-dev@xmlgraphics.apache.org Summary: [PATCH] Removed the undefined PDF StandardEncoding type from FOP Severity: normal Classification: Unclassified OS: Linux Reporter: rme...@hotmail.co.uk Hardware: PC Status: NEW Version: all Component: pdf Product: Fop Created attachment 29266 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29266&action=edit Patch to remove the PDF StandardEncoding type A support case recently highlighted the issue where PDF's generated using FOP fallback to the use of a "StandardEncoding" type. The reason why this was brought to our attention was because it was failing a syntax check in preflight Adobe Acrobat Pro. The error was an undefined key value on either the /Encoding or /BaseEncoding in the font definition. That undefined value was FOP's use of the StandardEncoding type. After studying the PDF specification third edition, I first found the following references with regard to valid encoding types: "For each named character, an octal character code is given in four different encodings: StandardEncoding, MacRomanEncoding, WinAnsiEncoding, and PDFDocEncoding" However, when researching the StandardEncoding type further, the following is stated in Table D.1: "PDF does not have a predefined encoding named StandardEncoding. However, it is useful to describe this encoding, since a font’s built-in encoding can be used as the base encoding from which differences are specified in an encoding dictionary." Essentially then, FOP's use of StandardEncoding with a definition is not valid. This patch resolves this issue by removing the /Encoding and /BaseEncoding tags when it is set to StandardEncoding as if none is specified, it will default to the default encoding type for which this tag represents. This change resolves the preflight errors. -- You are receiving this mail because: You are the assignee for the bug.