When you test software, you must ask yourselves how many people will be affected by that use? They are of course doing the one sensible thing, but Perspective, placing their own needs at the forefront. Y checks, they always do it from their own Nevertheless, even if mutual understanding (compatibility) is not perfect, it is already a step towards easy document exchange.When people evaluate software for their own need and run X vs. However, it is such a general format that, even if you have access or share the same DTDs, you can still have a diverging semantics. Also, the encoding may not be public: developers must guess how it is done and what’s its purpose in obscure cases.īoth suite use XML because XML is supposed to be self-descriptive. A feature may not exist or its design conflicts with the other. It does not always succeed for various reasons. This does not mean that M$ Word can’t format other elements such as words or pages., only it does it differently.Īs a consequence, whenever a file is cross-read, the importing suite must translate the other’s encoding into its own primitives (dictionaries).

M$ Word, on its side, only exports paragraph styles and a style sheet.

Consequently, it exports many dictionaries corresponding to paragraph, character, page, frame, list, … styles. Although both suites try to export their abstract documents in a way defined by the Open Document Format, you cannot expect full compatibility between suites because they are based on different principles.įor instance, LO Writer is heavily based on styles. The good question would be to ask for differences between M$ Office and LibreOffice…įiles, and their formats, is only a means to encode primitives for storage and exchange.

Libreoffice vs openoffice excel 2007