Dear office suite users, In recent days you will have read various articles announcing the arrival of Euro-Office, which is being “marketed” as the first open-source office suite developed in Europe. We feel compelled — reluctantly, since open source should rest on transparency, not deception — to correct this claim. The first open-source office suite developed in Europe was OpenOffice.org in 2001, based on StarOffice’s source code, followed by LibreOffice from 2010. These are two genuine open-source office suites, built from source code that originated in Europe. They are not a freeware clone of MS Office whose code provenance is undisclosed, nor a product that has rebranded itself out of pure opportunism to ride today’s wave of Digital Sovereignty. It is worth remembering that many of those who champion Digital Sovereignty today were silent back in 2006, when the open ISO/IEC ODF standard — the pillar of Digital Sovereignty — was announced: not only did they not listen to us during all these years, but in some cases they greeted us with a condescending smile. If we can speak of Digital Sovereignty in Europe today, it is thanks to The Document Foundation and LibreOffice community members at large, who kept
Their point about OOXML has traditionally been that the format that Microsoft Office itself produces has never once matched the standardized standard they ratified. So Microsoft used it to check a box on some requirements sheet and muddy the waters (like this), but anyone actually following the standard would not have achieved actual cross compatibility with the massive gorilla in the space. But because it’s “Microsoft’s format” any issues would have felt like bugs in LibreOffice rather than bugs in Microsoft Office. In contrast the standardized ODF actually matches the ODF you find in practice.
That all having been said, I stopped paying attention to that whole scene a while ago, so I don’t know what the current situation is, or if that still applies. It’s possible later version of MSOffice actually moved to the standard version at some point, or that the standard was updated to match what MSOffice actually reads and writes. Possible, but I just don’t know.
I basically agree with you, but I’m also a little pedantic, so I’ll also say that if the standard format isn’t the format MSOffice outputs, then the standard format isn’t the format everyone is using, they’re using a similar but incompatibly different format. And so if there’s an opportunity to pick what the standard must be going forwards, and the actual true OOXML spec has effectively zero users, and what MSOffice outputs isn’t an open standard, then you might as well pick ODF which has more than zero users and is standardized.
But again, this is moot if the thing MSOffice outputs is actually actually OOXML now.
Their point about OOXML has traditionally been that the format that Microsoft Office itself produces has never once matched the standardized standard they ratified. So Microsoft used it to check a box on some requirements sheet and muddy the waters (like this), but anyone actually following the standard would not have achieved actual cross compatibility with the massive gorilla in the space. But because it’s “Microsoft’s format” any issues would have felt like bugs in LibreOffice rather than bugs in Microsoft Office. In contrast the standardized ODF actually matches the ODF you find in practice.
That all having been said, I stopped paying attention to that whole scene a while ago, so I don’t know what the current situation is, or if that still applies. It’s possible later version of MSOffice actually moved to the standard version at some point, or that the standard was updated to match what MSOffice actually reads and writes. Possible, but I just don’t know.
It’s a poorly designed standard without a doubt. But it is the format people use, and no one who uses it is paying Microsoft (including LibreOffice).
Whinging about people using it is not the way to make useful software.
I basically agree with you, but I’m also a little pedantic, so I’ll also say that if the standard format isn’t the format MSOffice outputs, then the standard format isn’t the format everyone is using, they’re using a similar but incompatibly different format. And so if there’s an opportunity to pick what the standard must be going forwards, and the actual true OOXML spec has effectively zero users, and what MSOffice outputs isn’t an open standard, then you might as well pick ODF which has more than zero users and is standardized.
But again, this is moot if the thing MSOffice outputs is actually actually OOXML now.
I believe they are using a modified version, not 100% sure. But in my opinion they should let the user decide on install.
https://news.ycombinator.com/item?id=47559056
I honestly blame ISO they should have never approved this format. https://www.ip-watch.org/2008/04/01/office-open-xml-officially-approved-as-international-standard/
There is evidence of intent behind some of those poor design choices.