[sw-issues] [Issue 82785] PDF: AcroForm fieldnames n ot correct, "." --> #2E

2010-03-05 Thread hi
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=82785


User hi changed the following:

What|Old value |New value

  Status|RESOLVED  |VERIFIED





--- Additional comments from h...@openoffice.org Fri Mar  5 12:10:46 + 
2010 ---
Verified with cws vcl109 = OK
The annotation is correct now

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org
For additional commands, e-mail: issues-h...@sw.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[sw-issues] [Issue 82785] PDF: AcroForm fieldnames n ot correct, "." --> #2E

2010-02-19 Thread pl
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=82785


User pl changed the following:

What|Old value |New value

 Assigned to|pl|hi





--- Additional comments from p...@openoffice.org Fri Feb 19 14:17:59 + 
2010 ---
please verify in CWS vcl109

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org
For additional commands, e-mail: issues-h...@sw.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[sw-issues] [Issue 82785] PDF: AcroForm fieldnames n ot correct, "." --> #2E

2010-02-18 Thread pl
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=82785


User pl changed the following:

What|Old value |New value

  Status|NEW   |RESOLVED

  Resolution|  |FIXED

Target milestone|OOo 3.x   |OOo 3.3





--- Additional comments from p...@openoffice.org Thu Feb 18 13:33:16 + 
2010 ---
fixed in CWS vcl109: full qualified names (containing dots) will be output as a
field hierarchy now. This has the following caveats:

- actual controls need to be terminal fields - this will be enforced by cutting
field hierarchy as long as names are unique.
Example: you have a button foo.bar and a button foo.bar.baz. This is valid in
OOo, but not in PDF; this will result in two PDF buttons foo.bar and foo.baz.

- field names need to be unique unless explicitly allowed in OOo's PDF export
UI; per default two same named terminal fields will be renamed
Example: two buttons foo.bar will result in one PDF button foo.bar and one 
foo.bar_2

Also changed in CWS vcl109: spaces in partial field names are not encoded as #20
anymore (since the lapo_luchini wanted that).

What remains is the encoding of Unicode characters larger than 126 as escaped
UTF8; this should be changed if and when we switch to PDF-1.5 or later and will
be tracked in issue 109404

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org
For additional commands, e-mail: issues-h...@sw.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[sw-issues] [Issue 82785] PDF: AcroForm fieldnames n ot correct, "." --> #2E

2010-02-17 Thread pl
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=82785


User pl changed the following:

What|Old value |New value

  CC|'kpalagin,lapo_luchini'   |'kpalagin,lapo_luchini,sve
|  |nkoelsch'





--- Additional comments from p...@openoffice.org Wed Feb 17 16:27:53 + 
2010 ---
regarding the '.' issue: if you set a field name containing dots acrobat seems
to silently insert parent fields so that the constructed fully qualified name
results in the exepcted result. So naming a widget "sender.person" would result
in two fields "sender" and "person", person being a child of sender.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org
For additional commands, e-mail: issues-h...@sw.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[sw-issues] [Issue 82785] PDF: AcroForm fieldnames n ot correct, "." --> #2E

2010-02-17 Thread pl
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=82785





--- Additional comments from p...@openoffice.org Wed Feb 17 16:00:57 + 
2010 ---
*** Issue 109329 has been marked as a duplicate of this issue. ***

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org
For additional commands, e-mail: issues-h...@sw.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[sw-issues] [Issue 82785] PDF: AcroForm fieldnames n ot correct, "." --> #2E

2009-02-12 Thread hi
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=82785


User hi changed the following:

What|Old value |New value

 Assigned to|hi|pl

  Ever confirmed|  |1

  Status|UNCONFIRMED   |NEW

  Issue type|DEFECT|ENHANCEMENT

  OS/Version|Linux |All

Target milestone|---   |OOo 3.x

 Version|OOo 2.3   |OOo 3.0





--- Additional comments from h...@openoffice.org Thu Feb 12 10:06:47 + 
2009 ---
@PL: Anytime we should measure up to a newer PDF-Reference.
Therefore Issue type changed to Enhancement.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org
For additional commands, e-mail: issues-h...@sw.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[sw-issues] [Issue 82785] PDF: AcroForm fieldnames n ot correct, "." --> #2E

2009-02-11 Thread lapo_luchini
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=82785





--- Additional comments from lapo_luch...@openoffice.org Wed Feb 11 
16:19:15 + 2009 ---
Document version 1.4 is quite old, in PDF Reference 1.7 I see:
116. Beginning in Acrobat 3.0, partial field names cannot contain a period.
117. Acrobat 6.0 and later support Unicode encoding of field names. Versions
earlier than Acrobat 6.0 do not support Unicode encoding of field names.

