Dear Europe: Germany has shown the way forward, by making the Open Document Format (ODF) mandatory within its sovereign digital infrastructure.

[david_chisnall@infosec.exchange]

@mkljczk @jonxion @libreoffice

It's been many years since I actually read the specifications, but I was not convinced that ODF was particularly good in this regard this when I did.

OOXML had a bunch of things like the infamous 'typeset like Word 97' entry, but they were clearly marked in OOXML as for legacy compatibility (like emoji in Unicode, until the Unicode Consortium went silly). It also has a bunch of things like assuming everyone knows how the Windows GDI drawing model works. It is an objectively terrible standard.

ODF and OOXML were both rushed through standardisation too quickly and both were bad specifications.

ODF was much shorter than OOXML and that was partly because a lot of things were underspecified, people implementing it just did what OpenOffice did and had to use OpenOffice as a reference because it was the only way to know what you needed.

It is uncontroversial to say that OOXML is terrible. But it is a logical fallacy to say 'X is bad, Y is not X, therefore Y is good.

[martinrust@infosec.exchange]

@libreoffice We really did that? Hard to believe.

[f800gecko@mastodon.online]

@libreoffice

All well and good until citizens in places like the UK, Canada, America, et. al., start demanding clean drinking water for all from their taps...

[tatus_ua@mastodon.social]

@libreoffice, мої вітання!

[chewie@mammut.gogreenit.net]

@f800gecko @libreoffice huh? What has that got to do with document formats?

[avuko@infosec.exchange]

@david_chisnall @mkljczk @jonxion @libreoffice No "layout before format before content" document type is ever good. But that's besides the point at this stage. Really happy at least one more vendor lock-in tool is off the table.

Now for the rest of Europe to truly adopt this (both odt and ods).

[savera@mastodon.sdf.org]

@libreoffice that’s something many countries and even counties in the US can get behind. Especially when they come asking for tax revenues to fund vector control of the #anopheles mosqiito

[d1@autistics.life]

@libreoffice #Canada is pretty much hopeless in this regard, sorry. I wish it were otherwise! Alas, it's pretty much no #elbowsUp, unless it's a selection between two competing whiskey bottles on a liquor store shelf - one being American whiskey, the other #Canadian whiskey. Prove me wrong, Canada! Canadians will smash each other's teeth out in a hockey fight, but there will be no changing of Office software on the office computers!

[lumiukko@metalhead.club]

@libreoffice as afar as I can see it (in the document by the IT-Planungsrat), this is only one of several formats for "semantic technologies" with the aim "networking, exchange and retrieval of data" [my translation]. Other formats in that group are RDF, OWL, JSON, XML, CSV... this is very broad... am I missing a document describing specific use cases?

and on a side-note: listing CSV here is showing how broad this category is, so I really hope there is something more specific.

[vepr_jako_pepr@mastodon.social]

@libreoffice sovereignty is only liberatory for the individual, a republic or anything worse weilding it is a mistep.
I am for the move away from microsoft but digital sovereignty is digital nationalism

[holothuroid@rollenspiel.social]

@lumiukko

The difference I can imagine is that office workers do not "write" XML and json. Those are things computers talk with between themselves. And people in software have used them already.

@libreoffice

[swggrkllr3rd@mastodon.world]

@libreoffice LibreTranslate not working.

[libreoffice@fosstodon.org]

@swggrkllr3rd Are you talking about https://libretranslate.com ? Then if so, you need to talk to them about it. (That's not from us.)

[swggrkllr3rd@mastodon.world]

@libreoffice thanks.