Bonum Certa Men Certa

Microsoft Continues to Further Distort OOXML in Order to Make it Less Compatible With Non-Microsoft Software

ooxml_demo_4.jpg



Summary: Microsoft continues to distort the office suites market and impede interoperability using the OOXML pseudo 'standard', essentially by branching out into "Strict" and "Transitional", making it exceedingly hard for developers to deal with files generated by Microsoft Office and vice versa

TRYING to work with Microsoft is misguided. Just look and see what has happened to many companies, including -- to name a recent example -- Nokia. Microsoft has no honour for anyone but Microsoft itself. Microsoft was bribing officials and abusing sceptics in order to get its way when it comes to document formats. Nobody should forget the crimes that Microsoft committed in order to keep the world stuck with Microsoft Office. We reminded the British government of these crimes and very recently the UK adopted ODF. This was a very smart and timely move because based on people from The Document Foundation (TDF), the bogus 'standard' which is basically just an 'open'-looking gown for Microsoft Office (proprietary) formats is now being further distorted in order to cause trouble for people who are not Microsoft customers. These abuses are even worse than before and Microsoft thinks it can get away with them because it bribed people to put an ECMA and ISO stamp on OOXML (no matters what happens to it later on).



As Charles from The Document Foundation put it the other day:

Regular readers of this blog will remember these glorious days, just before the big financial crisis, where Microsoft had created the so-called OpenXML standard that was supposed to be totally not competing against the OpenDocument Format, managed to have pretty much the entire standards community swallow it in the most creative ways possible, then fell short of actually implementing it in its own products. A good summary of the whole -technical- story is available here. The irony of life has the uncanny ability to devise ways to enchant us. Well, sort of. The format called “OOXML – Strict”, by comparison to “OOXML-Transitional” was the readable open part of the ISO 29500 standard, known as OOXML. For years, it was obvious that Microsoft Office implemented OOXML-Transitional (the heap of the more or less documented parts of the format alongside undocumented blurbs) and nothing else, creating a situation where one standard, OOXML was existing, and another format, OOXML, was fully implemented and spread all around, yet was an undocumented, proprietary specification. That’s the .docx, pptx, and .xlsx you see everywhere, and the one LibreOffice was busy reverse-engineering for all these years.

This unfortunate situation, we were told, was about to change soon, with the full adoption of OOXML-Strict by Microsoft Office. Helas, if you open a purely OOXML-Strict compliant file with Microsoft Office 2013, the file will be declared corrupt. If you open the same one with LibreOffice 4.3, the file will open and you will be able to edit its contents just like with any other format supported by LibreOffice. In other words, LibreOffice can claim to have a better support of OOXML than Microsoft Office, despite years of unfulfilled promises, pledges, and never met expectations by Redmond. I guess that, just like the old saying goes, promises only commit the ones who actually believe them.


IBM's Rob Weir has just released another piece about document formats [1] and a new interview with Italo Vignoli of The Document Foundation [2] sheds more light on what Charles spoke about. To quote Vignoli: "MS Office locks-in the user not only with proprietary formats but also with the OOXML pseudo-standard format. This is due to the way the supposedly standard format is handled by MS Office.

"In fact, each version of MS Office since 2007 has a different and non standard implementation of OOXML, which is defined as “transitional” because it contains elements which are supposed to be deprecated at standard level, but are still there for compatibility reasons.

"Although LibreOffice manages to read and write OOXML in a fairly appropriate way, it will be impossible to achieve a perfect interoperability because of these different non standard versions.

"In addition to format incompatibilities, Microsoft – with OOXML – has introduced elements which may lead the user into producing a non interoperable document, such as the C-Fonts (for instance, Calibri and Cambria)."

When Microsoft speaks about following standards what it means to say is that "Microsoft is the standard" and everyone must just follow Microsoft. Only a fool would choose OOXML over ODF, especially now. Korea and China seem to be moving away from Office quite rapidly.

Related/contextual items from the news:


  1. Document as Activity versus Document as Record
    And then there is a document as the record of what we did. This is implied by the verb “to document”. This use of documents is still critical, since it is ingrained in various regulatory, legal and business processes. Sometimes you need “a document.” It won’t do to have your business contract on a wiki. You can’t prove conformance to a regulation via a Twitter stream. We may no longer print and file our “hard” documents, but there is a need to have a durable, persistable, portable, signable form of a document. PDF serves well for some instances, but not in others. What does PDF do with a spreadsheet, for example? All the formulas are lost.


  2. Why you should never use Microsoft’s OOXML pseudo-standard format
    The UK government recently announced that they would use ISO approved document standard ODF for viewing and sharing government documents. It’s a very important move because it breaks Microsoft’s vendor lock where single US-based company ‘owns’ and ‘controls’ all the documents created on Earth. Microsoft is infamous for using unethical means to make it harder for other players to offer any kind of interoperability with their products which can threaten Microsoft’s market share.

    So we reached out to Italo Vignoli of The Document Foundation, the organization responsible for developing LibreOffice which is a fork of OpenOffice, to understand the risks of using OOXML…




