From #1356124: XFDF generation fails if PDF-field key contains an apostrophe:
However, I am 95% sure that there is no need for this code at all. The code converts an array with PDF-field keys containing periods into a multidimensional array for generation of nested field elements in the XFDF. I believe the @name of a field element can contain the original PDF-field key with periods and it will work the same way, no need for nested elements. I don't have a PDF like that which would allow me to test this. If anyone has or can make a test PDF, I will test and simplify the code if it works.
I can create a PDF like that with LiveCycle. If we change that logic we will want to test it.
Please email me a PDF with PDF-field keys containing periods and I will test.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | fillpdf_1393022_xfdf-D6.patch | 3.22 KB | liam morland |
| #1 | fillpdf_1393022_xfdf.patch | 1.66 KB | liam morland |
Comments
Comment #1
liam morlandHere is a patch implementing the simplified XFDF generation. This needs to be tested with a PDF which has field keys containing periods.
Comment #2
wizonesolutionsWorks for me with my LiveCycle test PDF, which has periods in it. Committed. Needs backport.
Comment #3
liam morlandD6 version attached. xfdf.inc files are now identical in D6 and D7.
Comment #4
liam morlandApply this patch after #1430390: Coding standards: remove whitespace.
Comment #5
wizonesolutionsComment #6
wizonesolutionsThanks! Committed in 6874d5a.