[
https://issues.apache.org/jira/browse/FOP-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17476182#comment-17476182
]
Juhani Laiho commented on FOP-2910:
-----------------------------------
[~ssteiner]
I tested this by generating a PDF/A-2 (that is non-compliant when using FOP 2.6
according to veraPDF) using the FOP all in one jar build here (instead of the
FOP 2.6 JAR):
[https://builds.apache.org/job/XMLGraphics/job/xmlgraphics-fop/69/]
...and the PDF is now valid according to both veraPDF 1.18 and 1.20RC9.
Thank you very much!
> Create valid PDF/A part 2 or 3 with font subset
> -----------------------------------------------
>
> Key: FOP-2910
> URL: https://issues.apache.org/jira/browse/FOP-2910
> Project: FOP
> Issue Type: Improvement
> Components: renderer/pdf
> Affects Versions: 2.4
> Environment: OS: Windows 10
> Java: 1.8
> Reporter: Roberto Benedetti
> Assignee: Simon Steiner
> Priority: Major
> Fix For: trunk
>
> Attachments: otf.zip, samples.zip
>
>
> When creating PDF/A-2a or PDF/A-3a with font embedding mode "subset" the
> resulting PDF in not valid according to veraPDF which reports:
> ??Specification: ISO 19005-3:2012, Clause: 6.2.11.4, Test number: 4. If the
> FontDescriptor dictionary of an embedded CID font contains a CIDSet stream,
> then it shall identify all CIDs which are present in the font program,
> regardless of whether a CID in the font is referenced or used by the PDF or
> not.??
> Embedding the complete font seems to solve the validation error but resulting
> files are very large.
> When exporting files as PDF/A from Microsoft Word the PDF is valid and it
> only contains a subset of the font.
> The only difference I noticed is that Word does not create a CIDSet.
> File [^samples.zip] contains two PDF/A-3a created by Word and the files used
> to create the same PDFs with FOP.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
