The renowned open-source office suite LibreOffice recently issued a statement accusing Microsoft of deliberately employing unnecessarily complex file formats to lock users into its Microsoft 365 ecosystem, thereby obstructing the seamless migration of documents to alternative platforms and hindering workflow continuity.
The complexity in question centers around XML markup languages—both Microsoft 365 and LibreOffice utilize XML to construct and define documents. As LibreOffice explains:
“An XML schema comprises the structure, data types and rules of an XML document and is described in an XML Schema Definition (XSD) file. This tells the PC what to expect and checks that the data follows the rules. In theory, XML and XSD together form the basis of the concept of interoperability.”
However, when it comes to interoperability, LibreOffice and Microsoft 365 have adopted entirely divergent approaches. LibreOffice adheres to the OpenDocument Format (ODF)—an industry-standard, open format free from corporate control. The ODF standard underpins familiar file types such as ODT for text documents and ODS for spreadsheets.
In contrast, Microsoft has engineered its own proprietary Office Open XML (OOXML) standard to encapsulate every functionality of its software suite, resulting in widely used formats like DOCX and XLSX. These are, in essence, ZIP archives—by simply renaming a DOCX file to a ZIP extension, one can access the inner workings of a Microsoft 365 document.
LibreOffice contends that XML should serve as a bridge for compatibility, yet Microsoft has “weaponized” its OOXML standard, rendering it excessively convoluted and, as such, an intentional barrier to entry. The suite cites deeply nested structures, non-intuitive naming conventions, and an abundance of optional elements as hallmarks of this complexity.
For developers of open-source office software, achieving compatibility with Microsoft formats—without direct assistance from Microsoft engineers—becomes a near-impossible challenge. Even the simplest of sentences is transformed into a labyrinth of nested tags. Though the output may appear visually identical on the screen, the underlying archive structure is so intricate that it proves nearly indecipherable to alternative office suites.
LibreOffice also points to similar “lock-in” mechanisms being embedded elsewhere, particularly in the integration of these complex formats with the broader push for Windows 11 adoption. It argues that Microsoft’s insistence on such transitions lacks sound technical justification and serves merely to entrench user dependence.
In conclusion, LibreOffice appeals to users to consider migrating from the proprietary Windows NT operating system to open and community-driven Linux platforms, and to replace the closed Microsoft 365 suite with the open-source LibreOffice alternative.
Related Posts:
- The Mozi Botnet Demise: ESET Researchers Reveal Takedown Tactics
- Unknown developers publish LibreOffice on Microsoft Store
- LibreOffice 25.8 Beta 2 Drops Support for Windows 7/8/8.1 and All 32-bit Systems
Support Our Threat Intelligence
If you find our CVE report and cybersecurity news helpful, consider supporting our work.