Q: "Am I correct to assume that ODF 1.2 is backward compatible? I.e. an old
application will still be able to open a ODF 1.2 document?"
A: It depends. There are provisions in ODF 1.2 that, if exercised in an ODF 1.2, make it unlikely
that an ODF 1.1 consumer could handle it properly. Also, the document will be identified as an ODF
1.2 document and possibly in unexpected places that might interfere with an ODF 1.1 consumer.
More A: In general, documents identified as 1.2 often have nothing that requires an ODF 1.2
consumer and they will be successfully handled. There is no downward compatibility promise in 1.2
and there is no special provision, as some standards have, to help a down-level consumer detect and
work around up-level features it was not designed for.
Q: "I assume you didn't use LO Writer to compose the 1217 page document. Which program did you use"
A: All of the document production was in ODF. The editable forms of the documents are ODT files,
and these are provided as the authoritative versions of the specification, along with PDF and HTML
versions that are not authoritative. Since most of the work was completed by the end of 2010,
OpenOffice.org versions were used. Also, some special XSLT scripts were used to create some of the
content, such as cross-references and statement of XML dependencies that are derived by
consultation of the schema.
More A: I am currently working on an Errata for ODF 1.1 and that work is being done in LO 3.3.2,
including a change-tracked version of the ODF 1.1 specification that shows the Errata applied. (I
won't change LO versions until the document is completed.) Also, an Amendment for the ISO version
of ODF 1.0 was produced in ODF, although the documents circulated for approval at ISO are PDFs. At
this time, I do any creation of ODF documents for production purposes using LibreOffice. (By the
way, I am an editor on Part 3 only, the smallest part of the specification.)
- Dennis
-----Original Message-----
From: Pedro [mailto:pedlino@gmail.com]
Sent: Saturday, October 01, 2011 02:40
To: users@global.libreoffice.org
Subject: [libreoffice-users] Re: OASIS Standard ODF 1.2 Approved
Congratulations to all.
I believe that a solid open file format is extremely important.
Am I correct to assume that ODF 1.2 is backward compatible? I.e. an old
application will still be able to open a ODF 1.2 document?
Dennis, one curiosity since you were one of the editors: I assume you didn't
use LO Writer to compose the 1217 page document. Which program did you use?
Scribus?
--
View this message in context:
http://nabble.documentfoundation.org/OASIS-Standard-ODF-1-2-Approved-tp3384139p3384633.html
Sent from the Users mailing list archive at Nabble.com.
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-users] Re: OASIS Standard ODF 1.2 Approved (continued)
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.