[FOP-2621] ToUnicode missing for AdobeStandardEncoding Fonts but present for FontSpecific

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.1
• Fix Version/s: 2.2
• Component/s: renderer/pdf
• Labels: encoding pdf/a

Environment

Linux
java version "1.8.0_73"
Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)
java version "1.7.0_95"
OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1)
OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)

• Assignee: Unassigned
• Reporter: Stefan Hegny
• Created: 07/Jul/16 11:17
• Updated: 18/Apr/17 09:38
• Resolved: 18/Apr/17 09:38

Description

Generating PDF/A-1a gives non-validating pdf due to missing ToUnicode tables for embedded AdobeStandardEncoding Fonts (e.g. Nimbus Roman 9L from ghostscript, but also commercial T1 fonts). Validation here refers to the online validator at pdf-tools.com .

Fonts embedded with FontSpecific Encoding produce ToUnicode tables.

Using modified .afm files where AdobeStandardEncoding is manually replaced by FontSpecific will produce the ToUnicode tables for these fonts too and then the resulting PDF will validate. The Files look identical to those non-validating due to AdobeStandardEncoding also for more complex documents.

fop-2.1/fop -c working.xconf -a -pdfprofile 'PDF/A-1a' -pdf test_works.pdf -fo test_0.fo

fop-2.1/fop -c notworking.xconf -a -pdfprofile 'PDF/A-1a' -pdf test_notvalid.pdf -fo test_0.fo