[
https://issues.apache.org/jira/browse/PDFBOX-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097184#comment-14097184
]
Tilman Hausherr commented on PDFBOX-1511:
-----------------------------------------
What we need now is a test. [~msahyoun] can you create the two files I
mentioned? Even one is enough, I could edit it to create the second i.e. by
shuffling the names. The file must have global resources. Either with two
different looking fonts or with different sized images. I can create the test,
the simplest would be to render the merged file, and to check that its two
pages are identical. (And check that they are not identical with the "bad"
code). This would be an insurance against incorrect changes in the future.
> pdfMerger App produces Garbage
> ------------------------------
>
> Key: PDFBOX-1511
> URL: https://issues.apache.org/jira/browse/PDFBOX-1511
> Project: PDFBox
> Issue Type: Bug
> Components: Utilities
> Affects Versions: 1.7.1
> Environment: Win XP; Windows Server 2008 R2; java version "1.6.0_21",
> Reporter: Michael Huber
> Fix For: 1.8.7, 2.0.0
>
> Attachments: 078117u1.pdf, 078117u2.pdf, 078118.pdf, 1.pdf, 2.pdf,
> PDFMergerUtility.java, PDFMergerUtility.java.diff, PdfRenderer.java,
> targetPdfMergeJava.pdf, targetPdfMergeUtilityApp.pdf
>
>
> pdfbox Utility pdfMerger produces a merged document containing garbage. All
> merged pdf files are contained but Strings are destroyed.
> The source pdf files are created with graphviz and are readable without error
> or disturbance both with Acrobat X and pdfbox pdfDebug Utility.
> Another astounding thing is that a handcoded merger using pdfMergerUtility
> class works fine when run within Eclipse Juno and creates same garbage when
> run from cmd line (pls. see attached source PdfRenderer.java)
> I checked everything that comes in mind to find the differences, e.g. Java
> version, encoding/codepage issues, memory settings, found nothing.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
