[
https://issues.apache.org/jira/browse/PDFBOX-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627542#comment-13627542
]
Christian Connert commented on PDFBOX-1533:
-------------------------------------------
Thanks for the update. I tried both approches without any success. When I
update to PDFBox 1.8.0 the merged pdf is invalid and cannot be opened by
acrobat anymore (also in combination with the second tip). The second approach
doesn't help either. Still got the same behaviour. I have to check if our
customer might be able to supply an test pdf without any private data to
attache to this issue.
> When merging certain PDF's several odd looking empty pages occure in the
> result
> -------------------------------------------------------------------------------
>
> Key: PDFBOX-1533
> URL: https://issues.apache.org/jira/browse/PDFBOX-1533
> Project: PDFBox
> Issue Type: Bug
> Components: Utilities
> Affects Versions: 1.7.1
> Reporter: Christian Connert
>
> Unfortunately I cannot attach a input file for this case as it contains
> confidential customer data, but I'll try to explain the problem in depth so
> you hopefully are able to track it down.
> When we merg certain PDF's with the PDFMergerUtility the result contains
> serveral empty pages at the end of the document. It seems like that only
> certain pdf versions are effected (i.p.: 1.5 (Acrobat 6.x)).
> I tracked the problem down to the the following part in the appendDocument
> method of the PDFMergerUtility:
> //finally append the pages
> List<PDPage> pages = srcCatalog.getAllPages();
> Iterator<PDPage> pageIter = pages.iterator();
> while( pageIter.hasNext() )
> {
> PDPage page = pageIter.next();
> PDPage newPage =
> new PDPage( (COSDictionary)cloner.cloneForNewDocument(
> page.getCOSDictionary() ) );
> newPage.setCropBox( page.findCropBox() );
> newPage.setMediaBox( page.findMediaBox() );
> newPage.setRotation( page.findRotation() );
> destination.addPage( newPage );
> }
> The problem is that call to srcCatalog.getAllPages(); returns for expamle 6
> PDPage objects, but for the same input document, the call to
> source.getNumberOfPages() returns only 2. Thus we add 4 odd empty pages to
> the result document.
> I hope this description is good enought to figure out the problem. Don't
> hesitate to ask for further details.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
