It’s more egregious to me that if you properly implement the Office Open XML [sic] formats, it won’t work with MS Office, because they don’t follow their own specs.

Microsoft Office 2013, 2016, 2019, 2021 and Microsoft 365 continue to read and write files that are conformant to ISO/IEC 29500 Transitional by default. Microsoft Office 2013 and later fully support ISO/IEC 29500 Strict,[73]but do not use it as the default file format because of backwards compatibility concerns.[74]

- https://en.wikipedia.org/wiki/List_of_software_that_supports_Office_Open_XML

EU: “The Americans sent another goddamn .docx file.”

embassy gets sent a notice that closed source formats are not accepted

Microsoft: REEEEEEEEEEE!!!

MS has been playing this game since the early 90’s

This isn’t new, WordPerfect was killed by this among other illegal MS moves.

Microsoft being an illegal monopoly for the *checks notes* twenty-fourth official year.

Just out-and-out assholes for the fiftieth straight year.

It’s been like that since the files got X on the end; docx, xlsx, pbix. They are just zip files containing XML and stuff. This is how you can turn off any password protection of a file, change to zip, disable protection in the XML, change the extension back.

This is the innovation that capitalism breeds. The one they have been telling us all this time, remember?

I remember working with a library called HSSF to read excel files some years ago. It’s an acronym meaning Horrible SpreadSheet Format.

I echo the devs sentiment.

I mean since the company literally pioneered these type of techniques. Unfortunately I don’t see this being fixed anytime soon

And now Microsoft is supported in every thread by an army of stan bots.

What is this, 2007?

I wonder if this is something AI could figure out. Some sort of file converter that can load the doc in office 365 and ‘figure out’ how what tomfoolery was used this time.