[ https://issues.apache.org/jira/browse/PDFBOX-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073371#comment-14073371 ]
Tilman Hausherr commented on PDFBOX-1511: ----------------------------------------- Thanks... what we'd also need, would be a test that fails with the old version and succeeds with the new one: - two files, either created by somebody who has filed a CLA, or with no copyright (e.g. government files) - a java test, i.e. not just "human looking at it" but some java call that can find whether two identically named resources are different. > 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 > Attachments: 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)