nojhan, Cassandre de l’analyse systémique2d ago

Après avoir profité de l’open-source pour se tailler des parts de marché, tout en minant sa licence avec des clauses dignes d’un patent-trolleur pour continuer à imposer un format pseudo-ouvert corrompu par Microsoft, ONLYOFFICE passe à l’attaque contre son principal rival (Nextcloud), qui l’avait exclu d’un partenariat stratégique.
https://www.onlyoffice.com/blog/2026/03/onlyoffice-flags-license-violations-in-euro-office-project-by-nextcloud-and-ionos
Nextcloud, qui venait justement de passer son produit phare en format-Microsoft-par-défaut — contre l’avis de sa communauté — par pure flemme intellectuelle.

#nextcloud #onlyoffice #libreoffice #opendocument #logicielLibre #openSource

ONLYOFFICE flags license violations in “Euro-Office” project

The “Euro-Office” initiative is an evident and material violation of ONLYOFFICE licensing terms and principles of international intellectual property law.

ONLYOFFICE Blog
Job Bautista3d ago
Has anyone been able to get a valid conforming #ODF document result out of The Document Foundation's ODF Validator with an ODT file created by a non-OpenOffice derived word processor? It seems the validator just never finds a valid result with an ODT document produced by WordPad (supposedly ODF 1.1, yet not versioned at all), MS Word 2019 (supposedly ODF 1.2) and SoftMaker's TextMaker 2024 (more probably ODF 1.2 or 1.3, but versioned 1.0).

https://odfvalidator.org/

#OpenDocument #LibreOffice #TheDocumentFoundation #OpenOffice #OpenOfficeOrg #OOO #WordPad #Word #MSOffice #MicrosoftOffice #MSWord #MicrosoftWord #SoftMaker #TextMaker
ODF Validator 1.4

ODFToolkit

Show threadYesterday's Rose5d ago

I spent a considerable time fixing up the Ruby install.

Fortunately the development time for the actual feature went much, much smoother.

Basically I wanted to make the #DVD / #BluRay database export a complete list of discs as #OpenDocument spreadsheet, for smoother printing 'n' stuff.

The actual part of adding that feature was actually pretty easy. Just had to learn about the respond_to mechanics a bit and use rodf to generate the ODS file. As we say here in Rails land, "whoops, done". (Well the ODS file looks ugly, but it will suffice for now.)

brume ⏚ 🤔 ⛵ 🐧 ☮️ 🇵🇸 🍉5d ago

RE: https://fosstodon.org/@libreoffice/116305551484076793

Le format #OpenDocument (ODF), (les fichiers .odt, .ods, etc) est de plus en plus adopté. C'est ça l'avenir : un format totalement ouvert, documenté et normalisé, contrairement au format #Microsoft OOXML "Transitional" qui est un format défectueux, mal documenté et non libre utilisé par défaut par MS Office.

Défendez votre liberté, la pérennité et la qualité de vos documents, et n'utilisez plus les .docx ni les .xslsx, quelle que soit votre suite bureautique, faites le choix du bon format lors de l'enregistrement de votre document.

#FormatsOuverts #LogicielsLibres #NoGAFAM

Fmutix5d ago

Das hört sich nach einem guten Schritt in die richtige Richtung an:
ODF für die öffentliche Verwaltung in Deutschland vorgeschrieben - LinuxNews.de https://linuxnews.de/odf-fuer-die-oeffentliche-verwaltung-in-deutschland-vorgeschrieben/

#opensource #oeffentlicheVerwaltung #opendocument

ODF für die öffentliche Verwaltung in Deutschland vorgeschrieben

Der Begriff »Digitale Souveränität« ist mittlerweile inflationär. Die verpflichtende Nutzung von ODF für die gesamte Verwaltung ab 2027 könnte ihn mit etwas…

LinuxNews.de
Show threadmkj6d ago

I found https://odftoolkit.org/conformance/ODFValidator.html which looks to be roughly what I'm looking for at a *technical* level. Unfortunately it points at quite a lot that's not strict ODF compliant. When setting the save format to 1.4 instead of 1.4 Extended in LibreOffice, validation comes out clean, as expected; but I don't see any ready indication of what, if anything, I've done which is lost in the process, so that part of my question remains. (The resulting file is *much* smaller.)

#OpenDocument #ODF #LibreOffice

ODF Toolkit

mkj6d ago

