[PDFBOX-3317] Merged PDF/A files no longer valid PDF/A

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0, 2.0.1, 3.0.0 PDFBox
• Fix Version/s: 2.0.1, 3.0.0 PDFBox
• Component/s: Utilities
• Assignee: Tilman Hausherr
• Reporter: Tilman Hausherr
• Created: 16/Apr/16 20:41
• Updated: 05/Jan/18 07:04
• Resolved: 19/Apr/16 16:22

Description

From Alexander K. on the mailing list:

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.

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.

Issue Links

• is related to: PDFBOX-4051 Different DestOutputProfiles in OutputIntentArray after PDFMergerUtility.Merge leads to non-conformity