Uploaded image for project: 'FOP'
  1. FOP
  2. FOP-2621

ToUnicode missing for AdobeStandardEncoding Fonts but present for FontSpecific

    XMLWordPrintableJSON

    Details

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

      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

        Attachments

        1. buggele1.tar.gz
          332 kB
          Stefan Hegny

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              shyrodgau Stefan Hegny
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: