Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
Microsoft IT

LibreOffice Calls Out Microsoft For Using 'Complex' File Formats To Lock in Office Users (neowin.net) 81

LibreOffice has accused Microsoft of intentionally using "unnecessarily complex" file formats to lock in Office users, claiming the company weaponizes its Office Open XML schema to create barriers for competitors. The open-source office suite argued that Microsoft's OOXML format includes deeply nested structures with non-intuitive naming conventions and numerous optional elements that make implementation difficult for developers outside Microsoft.

LibreOffice compared the situation to a railway system where tracks are public but one company's control system is so convoluted that competitors cannot build compatible trains.

LibreOffice Calls Out Microsoft For Using 'Complex' File Formats To Lock in Office Users

Comments Filter:
  • The only thing locking anyone in is ignorance. So spread the word! Wait, don't...
  • Format (Score:5, Insightful)

    by JBMcB ( 73720 ) on Friday July 18, 2025 @02:29PM (#65529824)

    So you have a file format going back almost 20 years, that supports embedding almost any kind of content anywhere, that has had new features bolted on almost constantly, and also is backwards compatible so that anything not using a new feature is readable by older applications, and is also forward-compatible so newer versions of the application can render these documents accurately. And people complain that said file format is too complex?

    For a comparison, go read up on how complex the TIFF standard is, and that is, basically, a bunch of numbers corresponding to color values in a bitmap. The ancient base-standard document is 120 pages long.

    • Yeah. pretty sure it is not intentional. It's just years of kruft stacking on top of each other. They could probably clean up the specification, but it would break stuff left and right. One thing Microsoft actually does well is backwards compatibility. Sometimes you just gotta clean house though.
      • Re:Format (Score:5, Interesting)

        by Anonymous Coward on Friday July 18, 2025 @02:56PM (#65529914)

        One thing Microsoft actually does well is backwards compatibility.

        Odd, I haven't seen that. I have tons of old powerpoint presentations where half the images are replaced by a huge red "X" because the new powerpoint won't deal with them.

        When I need to open old files, I use Libre Office.

        --
        (apologies for posting AC-- had a few mod points to burn).

      • Can't agree on "Microsoft actually does well is backwards compatibility". Have you seen the hoolahoops to jump through to get some old game to work on current Windows? Or old printer, from the days when they didn't break after couple of years. Also regarding Word, I remember when USB sticks came around and MS changed some .doc format - every second coworker got confused when one Word version could not open others file. I had Openoffice then and could not fathom all the fuss, it just opened all of them.
    • Yes that explains the complexity, but not the ongoing bad naming of the options.
      • That's the weakest complaint. If the bad option names are documented, so what? You have to read the spec to know what to do anyway. If they aren't documented, complain about that.

      • Variable names and what constitutes good or bad ones have been a point of contention and flame wars since most of us were toddlers, or even not even born yet. Remember those crusty old neckbeard rants we used to find on BBSs, usenet, and gopher about how "real programmers" don't eat quiche, program in Pascal, can diagnose bugs by watching das blinkenlights on the front panel, and write and deploy their code fixes by using the bit toggles on said front panel to directly change the assembly in-memory? Yeah.

    • by dvice ( 6309704 )

      I once had to re-implement an application based on specification document. When doing that, several times I encountered a situation where I noticed that the documentation was not specific enough. I then realized that it would be extremely helpful if a specification would come with a sample code that implements it.

    • That's one of the two big complaints about OOXML: that Microsoft took their old binary formats (which, as you alluded in your post, were a essentially memory dump of the application's memory with new features overlaid on top of old ones), gave the fields meaningless names, and dumped them into XML. This was beneficial to Microsoft because they didn't have to write any complex conversion code (from the old binary formats to OOXML and vice-versa), but it's not the ISO-class format they promised the world (yet
    • by ratbag ( 65209 )

      Can't find any concrete references (too lazy). But I remember many of us (here on Slashdot and other dens of iniquity) laughing at the insanity of the OOXML format when it first emerged. Especially given the pre-existence of ODF.

      The Wikipedia page [wikipedia.org] does tell us the number of pages the standard runs to - it's greater than 120.

      It also suggests there have only been two major releases of the format and the problems seem to have been baked in from day one.

    • Well, they just could invent their own sane XML format (is that possible? Sane and XML?) ...
      And then use XSLT to either transform the bad bad M$ format into their sane one, or into the other direction ... /me runs and hides

    • For a comparison, go read up on how complex the TIFF standard is [...] 120 pages long.

      A comparison needs information of at least two items.

      Here is the length of the specifications for each document format:

      • Latest OOXML: 7000+ pages.
      • Latest Open Document Format: ~1050 pages

      Add on top of that misleading naming schemes and OOXML has a considerable higher complexity.

    • What the hell is up with pasting either a portion of another Word document or pasting part of an Excel spreadsheet into Word? It's the stuff of nightmares
  • by echo123 ( 1266692 ) on Friday July 18, 2025 @02:32PM (#65529828)

    Q: How many Microsoft engineers does it take to change a light bulb?

    A: Zero. Microsoft simply declares Darkness the new Standard.

  • by v1 ( 525388 ) on Friday July 18, 2025 @02:34PM (#65529836) Homepage Journal

    I've spent time on the difficult end of black-boxing a BINARY file format. You jokers with your XML and LABELS have it faaaaaar too easy. Here, I'll tell you my secret:

    Gather as many saved files as you can, from as diverse of a group as possible. (there is NO upper limit, literally grab as many as you can) Write a short little test script to import and then export every single one. Then compare the export with the original. Refer the mismatches to the dev. I had over 1,000 test files in my suite, and in the initial release only a SINGLE flag was missed, because of all those test files, nobody implemented that feature and the dev guessed the storage would be the same as EVERY other one. (it turned out to be quite unique)

    Oh and as for XML depth.... it's RECURSION. It literally does not care if it's 5 levels or 200 levels deep. (unless your IDE has a truly pathetic stack size)

    So it's not difficult. QYB.

  • My stars and garters! Fetch me my fainting goats!

    Every now and then nerds will realize that their computer is kind of suck because we don't enforce antitrust law but we always go back to sleep.
  • by dfn5 ( 524972 ) on Friday July 18, 2025 @02:37PM (#65529848) Journal

    \documentclass{slashdot}
    \begin{document}

    \LaTex is the one true format. All others are trash.

    \end{document}

    • by gweihir ( 88907 )

      Indeed. And ODF is not that much worse.

    • Yeah, after you get used to it, LaTex works quite well. I do my manuals in it and have for years. Originally I used Frame back when Sun was a thing. Both Frame and LaTex have one huge advantage over MS, or at least used to. Size. You can do 3K page docs no problem in LaTex. A friend who was a tech writer would moan bitterly about MS products crashing if the client demanded she use MS.
      • I think it was called FrameMaker.

        It was so simple to invent a format for a text block, give it a name, and apply it where needed.

        No idea why no office suit can do that 30 years later ...

        • Yes full name was FrameMaker. Adobe bought them and screwed it up. It also had a real API, could dump out in "maker" text format which you could edit or process and reload. We would have pubs put markers in FrameMaker and then, FrameViewer, could open and jump to a specific marker when you pressed the help button in the software we were developing. FrameViewer was either free or low cost, can't remember anymore. Frame was light years ahead of microsoft. I do something similar with LaTex. There the markers I
  • ... is the name of the Free Software anthem. Maybe not fair to lump all projects together but we're cutting really close to stone thrown from a glass house.

    • ^This^

      That's always been my issue with the *Nix stuff... sure, it might run fine and be more stable (and if a user has the programming knowledge, completely editable to whatever they can dream up), but for the vast majority, it's too complex to get it running without having to read a document the size of the Bible, let alone open a file made in Office 2016 or whatever (whether it's a PowerPoint or Word or spreadsheet document).
      While FOSS is a great idea, the problem is compatibility.
      The general purpose of a

      • This is about LibreOffice. There's nothing complex about it, or nothing more complex than MS Office. Try it, it just works. The interface is convergent with at least the older versions of MS Office (I don't know the more recent so I can't tell about them).
        Compatibility... have you tried LibreOffice? It is MORE compatible with (older) MS Office documents than MS Office itself.

  • Microsoft's OOXML format includes deeply nested structures with non-intuitive naming conventions and numerous optional elements that make implementation difficult for developers outside Microsoft.

    Just have Copilot refactor and document the format.

  • by gweihir ( 88907 ) on Friday July 18, 2025 @02:53PM (#65529906)

    Because anti-competitive behavior is just that: Not competing on merit but instead scamming users and competitors. I hope there will be another massive fine from the EU incoming. Because obviously, there is absolutely no need to do it this way on the tech side.

    • It sounds like you're venting about a Microsoft-branded bug up your ass until the last sentence, which makes it seem like it's all been sarcasm. Was that your intent or am I reading you wrong?
      • by gweihir ( 88907 )

        You are reading me wrong. The human endeavor is advanced by competing on merit. It is hampered by other forms of competition. You, know, commercial/evil.

  • I doubt it.

    In my experience, the most complicated code comes from the hands of lower-skilled developers. It takes skill, knowledge, and intelligence, to produce code or file formats that are elegant and usable.

    To the extent that they're right about the format, I highly doubt that it was *deliberately* complex.

  • Remember .xls, .doc, and .ppt files? They were both complicated and binary. The BIFF format, used in Excel, had a binary format built on record identifiers and length indicators, followed by variable-length data where each record type had an entirely different format from the other record types. Further, if you embedded a chart or image in an Excel file, the bytes of that blob were broken up into chunks and interspersed in the file at almost random intervals, with individual blobs cut right in the middle of

  • by Mirnotoriety ( 10462951 ) on Friday July 18, 2025 @03:39PM (#65530010)
    From: Bill Gates
    Sent: Monday, December 07 1998 8:28 PM
    To: Jon DeVann; Steven Sinofsky; Bill Neukom (LCA)
    Cc: John Mason (LCA)
    Subject: FW: free desktop suite from star

    Importance: Low

    Attorney client privileged

    An Interesting development...

    At some point we will have to consider the patents they violate. [gotthefacts.org]
  • by Anne Thwacks ( 531696 ) on Friday July 18, 2025 @03:51PM (#65530040)
    Mandate an open file format so their data is not held to ransom.

    Hint: Open Document formats are your friend and MS formats are the work of the devil.

  • I had a coworker ~15 years ago who hated MS to the point he used OpenOffice even though the company provided a license of Office 200x. Invariably, we would need to share documents, presentations, and spreadsheets and all worked fine until he got sent a copy to update. Every single time he touch a doc and sent it to anyone, the formatting and other components would get off. He'd complain MS wasn't following the correct format for Word/Excel/PowerPoint.

    When we told him the "format" for their tools is WHATEVER

    • That was long ago. I'm literally that guy today and there are no problems. I edit and send files back to colleagues, customers, managers, CEO. I use to use my separate MS Office laptop and check if my files opened fine, I don't do it anymore. There are no complains, and people don't even know I'm not using same things as them.

      I do have a rare issue where LO incorrectly reads the crop settings of pictures from particular DOCX files and I need to set the crop manually before saving. That's about it.

    • And ironically, I just looked him up on LinkedIn and he is a senior consultant for Microsoft!!!
      In which phase is he? Embrace?
      I hope he is not going to suffer from "Stockholm Syndrom" before he gets into the final phase!

  • This battle was waged. OOXML won. It's hacky, it's the default, there is probably better, but nobody cares enough to force the use of ODT. This is about working documents in organizations. The read only archives are all PDF.

    If you want to displace those use cases, you need to have product that brings its own values and advantages to Office 365 users. No, being free isn't enough. Office and Windows is eighty bucks at most for a user per month. It doesn't take much to recoup that cost in organizations, which

  • ...Microsoft doing everything in its power to make sure it remains incompatible with the rest of the world.

    Who would have thought?

  • Microsoft is doing these things since the very early days⦠look at memory management interrupt calling of MSDOS! ðY' it was deliberately undocumented even if it was the primary vehicle for the task. No technical cause, just pure business greed. I was a teenager back then and now good enough to win global obfuscated competitions, so I literally grew up with Microsoftâ(TM)s shenanigans! Shame them at every corner.
  • My company doesn't have the latest version of Office, and the version dates we do have can vary by a few years, so I just save everything I touch in a 15 year old format, because the new format provides nothing I need for 99.9% of documents, and the remaining 0.1% can be pdf. I use LibreOffice. Others use Word 2016 or 2012, and none of it particularly matters.

    For governments, the things LibreOffice complains about with OOXML ought to be security concerns. If you can't know how to duplicate what's correct
  • When OpenOffice/LibreOffice were on the verge of winning major contracts, due to their open formats, Microsoft invented their own XML-based format. Anyone who has looked into it knows that it is an abomination. This is not news.

    Add in some of the abstruse specifications, for example, requiring apps to reproduce an early Excel bug where it screwed up dates (because it thought 1900 was a leap year).

  • I haven't had a word/office license, or even been plagued with a windows machine of any kind, since 5 jobs ago. Maybe the stodgy old legacy grandfathers of tech still use office and windows. But all the startups I've worked for since have all used gSuite (or Google Workspace after the re-branding) for everything the house of gates used to provide. Endpoints have been all either Mac or Linux laptops in that time. At my current startup, windows machines aren't even allowed on the office wifi. And the onl

"I have five dollars for each of you." -- Bernhard Goetz

Working...