Issue 100121

Summary: Replacement for Words "Document variables" needed
Product: Writer Reporter: Mathias_Bauer
Component: codeAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: cno, issues
Version: OOo 1.0.0   
Target Milestone: ---   
Hardware: Unknown   
OS: All   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---

Description Mathias_Bauer 2009-03-11 12:31:21 UTC
Word has "document variables" that are not visible to the user directly. They
can be seen (and changed) in some VBA code or in text fields using them.

OOo has custom document properties, but they are an incomplete replacement for
several reasons:

- they are visible in the custom properties dialog
- mapping both Word custom properties and document variables to OOo custom
properties can create name clashes
Comment 1 2009-04-01 15:43:54 UTC
i've just had a look at this.

word document variables are imported as user-defined document properties.
word document variable get/set fields are imported as ??? don't know.

ODF has fields for getting user-defined document properties:
<text:user-defined>, but not for setting them.

ODF also has variables:

corresponding OOo API:

the writer core objects seem to be in encfld.hxx:
SwSetExpField SwGetExpField

so maybe we could import word document variables as expression fields,
which has the advantage that we can store them in ODF as well.
Comment 2 sos 2009-11-27 11:45:19 UTC
May i suggest to gives us a tool in the API to make a property non-editable for 
cummon users ?
see also (100150)
Comment 3 Mathias_Bauer 2009-11-27 12:31:23 UTC
This is one possible solution, but it wouldn't be less work than inventing
something completely new as this also would require an ODF change.

*If possible*, we should find something that works without changing ODF.
Comment 4 Marcus 2017-05-20 11:15:31 UTC
Reset assigne to the default "".