You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by "Stefan Hegny (JIRA)" <ji...@apache.org> on 2016/07/07 11:18:10 UTC

[jira] [Created] (FOP-2621) ToUnicode missing for AdobeStandardEncodingFonts but present for FontSpecific

Stefan Hegny created FOP-2621:
---------------------------------

             Summary: ToUnicode missing for AdobeStandardEncodingFonts 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


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).

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. Will attach simple sample.

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
(v6.3.4#6332)