[
https://issues.apache.org/jira/browse/PDFBOX-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244398#comment-15244398
]
Tilman Hausherr commented on PDFBOX-3317:
-----------------------------------------
The solution uses the OutputConditionIdentifier as a unique key to avoid
duplicate outputIntents being added, except when the OutputConditionIdentifier
is missing or when it is named "Custom".
> Merged PDF/A files no longer valid PDF/A
> ----------------------------------------
>
> Key: PDFBOX-3317
> URL: https://issues.apache.org/jira/browse/PDFBOX-3317
> Project: PDFBox
> Issue Type: Bug
> Components: Utilities
> Affects Versions: 2.0.0, 2.0.1, 2.1.0
> Reporter: Tilman Hausherr
> Assignee: Tilman Hausherr
> Fix For: 2.0.1, 2.1.0
>
>
> From Alexander K. on the mailing list:
> {quote}
> Situation: We have a bunch of PDF/A-1b compliant documents from a 3rd
> party system and merge them into a new document. The end result is not
> PDF/A-1b compliant though.
> {quote}
> The cause is that the outputIntents are ignored. But if all are copied, the
> file isn't valid either because only one outputIntent is allowed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
