Issue 103932 - duplicated fields in PDF Export
Summary: duplicated fields in PDF Export
Status: VERIFIED FIXED
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 3.1
Hardware: All All
: P3 Trivial with 1 vote (vote)
Target Milestone: OOo 3.3
Assignee: h.ilter
QA Contact: issues@gsl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-31 12:04 UTC by amoroder2
Modified: 2009-11-02 10:34 UTC (History)
1 user (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
document containing two controls with the same name (8.17 KB, application/vnd.oasis.opendocument.text)
2009-10-21 15:01 UTC, philipp.lohmann
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description amoroder2 2009-07-31 12:04:02 UTC
Hello,

with writer we create forms and export them as PDF to, We then merge them with
xfdf files at printing. In certain situation it is necessary to have the same
field twice in a form or on different page. This does not work with ooo because
when the pdf is created it attaches a _x (where x is a number generated by ooo)
to the fieldname. When acrobat reader merges the xfdf with the pdf this fields
remain empty.

It should be possible to select as option to export fields that have the same
name without the extension.

Thanks
Andreas
Comment 1 philipp.lohmann 2009-07-31 12:51:11 UTC
pl->fs: this would require non-unique field names; don't know if that is
feasible in OOo.
Comment 2 Frank Schönheit 2009-08-10 12:35:42 UTC
I think this can indeed be done with an option only. The PDF spec allows for
duplicate fully qualified names only in certain situations, which have no
canonical match in a ODF document (its form controls, respectively). So, it is
up to the document creator to decide whether names should be made unique.

fs->pl: Sounds like yet another option to the PDF export dialog to me: "Make
form control names unique (recommended)", or something like this.
Comment 3 philipp.lohmann 2009-08-25 14:16:23 UTC
If we make this configurable, it will have to wait for 3.3. However I also think
changing the behavior unconditionally might be a bad idea.
Comment 4 philipp.lohmann 2009-10-21 14:55:06 UTC
pl->fs: I made the necessary changes in the pdf export filter and vcl in CWS
vcl106; only to find that describePDFControl in toolkit already comes up with
unique names. So please find out who makes those names unique. I'll attach a
test doc with two controls having the same name as shown in the UI.
Comment 5 philipp.lohmann 2009-10-21 15:01:24 UTC
Created attachment 65512 [details]
document containing two controls with the same name
Comment 6 Frank Schönheit 2009-10-23 11:27:48 UTC
fs->pl: as seen: PDFExtOutDevData::CreateControl is the place where there's
still some "make control names unique" wizardry is applied ...
Comment 7 philipp.lohmann 2009-10-23 11:42:15 UTC
Ah, it seems I'm blind and dumb again ... thanks. So now in CWS vcl106 we you
can emit duplicate field names; the default is still not to.
Comment 8 philipp.lohmann 2009-10-26 12:14:20 UTC
please verify in CWS vcl106
Comment 9 h.ilter 2009-11-02 10:34:15 UTC
Verified with cws vcl106 = OK
In default (disabled) mode, the controls will be named as (ControlA) and
(ControlA_2)
In enabled mode, both controls will be named as (ControlA)