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

Hi :)
If this is for an article then i am not sure we can really help.
Mostly we are all just volunteers and can't give the TDF's official
stand-point on any of this.  All we can give is anecdotes which
doesn't really count as proof!

Over the years we have often heard about problems with the MS format
on this mailing list but very seldom heard about problems with our
format on their systems!

Quite why the problems weren't being raised as bug-reports against
MS's apparently poor implementation is a bit of a mystery.  MS admit
to making "accidental" mistakes in their implementation of their own
format and we get the blame.  It was the same with the Rtf format and
even now that MS have lost the court case about their 'accidents' with
Rtf people still seem to think that everyone else was to blame.  It
might be interesting to compare the similarity of the promises for
interoperability made by MS for both formats over the years and the
types of 'accidents' that both formats have suffered.

We know for certain that Excel 2010 and previous versions of MSO
implemented ODF support so badly that formulas got replaced by
hard-coded values.  However, over the years this only got reported to
us 1 or 2 times.

What we don't know is whether people experienced the problem and took
it as a sign to avoid Open Document Formats in favour of proprietary
implementations of other formats or whether people were simply not
using ODF much at all and so never noticed the problem.

Perhaps people expected formats to only work on the systems they were
written in, ie that the much vaunted "interoperability" was a complete
myth and only applied to machines running the same OS and the same
version of the same programs.  That certainly seems to be the
prevelant attitude amongst office workers i work with.

Anyway, i personally think MS Office is only just attempting to
correctly implement the format because ODF is only just beginning to
be used widely enough that people are beginning to question why it
works so well on everything except MS's stuff.

Regards from
Tom :)

On 14 February 2014 13:59, Jay Lozier <> wrote:

On 02/14/2014 06:51 AM, M. Fioretti wrote:


here is the question, you're welcome to pass it around as much as you
see fit:

what is the ACTUAL, current status of Microsoft Office compliance with
support for the OpenDocument Format? Is there something specific that
isn't supported yet? What, how.. Case stories, tests, reports,
whatever, all pointers are welcome. Thanks in advance!



MSO 2010 and earlier did not support ODF 1.2 only ODF 1.1. I saw somewhere
that ODF 1.2 is supported in MSO 2013/Office 365. Since MS has a history of
"improving" their own formats each release I do not know if they have not
introduced "improvements" which make the alleged ODF 1.2 effectively a
proprietary format.

Jay Lozier

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be

To unsubscribe 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.