[
https://issues.apache.org/jira/browse/FOP-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17475160#comment-17475160
]
Juhani Laiho commented on FOP-2910:
-----------------------------------
Is it possible to consider leaving out the CIDSets when targeting PDF/A-2 or
PDF/A-3 compliance as described in the answers to [this Stack Overflow
question|https://stackoverflow.com/questions/31209981/pdfbox-pdf-a-1a-to-pdf-a-3a]?
Maybe make omitting the CIDSets user-configurable?
This is the only issue left according to [veraPDF|https://verapdf.org/]
validation when attempting to generate valid PDF/A-2s with FOP (now that
FOP-3006 will be apparently fixed in an upcoming release).
> 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
> Priority: Major
> 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)
