Stefan Hegny commented on FOP-2621:

Seems the issue can *not* be reproduced using the verapdf validator even with 
fop 2.1 nor with fop 2.2.

> ToUnicode missing for AdobeStandardEncoding Fonts but present for FontSpecific
> ------------------------------------------------------------------------------
>                 Key: FOP-2621
>                 URL: https://issues.apache.org/jira/browse/FOP-2621
>             Project: FOP
>          Issue Type: Bug
>          Components: renderer/pdf
>    Affects Versions: 2.1
>         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)
>            Reporter: Stefan Hegny
>            Priority: Minor
>              Labels: encoding, pdf/a
>         Attachments: buggele1.tar.gz
> 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

This message was sent by Atlassian JIRA

Reply via email to