Fix My Home Computer

Blog

LibreOffice Condemns Microsoft for Prioritizing Profits Over User Freedom

0.7k words By Robert

The Document Foundation has publicly accused Microsoft of weaponizing the OOXML document standard to trap users in its ecosystem, creating deliberate compatibility barriers that break formatting when people switch to free alternatives like LibreOffice. In spite of being an ISO-approved "open standard," OOXML's 7,000-page specification contains proprietary extensions and undocumented legacy behaviors that competitors can't replicate without Microsoft's blessing. The controversy centers on vote manipulation allegations during standardization and Microsoft's refusal to implement the ISO Strict version-keeping switching costs high as it strengthens its market stranglehold. The technical details reveal exactly how deep this rabbit hole goes.

The Document Foundation has launched a scathing condemnation of Microsoft's OOXML implementation practices, accusing the tech giant of weaponising document standards to trap users in its ecosystem. According to LibreOffice developers, Microsoft has systematically manipulated the Office Open XML format through proprietary extensions and undocumented features that create deliberate compatibility barriers. The result? Users who attempt to switch to free alternatives find their documents riddled with formatting errors and broken functionality.

Microsoft's proprietary extensions and undocumented features create deliberate compatibility barriers that weaponise document standards to trap users in its ecosystem.

The technical evidence is damning. OOXML specifications span approximately 7,000 pages-roughly the length of War and Peace three times over-making faithful third-party implementation virtually impossible. But here's where it gets interesting: Microsoft Office doesn't even use the standardised ISO/IEC 29500 Strict version. Instead, it relies on the "Transitional" variant, which references undocumented legacy behaviours from previous Office versions. It's like publishing a recipe but leaving out half the ingredients.

LibreOffice developers have documented numerous instances where Microsoft Office creates OOXML files that deviate from published specifications. Advanced formatting features, complex mathematical equations, embedded objects, and sophisticated layout elements frequently break when processed according to the actual ISO standard. When LibreOffice opens these files correctly per specification, the results differ dramatically from the original appearance. Full functionality simply cannot be replicated without Microsoft's proprietary implementation details.

Platform-specific elements related to fonts, rendering, and system behaviours further complicate cross-platform implementation. Binary data structures embedded within the supposedly transparent XML-based format undermine the openness that XML should guarantee. The format's deeply nested tag structures create additional layers of unnecessary complexity. The whole situation raises an uncomfortable question: what's the point of an "open standard" that only one company can properly implement?

The standardisation process itself remains controversial. ISO's fast-track approval of OOXML faced allegations of procedural irregularities and vote manipulation. Legitimate doubts persist about whether commercial interests trumped technical merit during standardisation. OOXML differs fundamentally from competing standards like ODF regarding complexity and genuine openness.

For enterprises seeking to escape vendor lock-in, these compatibility issues represent critical barriers. Hybrid work environments increasingly demand seamless document sharing across platforms, yet Microsoft's implementation choices systematically undermine interoperability. Organisations face an awkward choice: accept reduced flexibility in document workflows or absorb the costs and risks of incomplete compatibility. LibreOffice has responded by developing diagnostic tools for identifying compatibility issues before they disrupt workflows.

Backward compatibility requirements theoretically justify Microsoft's approach-supporting numerous formatting options accumulated over decades. But critics argue this explanation conveniently ignores how strategic ambiguity serves commercial interests. When switching costs remain artificially high because of implementation opacity, user freedom suffers whilst Microsoft's market position strengthens.

The Document Foundation's accusations highlight a broader tension in software standards: genuine openness versus standards designed primarily to satisfy regulatory requirements whilst maintaining competitive advantages. Until OOXML implementation matches specification transparency, users remain locked in-not by technical necessity, but by deliberate design choices prioritising profits over freedom.

Final Thoughts

The open-source community challenges Microsoft's prioritization of profits over user freedom, highlighting the ongoing struggle between vendor lock-in and genuine interoperability. As enterprises face the choice between convenience and control in an increasingly fragmented cloud-based productivity environment, the tension between proprietary and open-source solutions intensifies.

Fix It Home Computer understands the complexities businesses face when navigating between different office suites and document formats. Our team specializes in migrating systems from proprietary software to open-source alternatives like LibreOffice, ensuring seamless document compatibility and reducing long-term licensing costs. We provide comprehensive support for businesses seeking digital autonomy without sacrificing productivity.

Ready to break free from vendor lock-in and explore cost-effective office solutions? Click on our contact us page to discuss how we can help your business transition to open-source productivity tools while maintaining full document compatibility.

Computer trouble? Talk to a person, not a call centre

Flat $150 for the first hour, no call-out fee, and no surcharge at the weekend. Call (07) 3155 2051 and describe the fault.

Onsite rate
$150
first hour
Call-out fee
$0
never
Weekend surcharge
$0
incl. public holidays
Typical visit
< 1 hr
most problems

Flat $150 first hour · No call-out fee

Request a quote

Only the phone number is required. If you are not sure what is wrong, say that instead - working it out is part of the first hour and it is included in the rate.

Australian mobile, starting with 04.

Town or suburb only, no street address needed. Start typing to search.

Apple and some other brands quote better with it. Skip it if you cannot find it quickly - it will not delay anything.

Up to 5 photos. Handy for a cracked screen or a strange error message.

Or call (07) 3155 2051

Nothing is sent from this page yet, so pressing Send opens your email app with the answers filled in.