Hello all.
I'd like to reopen a discussion that some month ago took place here:
http://listarchives.documentfoundation.org/www/discuss/msg02398.html
It was suggested to discuss it with the developers but Google doesn't
seem to find other discussions on this topic. So here i am. :-)
LibreOffice 3.3.0 default file format is like OOo3.x: ODF 1.2 extended.
Let's call it ODF1.2+. The last ratified standard is ODF 1.2 and the
extended one is not yet ratified.
The question is: why using the extended version by default?
What if ODF1.2 extended will never be ratified? There is someone who is
pushing for it?
Shouldn't the feature that relies upon ODF1.2+ relegated under
"experimental feature" or something like that?
It's about interoperability.
If others wants to make software that interact with ODF files, which
version should they choose? The last standard one, or 1.2+ because the
main ODF implementation is OOo/LibO?
And what does ODF 1.2 extended mean? Is the extended version of OOo3.0.0
equals to OOo3.3.0? Or, since it is an in-progress standard, they differ
in some aspect? In other words, can OOo3.0.0 read a document produced by
OOo3.3.0?
The "extended" terms doesn't guaranteed this. I'm not a developer and i
have to google around to be sure to have no surprise in mixed environment.
I'd like to listen LibO develelopers point of view on this topic.
Keep up the good work, folks!
Ciao.
Cesare.
Context
- [Libreoffice] ODF 1.2 and extended · Cesare Leonardi
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.