Alexandro Colorado wrote:

> On Wed, Jun 17, 2009 at 1:59 AM, Mathias Bauer<[email protected]> wrote:
>> Alexandro Colorado wrote:
>>
>>> sure you cant but some parts only. Some other parts are fixed into the
>>> OOo internal binary template that will ignore, like meta information
>>> for example.
>>
>> I don't know what an "OOo internal binary template" is, maybe you are
>> talking about the internal default values for the default paragraph
>> style. Anyway, this is completely unrelated to the question.
> 
> No I mean the user-defined fields on the Document properties under
> meta.xml. The internal binary template of OOo will ignore aditional
> user-defined fields from the 4 slots it has. Not sure if this is fixed
> now on 3.1 since last I tried was 2.4 but I am sure I can find that
> out soon.

Just to avoid confusion, let me go into details here.

Maybe in the beginning OOo 1.x was not able to handle more than 4 custom
properties correctly (I don't remember that exactly), but at least
OOo2(!).0 was able to load and save them, so they were not ignored. OOo
didn't have a UI to show them before 3.1, but they could be accessed via
Basic.

In OOo2.4 we also added support for these properties in Writer text fields:

http://blogs.sun.com/GullFOSS/entry/custom_properties_and_fields

So now there was a way to make custom properties visible.

In 3.0 finally we added support for arbitrary meta data. ODF allows to
put any kind of meta data into meta.xml, not only properties, and before
3.0 we just ignored that. Now this data is read, preserved and written
again (we keep the whole DOM tree of meta.xml internally instead of just
picking up the properties in it as before).

OOo 3.1 finally also has got a new UI for displaying custom properties.

> UPDATE: ok it seems behavior has change a bit, and now at least the
> XML is preserved after adding extra nodes to the XML. Before  it use
> to rewrite the XML for what it was said to be a standard internal
> binary encapsulation of ODT which arguably break compatibility.
> 
> For example if I have an ODT editor that has 10 user-defined fields,
> as opposed to OOO's 4. All this ODT meta-info would be errased after
> OOo opens it. -- No longer the case.

As I wrote, that was fixed already a long time ago. Maybe you didn't
have custom properties, but custom meta data? This was fixed in 3.0.
Regards,
Mathias

-- 
Mathias Bauer (mba) - Project Lead OpenOffice.org Writer
OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
Please don't reply to "[email protected]".
I use it for the OOo lists and only rarely read other mails sent to it.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to