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


I saw with great pleasure the publication of the implementer's notes for
LibreOffice at

However - as I read thru the list of extensions and the rest of the
documentation on the page, I got a bit confused to the purpose of the
implementer's notes for LibreOffice.

If I should guess, the purpose of the implementer's notes would be to
facilitate better interop between LibreOffice and other implementations in
its ecosystem. The list of extensions go a long way towards achieving this

However, it can never stand on its own.

What is missing is clearly the delta between the implementation of
LibreOffice and ODF itself - in other words: what parts of ODF is not
implemented in LibreOffice? A classic example of this would be missing
support in LibreOffice of the chart type "gantt". Do you have any plan to
include information like this in the implementer's notes?

And finally - the list of extensions to OOF seems incomplete. When
LibreOffice 3.6 was announced, a rather large list of new functions were
added to LibreOffice, and they do not seem to appear in OOF itself . The
list I saw can be found here : (sorry, I only have it
in Danish).

Thanks for your attention :-)

Jesper Lund Stocholm

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.