[
https://issues.apache.org/jira/browse/PDFBOX-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140346#comment-17140346
]
Tilman Hausherr commented on PDFBOX-4888:
-----------------------------------------
The first file has only one field, topmostSubform[0].Page1[0].f1_9[0] . The
other "fields" are annotations only.
But yes, that field isn't renamed. Maybe we make a difference because once this
is the field name, and once this is constructed from the hierarchy.
> PDFMergerUtility doesn't rename common fields
> ---------------------------------------------
>
> Key: PDFBOX-4888
> URL: https://issues.apache.org/jira/browse/PDFBOX-4888
> Project: PDFBox
> Issue Type: Bug
> Affects Versions: 2.0.20
> Reporter: Jief Knudsen
> Priority: Major
> Attachments: f1040sb test-joined.pdf, f1040sb test.pdf, f8938 (blank,
> readonly).pdf
>
>
> I am merging 2 pdfs. They have fields with the same name.
> I though PDFMergerUtility would rename these field, so when I open it, I
> still have the correct values in each field.
> I am using PDFMergerUtility, with *_PDFBOX_LEGACY_MODE_*
> I am merging "f1040sb test.pdf" and "f8938 (blank, readonly).pdf".
> One common field is, for example, "topmostSubform[0].Page1[0].f1_11[0]"
> Am I wrong thinking it should be renamed ?
>
> I tried the workaround to render each page as an image and add it to a
> destination pdf (not using PDFMergerUtility). Of course, it worked (no field
> anymore), but destination pdf is big.
> Should I rename fields myself before merging ?
> NOTE : when I try to attach files, I got : "Jira could not attach the file as
> there was a missing token. Please try attaching the file again."
> Files available at : https://we.tl/t-dJZlLjPqLt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
