@libreoffice This has been the truth in multiple countries for some time, including in Portugal, but the governments don't always follow their own mandates for themselves. In Portugal @ansol monitors violation of this type of mandate for government institutions:
O Regulamento Nacional de Interoperabilidade Digital, publicado como uma Resolução do Conselho de Ministros na sequência da lei 36/2011, deveria ter sido actualizado em 2015, mas a publicação da sua revisão só ocorreu em 2018, e está disponível no Diário da República.
@DiogoConstantino @libreoffice @ansol We’ve seen it happen here in Germany—in Munich, to be exact. For 13 years, the city government had relied on Linux. For 13 years, apart from a few minor issues, there were no complaints. Then a new mayor came along, along with Microsoft and a big black briefcase, promising to move the company’s German headquarters to Munich if the city switched to Windows.
Well, what can I say? Munich is once again in the hands of the rip-off artists from Redmond.
@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.
@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).
Unfortunately, I keep reading about open-source software advocates who happily use Microsoft’s proprietary DOCX, XLSX and PPTX formats for their documents and therefore prefer proprietary software such as OnlyOffice to LibreOffice. Others write outrageous things such as: “OOXML is a standard format, and we have to accept it.” I would therefore like to take this opportunity to clarify, once and for all, why OOXML has never been, is not, and will never be a standard format unless Microsoft decides to completely redesign its office applications. I consider this impossible in light of past decisions, such as Excel’s inability to handle elements of the human genome properly. This forced the scientific community to change the names of these elements due to Microsoft’s refusal to fix an obvious Excel bug. In other words, because of Microsoft, all of us citizens of the world have been affected by the change of the names of some elements of our genome, with all that this entails for scientific research and, consequently, for the treatment of genetic diseases. This is an enormously important fact that has not received sufficient publicity in the media, but it illustrates how willing Microsoft is to overlook everything for its own
@libreoffice @jonxion the 2018 presentation is interesting, lots of good details. OOXML crudely reinventing so many other standards, like SVG, proves why it's problematic.
All I could think was, "So LibreOffice had to implement all of this for its .docx importer?!" Hats off to the devs who worked on that.
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...
@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.
Knut Branson
LibreOffice
Diogo Constantino
holzdiebimeinsatz
JonXioN
nicole mikołajczyk
David Chisnall (*Now with 50% more sarcasm!*)
⠠⠵ avuko
Chris Hayes
Wintergreen
Herman 🇪🇺🇺🇦🇾🇪🍋
Pinetrees
Peet Tet.....
Erik Play2Learn
zbrando
Martin Rust
Kyle Memoir 🍉🐧
Chewie
Tatus
Savera
Owl Eyes
Lumiukko