To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=107502





------- Additional comments from [email protected] Fri Dec 11 15:04:10 +0000 
2009 -------
i've had a look at the attached document's meta.xml.

the problem is that the meta.xml parsing in OOo 2 is quite broken:
it treats the first 4 meta:user-defined elements that have no meta:value-type
attribute "special", adds the via the XDocumentInfo interface, and displays them
in the dialog; all other meta:user-defined are added as properties at the
DocumentInfo service (i.e. they are not actually lost, they are loaded and
stored, just not displayed in the UI).

OOo 3 simply puts all meta:user-defined elements into a PropertyBag service.
an implementation detail of the PropertyBag service is that it sorts its
properties alphabetically; in effect, the meta:user-defined elements are 
reordered.

one way to prevent the reordering would be to change the DocumentProperties
service to remember which of the properties had a meta:value attribute and which
not.
this would in effect require storing the properties twice, which adds
unnecessary complexity and is bad from a maintainability perspective.

another way would be to change the implementation of the PropertyBag service so
it no longer sorts its properties.
but the PropertyBag service is used in lots of other places, and it would be
necessary to check if none of those other uses depend on the current sorting
behaviour; also it is possible that it would be a larger effort to change the
implementation (i think it uses a std::map).

so there is no easy way to change the OOo 3 code so that the problem with OOo 2
does not occur any more.
my advice: stop using the broken OOo version 2.


---------------------------------------------------------------------
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]

Reply via email to