[
https://issues.apache.org/jira/browse/PDFBOX-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095353#comment-14095353
]
Andreas Lehmkühler edited comment on PDFBOX-1511 at 8/13/14 11:08 AM:
----------------------------------------------------------------------
Identically named resources are problematic if 2 or more of the pdfs to be
merged are using global resources and if the merger merges the page related
resources and the global resources separately as it did befroe the patch.
The proposed patch -merges- doesn't use global resources by using
"findResources()" instead of "getResources()" -the global and the page specific
resources _before_ adding them to the page itself,- if page specific resources
are present, so that there aren't any duplicted names anymore. -I don't know if
that was intended in the first place but it solves the problem-
OTOH pdfs using global resources -will grow after merging as all resources are
multiplied.- still have that issue. -But AFAIKT global resources aren't used
that often.-
was (Author: lehmi):
Identically named resources are problematic if 2 or more of the pdfs to be
merged are using global resources and if the merger merges the page related
resources and the global resources separately as it did befroe the patch.
The proposed patch -merges- doesn't use global resources by using
"findResources()" instead of "getResources()" -the global and the page specific
resources _before_ adding them to the page itself,- if page specific resources
are present, so that there aren't any duplicted names anymore. -I don't know if
that was intended in the first place but it solves the problem :-) -
OTOH pdfs using global resources -will grow after merging as all resources are
multiplied.- still have that issue. -But AFAIKT global resources aren't used
that often.-
> 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: 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)
