LibreOffice Criticizes Microsoft's OOXML and Excel Date Handling

๐กUnderstand the risks of proprietary document formats when building data-heavy AI applications.
โก 30-Second TL;DR
What Changed
TDF accuses Microsoft of using closed, deceptive OOXML formats
Why It Matters
This highlights the ongoing friction between open-source alternatives and proprietary enterprise software, which affects data interoperability for AI training pipelines.
What To Do Next
If building data ingestion pipelines, validate date formats strictly rather than relying on Excel-exported CSVs.
Key Points
- โขTDF accuses Microsoft of using closed, deceptive OOXML formats
- โขExcel's date handling is criticized as the worst in the industry
- โขLibreOffice advocates for open standards to protect global users
๐ง Deep Insight
Web-grounded analysis with 16 cited sources.
๐ Enhanced Key Takeaways
- โขThe OOXML specification is criticized for its immense size, approximately 7,000 pages, which makes accurate implementation by third-party software nearly impossible, contrasting with the more concise OpenDocument Format (ODF).
- โขMicrosoft Office applications frequently utilize a 'Transitional' variant of OOXML, which incorporates features for backward compatibility with older formats, rather than strictly adhering to the ISO/IEC 29500 'Strict' standard, leading to interoperability challenges.
- โขExcel's long-standing date handling error, specifically treating 1900 as a leap year, originated from a deliberate decision to maintain compatibility with Lotus 1-2-3, resulting in dates after February 28, 1900, being off by one day in its serial date system.
- โขThe standardization process for OOXML by ISO/IEC was highly controversial, marked by allegations of procedural irregularities, vote manipulation, and 'committee stuffing' during its fast-track approval.
- โขThe Document Foundation (TDF) asserts that OOXML's complexity, proprietary dependencies, inclusion of binary data structures, and Windows-specific elements render it a 'fauxpen standard' primarily designed to create vendor lock-in rather than promote genuine interoperability.
๐ Competitor Analysisโธ Show
| Feature/Aspect | LibreOffice (ODF) | Microsoft Office (OOXML) |
|---|---|---|
| Native File Format | OpenDocument Format (ODF) - ISO standard | Office Open XML (OOXML) - ISO/IEC standard (controversial) |
| Format Openness | Open, multi-vendor, multi-stakeholder development; royalty-free; concise specification. | Less open, single-vendor control; complex, voluminous (~7,000 pages) specification; proprietary dependencies. |
| Date Handling | Adheres to standard Gregorian calendar rules. | Incorrectly treats 1900 as a leap year for backward compatibility with Lotus 1-2-3, causing a one-day shift for dates after Feb 28, 1900. |
| Compatibility | Can open/save MS Office formats, but may have formatting differences; native ODF ensures broader accessibility. | Best compatibility within Microsoft ecosystem; third-party implementation of OOXML is difficult due to complexity and inconsistencies. |
| Pricing Model | Free and open-source. | Commercial product, often subscription-based (Microsoft 365) or one-time purchase. |
| Platform Support | Windows, macOS, Linux, FreeBSD, NetBSD, OpenBSD, Haiku, ChromeOS (via Collabora Office). | Windows, macOS (with some feature differences), web, mobile apps. |
๐ ๏ธ Technical Deep Dive
- OOXML Specification Issues: The OOXML specification is notably voluminous, spanning approximately 7,000 pages, which critics argue makes it exceedingly difficult for third parties to implement correctly. It contains proprietary dependencies, including references to undocumented legacy behaviors of older Microsoft Office versions and Windows-specific features, complicating cross-platform implementation. Furthermore, despite being XML-based, OOXML incorporates binary data structures in various sections, particularly for backward compatibility, which compromises the transparency expected of an XML format. Microsoft Office applications often do not fully adhere to the 'Strict' ISO/IEC 29500 standard, instead using a 'Transitional' variant that includes compatibility features with legacy formats.
- Excel's 1900 Leap Year Bug: Excel's date system stores dates as serial numbers, with January 1, 1900, represented as '1'. The core of the bug is Excel's incorrect assumption that 1900 was a leap year (it was not, as century years must be divisible by 400 to be leap years). This error was deliberately incorporated for backward compatibility with Lotus 1-2-3, which had the same bug. Consequently, Excel accepts February 29, 1900, as a valid date, causing all dates after February 28, 1900, to be off by one day in the underlying serial system. This historical bug has even been formalized as a requirement within the Ecma Office Open XML (OOXML) specification.
๐ฎ Future ImplicationsAI analysis grounded in cited sources
โณ Timeline
๐ Sources (16)
Factual claims are grounded in the sources below. Forward-looking analysis is AI-generated interpretation.
Weekly AI Recap
Read this week's curated digest of top AI events โ
๐Related Updates
AI-curated news aggregator. All content rights belong to original publishers.
Original source: cnBeta (Full RSS) โ


