<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with ooxml]]></title><description><![CDATA[A list of topics that have been tagged with ooxml]]></description><link>https://board.circlewithadot.net/tags/ooxml</link><generator>RSS for Node</generator><lastBuildDate>Tue, 02 Jun 2026 23:27:54 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/tags/ooxml.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[A Standard in Name Only: What OOXML Transitional Tells Us About Format Sovereignty]]></title><description><![CDATA[A Standard in Name Only: What OOXML Transitional Tells Us About Format SovereigntyWhen a public administration is told its documents are stored in “an ISO standard format,” the assumption is that an ISO standard ought to be a clean, implementable specification that any qualified software vendor can support.OOXML — the format behind Microsoft’s docx, xlsx and pptx files — does not work this way.https://blog.documentfoundation.org/blog/2026/06/02/a-standard-in-name-only/#odf #ooxml]]></description><link>https://board.circlewithadot.net/topic/2e3cad18-ec51-4b84-af23-d3e796571ff2/a-standard-in-name-only-what-ooxml-transitional-tells-us-about-format-sovereignty</link><guid isPermaLink="true">https://board.circlewithadot.net/topic/2e3cad18-ec51-4b84-af23-d3e796571ff2/a-standard-in-name-only-what-ooxml-transitional-tells-us-about-format-sovereignty</guid><dc:creator><![CDATA[libreoffice@fosstodon.org]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Excel has a thing for getting dates wrong (the (in)famous 1900 leap-year bug, inherited from Lotus 1-2-3 and never fixed), and when Excel gets dates wrong, no other software does it worse.]]></title><description><![CDATA[Excel has a thing for getting dates wrong (the (in)famous 1900 leap-year bug, inherited from Lotus 1-2-3 and never fixed), and when Excel gets dates wrong, no other software does it worse. [..] The HUGO Gene Nomenclature Committee was forced in 2020 to rename dozens of human genes – including SEPT1 and MARCH1 – because Excel kept silently converting their symbols to dates. Rather than going to Microsoft and demanding a bug fix, scientists preferred to throw years of established nomenclature down the drain to avoid upsetting RedmondI really like these two examples, not because of the issues as such, but as two examples of how people usually handle bugs in proprietary software: ignore them or work around them, but almost never complain about the software.MS Office is always mentioned as the standard, and everything has to be as good as MS Office if people consider different solutions. But in the end, it's not because MS is so much better. People are just used to it and how to work around strange issues that they would never accept in a Free Software solution.https://blog.documentfoundation.org/blog/2026/05/15/no-digital-sovereignty-without-odf/#OpenStandards #ODF #OOXML #Microsoft #Office #FreeSoftware]]></description><link>https://board.circlewithadot.net/topic/e999c868-a57e-4cb4-a39e-722d2ac1bfe5/excel-has-a-thing-for-getting-dates-wrong-the-in-famous-1900-leap-year-bug-inherited-from-lotus-1-2-3-and-never-fixed-and-when-excel-gets-dates-wrong-no-other-software-does-it-worse.</link><guid isPermaLink="true">https://board.circlewithadot.net/topic/e999c868-a57e-4cb4-a39e-722d2ac1bfe5/excel-has-a-thing-for-getting-dates-wrong-the-in-famous-1900-leap-year-bug-inherited-from-lotus-1-2-3-and-never-fixed-and-when-excel-gets-dates-wrong-no-other-software-does-it-worse.</guid><dc:creator><![CDATA[bjoern@social.schiessle.eu]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>