Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Le 2011-10-05 03:30, Thorsten Behrens a écrit :
Dennis E. Hamilton wrote:
From: Marc Paré []

Thanks to all the people who answered this. It seems whether LibreOffice
is partially or completely compliant to "OASIS version 1.2" is more
complicated to establish for non-dev people.

LibO is, like OOo, an extended conformance producer/consumer of
ODF1.2, in its default setup. Choosing ODF format version 1.2 in
Tools->Options->Load/Save->General makes it produce "conforming ODF
documents" as per 22.2.1.

Everything else is a bug. :)

   There is basically schema validation available, and there are a variety
   of schema verifiers.  It would be good to work cooperatively to improve
   them.  (Schema validity assessment is not enough to know that all of the
   ODF rules not baked into the schema are honored, but it is an important
   first-order start.) to the
best of my knowledge goes beyond pure schema verification, but also
e.g. checks various prose-only normative requirements (e.g. for the
zip package).

I'm not subscribed to the users list, so if you need my answer,
please Cc me.


-- Thorsten

Thanks for the two sites. I'll give them a try to see what kind of results. they get.



Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.