From dev-return-61157-archive-asf-public=cust-asf.ponee.io@pdfbox.apache.org Sat Feb 2 15:39:04 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 7A7C8180656 for ; Sat, 2 Feb 2019 16:39:03 +0100 (CET) Received: (qmail 64944 invoked by uid 500); 2 Feb 2019 15:39:02 -0000 Mailing-List: contact dev-help@pdfbox.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@pdfbox.apache.org Delivered-To: mailing list dev@pdfbox.apache.org Received: (qmail 64933 invoked by uid 99); 2 Feb 2019 15:39:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Feb 2019 15:39:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 1B807C2898 for ; Sat, 2 Feb 2019 15:39:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id NyCc9uEIP1zC for ; Sat, 2 Feb 2019 15:39:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 05F9C5F19D for ; Sat, 2 Feb 2019 15:39:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7A0C1E02ED for ; Sat, 2 Feb 2019 15:39:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 0DE50243E2 for ; Sat, 2 Feb 2019 15:39:00 +0000 (UTC) Date: Sat, 2 Feb 2019 15:39:00 +0000 (UTC) From: "Tilman Hausherr (JIRA)" To: dev@pdfbox.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (PDFBOX-4454) PDFmergerUtility is changing the names of form fields to dummyField#X when fields have the same name. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PDFBOX-4454?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D167= 59068#comment-16759068 ]=20 Tilman Hausherr commented on PDFBOX-4454: ----------------------------------------- Merging these is tricky because we can't have two fields with the same name= (if we do, one of the two would simply be ignored) and just because they h= ave the same name doesn't mean they're the same... what should be done if t= hey have different values, or different properties? Is the merged file still to be edited manually or by a computer? And if so,= why not create a file that has all needed, or are there too many combinati= ons? > PDFmergerUtility is changing the names of form fields to dummyField#X whe= n fields have the same name. > -------------------------------------------------------------------------= ---------------------------- > > Key: PDFBOX-4454 > URL: https://issues.apache.org/jira/browse/PDFBOX-4454 > Project: PDFBox > Issue Type: New Feature > Components: AcroForm > Affects Versions: 2.0.13 > Reporter: Seth Freeman > Priority: Critical > Labels: PDFMergerUtility > > =C2=A0 > The merger renaming form fields that have the same name is a feature that= should be optional. In my situation, I need all the fields to keep their p= re-merge names. > In my case, we are using 3 different medical forms that intentionally all= have fields with the same name. In Acrobat merging would set the fields ou= tput equal to each other. I'm working on a project to automate filling thes= e forms with information provided by the patient. Right now merging with PD= Fbox breaks this. > My current workaround is to just fill each form separately then combine t= hem, but this makes edits later down the line needlessly complex.=C2=A0 > The simplest solution would be to have options to maintain the names. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org For additional commands, e-mail: dev-help@pdfbox.apache.org