[
https://issues.apache.org/jira/browse/PDFBOX-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764202#comment-16764202
]
Tilman Hausherr commented on PDFBOX-3111:
-----------------------------------------
Glad to read the good news.
Re new public API - can't tell any opinion without seeing what it is about.
There's a lot going on in merging and once we expose some new API we can't
change it. I've noticed sometimes (although I can't bring up examples) that as
soon there's something new in PDFBox or something suddenly works, that people
use it (even if there's no clear announcement) and come up with exotic new
requests that we hadn't thought about. But yes it would be an advantage if
there's a single merge method that something useful by default.
> Replicate Acrobat behavior when merging PDFs with interactive forms
> -------------------------------------------------------------------
>
> Key: PDFBOX-3111
> URL: https://issues.apache.org/jira/browse/PDFBOX-3111
> Project: PDFBox
> Issue Type: New Feature
> Components: AcroForm
> Affects Versions: 1.8.10, 2.0.0
> Reporter: Maruan Sahyoun
> Assignee: Maruan Sahyoun
> Priority: Major
> Fix For: 2.0.14, 3.0.0 PDFBox
>
> Attachments: proof.pdf
>
>
> When PDFs containing interactive forms are merged using Acrobat, fields with
> the same name are merged into one. That's different to the current behavior
> of PDFBox which renames to be merged fields so they have a unique name (see
> PDFBOX-3094).
> In addition Acrobat supports merging documents with interactive forms into
> collections when keeping the existing (duplicate) fields is required.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
