View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004218 | Scribus | public | 2006-09-05 23:02 | 2006-11-26 21:25 | |
| Reporter | arguile | Assigned To | fschmid | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | Opteron | OS | Linux | OS Version | 2.6.12 |
| Product Version | 1.3.3.3 | ||||
| Fixed in Version | 1.3.3.5cvs | ||||
| Summary | 0004218: Period '.' should not allowed in AcroForm field names? | ||||
| Description | According to the PDF 1.6 reference (Page 638) the T key in the field's dictionary holds a text string defining the fields 'partial name'. The 'fully qualified name' is built from the hierarchy of partial names. When referencing a field the deliminator between generations is a period ('.'). So the specification doesn't explicitly exclude it, but if it's used in Acrobat it creates a field hierarchy (fields with a Kids array in their dictionary) and the period is not present in the T attribute. And according to Implementation Note 115 "Beginning in Acrobat 3.0, partial field names cannot contain a period" (PDF 1.6 pg. 1023). Referencing a field in an AcroForm that has been declared in Scribus with a period in it also becomes problematic as instead of: foo.bar.field_name the alternate: foo.bar['field_name_with_._in_it'] has to be used. So, that's my interprettation of the standard. For the best compliance with existing tools I'd suggest that later version of Scribus also disallow periods in field names. P.S. A seperate feature request for being able to set up hierachies will be filed. | ||||
| Steps To Reproduce | 1. Create a new document (any size) 2. Create a form field with a period in it's name. 3. Export as PDF. You now have a PDF with a field who's T key contains the name including the period. | ||||
| Tags | No tags attached. | ||||
| Patch | |||||
|
|
Please move the . check into the annot.cpp form so this occurs when the user is changing the name. The way it is now if we had a field called a_frame_name and a.frame.name, then we would have a name conflict in the exported PDF. A name check should also be added into PDF export options (and not be optional so theres no need for preferences for this). |
|
|
Forgot to say, preflight checker needs this in case somehow one of these is imported, scripted or manually edited. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2006-09-05 23:02 | arguile | New Issue | |
| 2006-09-05 23:10 | cbradney | Status | new => assigned |
| 2006-09-05 23:10 | cbradney | Assigned To | => fschmid |
| 2006-09-06 09:00 | fschmid | Status | assigned => resolved |
| 2006-09-06 09:00 | fschmid | Fixed in Version | => 1.3.4cvs |
| 2006-09-06 09:00 | fschmid | Resolution | open => fixed |
| 2006-09-13 22:13 | cbradney | Status | resolved => feedback |
| 2006-09-13 22:13 | cbradney | Resolution | fixed => reopened |
| 2006-09-13 22:13 | cbradney | Note Added: 0012507 | |
| 2006-09-13 22:14 | cbradney | Note Added: 0012508 | |
| 2006-09-17 21:30 | cbradney | Relationship added | child of 0003964 |
| 2006-11-02 23:46 | cbradney | Relationship added | child of 0004439 |
| 2006-11-05 12:46 | fschmid | Status | feedback => resolved |
| 2006-11-05 12:46 | fschmid | Fixed in Version | 1.3.4cvs => 1.3.3.5cvs |
| 2006-11-05 12:46 | fschmid | Resolution | reopened => fixed |
| 2006-11-05 13:00 | mhanski | Relationship added | child of 0003831 |
| 2006-11-26 21:25 | cbradney | Status | resolved => closed |