Recent Techrights' Posts

Helping Microsoft 'Hijack' Developers (to Make Them Work for Microsoft, Not the Competition)
VS Code is proprietary spyware of Microsoft. Jack Wallen keeps promoting its use.
Gemini Links 28/02/2024: Groupthink and the 'Problem' With Linux
Links for the day
Android Rising (Windows Down to All-Time Lows, Internationally)
This month was a bloodbath for Microsoft
HexChat Looks for Successors to Keep IRC Growing
IRC is far from dead
[Meme] Just Make Him Happy
Y U no produce more monopolies?
End of a Long February
top 10 posts
[Meme] The EPO's Relationship With Patent Examiners
Nobody is "safe"
New Pension Scheme (NPS) at the European Patent Office Explained at the General Assembly
Investing in the future, or...
Donald Trump & FSFE Matthias Kirschner election denial
Reprinted with permission from Daniel Pocock
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, February 27, 2024
IRC logs for Tuesday, February 27, 2024
Links 27/02/2024: PlayStation Layoffs and More Oppressive New Laws for Hong Kong
Links for the day
Gemini Links 27/02/2024: Facebook as Containment Field and Depression Driven Development (DDD)
Links for the day
They're Adding Warnings Now: The Site "It's FOSS" is Not FOSS
It's better that they at least explicitly state this
Links 27/02/2024: Nevada Versus End-To-End Encryption, Birmingham Bankrupt
Links for the day
End of an Era
The Web isn't just filled with marketing spam but actual disinformation
[Meme] Onboarding New EPO Staff
You read the patent application and grant within hours
The Legacy Prolific Writers Leave Behind Them
"Free Software Credibility Index" after more than 15 years
The Ongoing Evolutionary Process of News-Reading (or News-Finding) on the World Wide Web
it gets worse
Phoronix in Google News
congratulating or welcoming Embrace, Extend, Extinguish (E.E.E.)
Google Fired Many Employees Working on Google News (Which Had Deteriorated and Became Gulag Noise, Littered and Gamed by Blogspam, Plagiarism, and Chatbot/Translator-Generated Spew), Now Comes the Likely 'Phase-out'
No wonder many yearn for the days of DMOZ and Web directories in general
IRC Proceedings: Monday, February 26, 2024
IRC logs for Monday, February 26, 2024
Over at Tux Machines...
GNU/Linux news for the past day
"It's Obvious There's No Future For Any of Us from Blizzard at Microsoft"
The rumours suggest that more Microsoft layoffs are on the way
[Meme] Who's the Boss?
"I thought EPC governed the Office"
Salary Adjustment Procedure (SAP) at the EPO and Why Workers' Salary is Actually Decreasing Each Year (Currency Loses Its Purchasing Power)
outline and update on a years-old blunder
Exposed: FSFE, Legal & Licensing Workshop (LLW), Legal Network & Modern Slavery
Reprinted with permission from Daniel Pocock
Gemini Links 26/02/2024: Mastodon Trouble, RSS, and Zombie-scrolling
Links for the day
Links 26/02/2024: Suicide Crisis and Doctor Walkouts in South Korea
Links for the day
Why Do People Who Attack GNU/Linux Hate Women So Much?
My wife is being viciously targeted again
Ongoing Media Campaign, Sponsored by Bill Gates, to Portray Critics of Gates Crimes as "Conspiracy" Cranks
In prior years we wrote about this PR tactic of Gates
[Meme] Follow the Law, Not Corrupt Bosses
pressuring staff to break the rules to make more money
The EPO Uses Appraisals to Force Staff to Illegally Grant European Patents or Lose the Job. The Matter is Being Escalated en Masse to ILO-AT, Requesting a Review of Appraisal Reports.
it is only getting worse over time
Debian History Harassment & Abuse culture evolution
Reprinted with permission from Daniel Pocock
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Sunday, February 25, 2024
IRC logs for Sunday, February 25, 2024IRC logs for Sunday, February 25, 2024