So the period is really forbidden (and nothing can be done with regard to that),
but what about the space or other chars? Space is not a problem because it is
inside a dictionary and anyways a form field name is a "String Object" not a
"Name Object", so the escaping #xx means nothing but escaping is different if
using PDFDocEncoding (\ddd in octal, \r \n \\ or others), but it's probably even
better to use UTF-16BE (if Acrobat 6.0+ is not too much of a limitation).

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org
For additional commands, e-mail: issues-h...@sw.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[sw-issues] [Issue 82785] PDF: AcroForm fieldnames n ot correct, "." --> #2E

2009-02-11 Thread pl
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=82785





--- Additional comments from p...@openoffice.org Wed Feb 11 14:43:16 + 
2009 ---
The '.' is not a valid character in a partial field name (since it's the
delimiter between partial field names in a fully qualified field name); see
implementation note #82 in the PDF 1.4 reference manual

 "82. Beginning in Acrobat 3.0, partial field names may not contain a period."

Since the dot is not valid in PDF (but valid in the odt) it needs to be encoded.

The encoding of spaces among other characters is due to the fact that field
names cannot be unicode encoded; the names are unicode encoded in ODT, but must
not be in PDF; see implementation not #83 in  the PDF 1.4 reference manual

"83. Acrobat versions 3.0 and later do not support Unicode encoding of field
names."

This would not prevent us from using spaces in there as they obviously are
ASCII; however the field name can be concatenated to get a fully qualified field
name. In these it is never a good idea to use spaces since this is usually a
token separator. Also they are forbidden in PDF names. So it might be formally
correct to use spaces in field names, but it probably would lead to secondary
errors; why risk that.

For human readable text there is the /TU value in a PDF widget which can be set
via the description field in OOo.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org
For additional commands, e-mail: issues-h...@sw.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[sw-issues] [Issue 82785] PDF: AcroForm fieldnames n ot correct, "." --> #2E

2009-02-10 Thread lapo_luchini
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=82785


User lapo_luchini changed the following:

What|Old value |New value

  CC|'kpalagin'|'kpalagin,lapo_luchini'





--- Additional comments from lapo_luch...@openoffice.org Tue Feb 10 
16:48:07 + 2009 ---
I've found the same problem, while using not periods but spaces, I attached a
(very small) example.

Example code:
% fgrep -a #20 OOo_form.pdf

Current result:
/T(name#20with#20space)

Expected result:
/T(name with space)

Using an hex-editor to change the first in the second makes a PDF that can then
be correctly compiled with field name "name with space".

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org
For additional commands, e-mail: issues-h...@sw.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[sw-issues] [Issue 82785] PDF: AcroForm fieldnames n ot correct, "." --> #2E

2009-02-10 Thread lapo_luchini
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=82785





--- Additional comments from lapo_luch...@openoffice.org Tue Feb 10 
16:45:10 + 2009 ---
Created an attachment (id=60069)
exaple PDF with form


-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org
For additional commands, e-mail: issues-h...@sw.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[sw-issues] [Issue 82785] PDF: AcroForm fieldnames n ot correct, "." --> #2E

2009-02-10 Thread lapo_luchini
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=82785





--- Additional comments from lapo_luch...@openoffice.org Tue Feb 10 
16:44:33 + 2009 ---
Created an attachment (id=60068)
example ODT with form


-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org
For additional commands, e-mail: issues-h...@sw.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[sw-issues] [Issue 82785] PDF: AcroForm fieldnames n ot correct, "." --> #2E

2008-01-21 Thread hi
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=82785





--- Additional comments from [EMAIL PROTECTED] Mon Jan 21 15:25:07 + 
2008 ---
Please provide a odt&pdf sample to evaluate. Thanks.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[sw-issues] [Issue 82785] PDF: AcroForm fieldnames n ot correct, "." --> #2E

2008-01-21 Thread kpalagin
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=82785


User kpalagin changed the following:

What|Old value |New value

  CC|''|'kpalagin'





--- Additional comments from [EMAIL PROTECTED] Mon Jan 21 08:35:19 + 
2008 ---
perjensen63,
can this problem be reproduced without Java (as my developer skills are non-
existent)?

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[sw-issues] [Issue 82785] PDF: AcroForm fieldnames n ot correct, "." --> #2E

2007-10-23 Thread mru
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=82785


User mru changed the following:

What|Old value |New value

 Assigned to|mru   |hi

 Summary|AcroForm fieldnames not co|PDF: AcroForm fieldnames n
|rrect, "." --> #2E|ot correct, "." --> #2E





--- Additional comments from [EMAIL PROTECTED] Tue Oct 23 09:07:21 + 
2007 ---
Reassigned to HI.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]