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

No. The standard is open and thus is encouraged to be adopted by all.


On 07/06/2016 05:47 AM, wrote:
I am a software developer and using LibreOffice (LO) on a Linux
environment. But sometimes I have to deal with Word-users.
In such a mixed working group I found out that Word doesn't "respect"
the OpenDocument format.

I had a very(!) simple ODT file created with LO. Only text and headings
created with style sheets (german: "Formatvorlage").
Open and re-save that file with word "destroy" the structure of the
style sheets and something more. e.g. "heading 1-3" becomes just

I am sure you know such problems.

I want to understand why it is that way?

I am not so deep in the topic and in the documents about that. But I
think OpenDocument is a well documented and specified standard.

As I described I observed that Word doesn't fit to that standard. But
Word lie to the user and offer to open and save OpenDocument files.

Of course I know why Microsoft software behave like that - destroying
open and free standards.

The question is why is Microsoft allowed to use "OpenDocument" that way?

Isn't there a juristic way to restrict that?

And is the OD-standard really so wishy-washy that the behaviour I
described is fitted by the standard?

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.