[
https://issues.apache.org/jira/browse/FOP-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850250#comment-13850250
]
Sami Sundell commented on FOP-2134:
-----------------------------------
I had the same problems with PDF/A, and tracked them down to XGC-44
In short, XGC writes simple (string) values if there's only one value for a
metadata property, whereas Adobe Acrobat and other tools always expect rdf:Bag
or rdf:Seq. I added a patch into the XGC issue which forces the array creation.
Regarding fonts, adding {{encoding-mode="single-byte"}} into FOP font
configuration seemed to fix this particular issue. I'm not familiar with the
inner workings of FOP/PDF font handling, though, so it might introduce others,
maybe depending on the character set you use.
> PDF/A-1b compliance is broken in 1.1RC1
> ---------------------------------------
>
> Key: FOP-2134
> URL: https://issues.apache.org/jira/browse/FOP-2134
> Project: Fop
> Issue Type: Bug
> Components: pdf
> Affects Versions: trunk
> Environment: Operating System: All
> Platform: PC
> Reporter: oliver.moehrke
> Attachments: pdfa1b_issue_20120921.zip, pdfa1b_issue_20120927.zip
>
>
> While the patch for FOP-1940 fixed a PDF/A-1b compliance issue some time ago,
> the actual v1.1RC1 breaks the PDF/A-1b compliance again.
> Adobe Preflight 9.2.0 finds two new issues, if I use FOP v1.1RC1 instead of
> the patched v1.0:
> - CIDSet in subset font is incomplete (5 matches on 1 page)
> - XMP property not predefined and no extension schema
> I created a ready-to-run test-FO-file with a suitable configuration in the
> attachment for v1.0, v1.0HF1 and v1.1RC1. I also added the resulting
> PDF-files and the (german) reports of Adobe Preflight 9.2.0.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