For a given document, saved as OpenDocument, in LibreOffice, is there a hopefully convenient way to *locally* (no cloud service) find out which (if any) features it uses which can not be represented in the strict standard ODF format but only in Extended? (For example: if one switches from ODF "1.4 Extended" to "1.4" what's lost?)

It's fine if it's just a list like "this document uses the following features somewhere that require Extended".

#DuckDuckFedi #AskFedi #LibreOffice #OpenDocument #ODF

Show threadnojhan, Cassandre de l’analyse systémiqueMar 25

Since the NextCloud Office maintainers have not taken into account the arguments against their decision to use Microsoft OOXML as the default format, I submitted a pull request with code that sets OpenDocument as the default format:
https://github.com/nextcloud/richdocuments/pull/5516
I strongly encourage you to retweet, upvote, and comment on this PR, which will be harder to ignore than a “resolved” issue.

Edit: The maintainer (who is clearly terrible at managing comm) has closed the PR and directed people to the issue, which remains open for votes and comments↴
https://github.com/nextcloud/richdocuments/issues/4812#issuecomment-4129406883

Ping @tdforg @libreoffice @nextcloud

#NextCloud #RichDocuments #OpenDocument #microsoft #FreeSoftware #LibreOffice #sovereign

fix(format): makes OpenDocument the default format by nojhan · Pull Request #5516 · nextcloud/richdocuments

This reverts commit 8b464b6 by setting "od[fp]" instead of "ooxml" as a default. Following several downvotes and arguments against making the Microsoft-controlled format OOXML a...

GitHub
nojhan, Cassandre de l’analyse systémiqueMar 25

Comme les mainteneurs de NextCloud Office n'ont pas prêté attention aux arguments contre leur décision d'utiliser Microsoft-OOXML comme format par défaut, j'ai fait une pull-request avec le code qui permet d'avoir le format OpenDocument par défaut :
https://github.com/nextcloud/richdocuments/pull/5516
Je vous encourage fortement à retooter, à voter et à commenter sous cette PR, qui sera plus difficile à ignorer qu'une issue « résolue ».

Edit : le mainteneur (décidemment nul en gestion de comm) a fermé la PR et redirigé les gens vers l’issue, qui elle reste ouverte aux votes et commentaires ↴
https://github.com/nextcloud/richdocuments/issues/4812#issuecomment-4129406883

Ping @tdforg @libreoffice @nextcloud

#NextCloud #RichDocuments #OpenDocument #microsoft #LogicielLibre #LibreOffice #souveraineté

fix(format): makes OpenDocument the default format by nojhan · Pull Request #5516 · nextcloud/richdocuments

This reverts commit 8b464b6 by setting "od[fp]" instead of "ooxml" as a default. Following several downvotes and arguments against making the Microsoft-controlled format OOXML a...

GitHub
Ückück  ​ Mar 25

Oha, spannend! Ich hab es noch nicht wirklich durchdrungen, aber schaut mal her:

BIG NEWS: Germany has just made the standard Open Document Format (ODF) mandatory
https://blog.documentfoundation.org/blog/2026/03/20/big-news-germany-has-just-made-odf-mandatory/

#OpenDocument #odf

BIG NEWS: Germany has just made the standard Open Document Format (ODF) mandatory - TDF Community Blog

The German federal government has quietly taken an extremely significant step: hidden amongst the technical specifications of the Deutschland-Stack – the rules that will govern the sovereign digital infrastructure supporting public administration at all levels of government, from federal ministries to local council offices – there is a short but highly significant line. Under the technological pillar “Semantic technologies and real-time analysis”, the document mandates the use of just two document formats: ODF and PDF/UA. That is all. Two open, vendor-neutral formats, defined by international standardisation bodies. OOXML, Microsoft’s closed, proprietary format, is not on the list. What is the Deutschland-Stack? The Deutschland-Stack is the German federal government’s project for a sovereign, interoperable digital infrastructure that complies with European standards. It is neither a pilot project nor a policy discussion paper, but the result of a coordinated decision between the Digital Minister, the Federal Chancellery and the Chancellor, backed by the coalition agreement. The document sets out the standards that will govern how all federal public administrations, at all levels, build, procure and manage their digital systems, and envisages concrete implementation by 2028. It is worth reading its architectural principles carefully. “Made in the EU first.” Reduction of lock-in effects.

TDF Community Blog