[
https://issues.apache.org/jira/browse/PDFBOX-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16121164#comment-16121164
]
Maruan Sahyoun commented on PDFBOX-3891:
----------------------------------------
as already noted the /Fields entry for /AcroForm is empty. so from the current
code there is no AcroForm to be merged. But there is still an issue as the
Annotations for the pages do contain the entries for the field. Thus one would
expect that when merging the PDFs the annotations for the pages are merged too
and as a result the annotations on the merged pages should be visible. Looking
at the merged pdf this is the case but Adobe Reader either shows the annotation
for a page of the first document or for the second document. E.g. Page 1 of the
merged document has annotations (fields) shown in Adobe Reader where page 2
doesn't. Page 28 (the first page of the source document) doesn't have fields
shown where page 29 does.
Looking at the document in OSX Preview will show the fields for all pages as
does PDF.js.
So the question is what's causing Adobe Reader to not view the content.
>From a high level perspective the merge process is OK so there must be
>something in the details.
I'll do some merge tests using some other libs and Adobe tools to compare the
results.
> Missing data if document is merged with itself
> ----------------------------------------------
>
> Key: PDFBOX-3891
> URL: https://issues.apache.org/jira/browse/PDFBOX-3891
> Project: PDFBox
> Issue Type: Bug
> Components: AcroForm, Utilities
> Affects Versions: 2.0.7
> Reporter: Haiko Strotbek
> Attachments: MergeTest.java, merge-test-merged.pdf, merge-test.pdf
>
>
> When using PDFMergerUtility to merge the attached PDF twice into one document
> there may be data missing.
> To be more specific: In this case the data on page 1 looks fine, but page 28
> is empty. My expectation is that page 28 is identical to page 1 (the document
> has 27 pages).
> Of course that's not a common use case. But I can reproduce this behaviour
> with other documents which are not identical, but similar.
> I think this might be related to PDFBOX-3111 and PDFBOX-3218.
> What is the trigger for this and is there a workaround?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
