Issue 72164 - special chars in FieldMaster.User cause wrong values by using conditions
Summary: special chars in FieldMaster.User cause wrong values by using conditions
Status: ACCEPTED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 2.0.4
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: ms_interoperability
Depends on:
Blocks:
 
Reported: 2006-12-01 08:46 UTC by eberlein
Modified: 2017-05-20 11:15 UTC (History)
2 users (show)

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


Attachments
userfields with allowed and special chars (13.90 KB, application/vnd.oasis.opendocument.text)
2006-12-01 09:11 UTC, eberlein
no flags Details
doc with fields containing special chars (8.08 KB, application/vnd.oasis.opendocument.text)
2006-12-01 12:45 UTC, eberlein
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description eberlein 2006-12-01 08:46:55 UTC
You can set a FieldMaster.User with api and name it with umlauts and special
characters.
The fieldmaster ist displayed in GUI (STRG-F2).
If you insert fields of type "conditional text" and use the field name in the
condition, the result will not show the expected values.
I don't figured out, if the behavior will be the same with
FieldMaster.SetExpression.
Comment 1 eberlein 2006-12-01 09:11:18 UTC
Created attachment 41035 [details]
userfields with allowed and special chars
Comment 2 Oliver Specht 2006-12-01 10:47:47 UTC
The names containing special chars have to be quoted. 

"$EMPFF" == 1

works as expected. I had no problems with umlauts.
Comment 3 eberlein 2006-12-01 12:44:08 UTC
You tried it only once, right?
By adding and removing the quotes, the ConditionalText reacts.
It doesn't if the quotes are persistent, see attachment2 [details].

Btw, if you remove all fields from TextContent, you can't delete the Masterfield
$EMPFF with GUI.
Comment 4 eberlein 2006-12-01 12:45:52 UTC
Created attachment 41044 [details]
doc with fields containing special chars
Comment 5 Oliver Specht 2006-12-01 13:50:42 UTC
You're right. 
Target changed to 2.x
Comment 6 Oliver Specht 2006-12-01 13:51:09 UTC
Accepted
Comment 7 Martin Hollmichel 2007-09-10 13:35:50 UTC
move target to 3.x according http://wiki.services.openoffice.org/wiki/Target_3x
Comment 8 Marcus 2017-05-20 11:15:30 UTC
Reset assigne to the default "issues@openoffice.apache.org".