Euro-Office: sovereign in name only, or in reality too?

The announcement of the Euro-Office is welcome news. The coalition is credible, the governance is sound and the timing is perfect. Europe needs office software, and The Document Foundation is delighted to see such significant players allocating resources to make it happen.

However, we have a question. It is not meant to be hostile, but it is the only question that matters.

What is the native document format of Euro-Office?

The press release promises full compatibility with Microsoft formats. We are well aware of the logic behind migration: organisations moving away from Microsoft need to be certain that their documents will survive the transition. But “full compatibility with Microsoft formats” is certainly not a definition of sovereignty, but rather the definition of a different kind of dependency.

OOXML is a format designed, controlled and managed solely by Microsoft. Building a European office suite prioritising compatibility with OOXML means ensuring that the European document infrastructure remains subordinate to architectural decisions made in Redmond. The hosting moves to Europe, but the lock-in remains in Redmond.

The alternative exists, is mature and is a law in several European jurisdictions. ODF, the Open Document Format, is an ISO standard developed through an open and transparent process, which is not controlled or managed by a company. The German Deutschland-Stack has made it mandatory, and the EU Commission has approved it. It is not the LibreOffice format, but a European public good.

The Euro-Office press release does not mention ODF even once.

We are not asking Euro-Office to abandon support for Microsoft’s proprietary format. LibreOffice itself reads and writes OOXML: compatibility is a necessity for users, not an ideological concession. We are asking whether ODF will be the native format, the one in which documents are created, archived and exchanged between European public administrations.

This distinction is fundamental, and the time to define the native document format is now, before the architecture is finalised and the implementations take place. If necessary, we are here to help with the deployment of the ODF standard as native document format.

The coalition has the credibility and resources to build something truly innovative. We hope it will use them to build a project of sovereignty and not merely a tool for server migration, flying a European flag but with a lock-in firmly rooted in Redmond.

The Document Foundation is a non-profit foundation and the home of LibreOffice, the world’s leading open-source office suite. LibreOffice implements ODF as its native format and supports a wide range of document formats, including the import and export of OOXML.

Open Letter to European Citizens

The door to digital sovereignty is open, please come in

For decades, a community of developers, activists, researchers and public officials has quietly worked on the idea that free and open-source software based on open standards is not only the best technical choice, but also the only one compatible with democratic governance.

We have created the necessary tools, overseen migrations and provided user training. We have also drafted policy documents and presented them to committees.

We have documented the consequences of public documents being readable only by software developed in a single country, managed by a single company and subject to the laws of a different jurisdiction, as well as the commercial decisions of a board of directors.

The French gendarmerie, the Austrian Ministry of Defence and the German state of Schleswig-Holstein – to name but a few examples – have taken action, alongside regions, provinces and cities across Europe.

We have always been here, and not with a product to sell, but with the knowledge, patience and sincere conviction that public institutions belong to the public, and that this also applies to their digital infrastructure.

Sometimes we were listened to, but far more often we were merely tolerated, at best with a smile that seemed to say: “I know, but what can I do about this?”

And now, suddenly, the situation has changed, and not because the arguments have changed – there was no need for that – nor because the technology has changed, as it was already excellent.

The situation has changed because the geopolitical balance has shifted, and the dependence that once seemed a convenience now appears for what it has always been: a structural vulnerability.

We are glad that this moment has arrived, and we like to think that this clarity – which the evidence never managed to achieve – is also down to us, and not just the geopolitical crisis.

But we ask European citizens, and through them those who govern European countries, to understand one extremely important thing: the door to digital sovereignty does not open simply by choosing different software, but by understanding what sovereignty actually entails.

It requires open document formats, not as a preference, but as a legal and technical guarantee that a document produced today will be readable in thirty years’ time, by any compliant application, without the permission of any company. The format is not a detail, but the foundation.

It requires open fonts, because a document displayed differently on different systems is not an interoperable document, regardless of the standard it claims to follow. The display layer is just as important as the data layer.

It requires continuity of expertise: the people and institutions that have carried out this work, often without recognition and sometimes without resources, are not a lobby to be managed but a valuable repository of knowledge to be engaged.

It requires honesty about what “open” means. A coalition that speaks of digital sovereignty but chooses as its default document format one designed to replicate the behaviour of proprietary software is not building sovereignty but a new dependency under a different banner.

We have been here for years, and we will still be here for years to come.

The FLOSS ecosystem did not need a geopolitical crisis to believe in open standards. We have always believed in them, because they are right—technically, legally, and democratically.

Now that Europe is ready, we have just one request: listen to us carefully, unlike what you have done in the past. The lesson is not simply “use free and open-source software”. The lesson is: understand why it is important, and understand it thoroughly.

The tools exist, the knowledge exists, and above all, the community exists.

What happens next will depend solely on you: Europe’s digital sovereignty could become a genuine architectural commitment or remain yet another rebranding of dependency.

We hope, and would like to be sure, that you choose the first option.

Over the coming weeks, four articles will explore these topics in depth: the architecture of document formats, the hidden politics of font rendering, lessons learned from real-world migration experiences, and what a credible European policy on open standards would actually look like. We invite you to read them.

ODF Toolkit Project Announces Release 0.13.0: Last Release Supporting JDK 11

ODF logo

BERLIN, Germany — The ODF Toolkit community is proud to announce the official release of version 0.13.0. This release marks a significant transition point in the project’s history, representing the last release to support JDK 11, with the project pivoting toward modern Java long-term support (LTS) releases.

Release Highlights: Stability and Modernisation

The 0.13.0 release provides a stable, high-performance foundation for programmatic manipulation of ODF 1.2 documents.

  • Final JDK 11 Support: This is the definitive release for users operating on Java 11 environments.
  • Broad Compatibility: Validated across the Java ecosystem on Windows 10, macOS (Apple Silicon M3), and Ubuntu 24.04 LTS.
  • Automated Deployment: GitHub release artefacts are now built automatically with Temurin JDK, ensuring a transparent, reproducible supply chain.

FOSDEM 2026: Setting the Stage for 1.0.0

Following the release, the project’s core developers met in person at FOSDEM in Brussels, using the opportunity to align on the project’s next major milestone. During the event, the team finalised the roadmap for the upcoming 1.0.0 Release Candidate. Discussions focused on resolving the remaining blocking issues in the toolkit’s code-generation engine, paving the way for a more robust and extensible architecture.

Immediate Future: JDK 17 and Apache Jena 5

The project has already moved its development baseline to JDK 17 for the upcoming version, 0.14.0.

  • Apache Jena 5.6.0: The shift to JDK 17 enables integration with the latest Apache Jena library, significantly enhancing the toolkit’s ability to handle document metadata and RDF.
  • Early Access: A 0.14.0-SNAPSHOT release is now available for developers who want to test these new features.

Expanding the Core Team

The project continues to grow its community of maintainers. Following discussions between Michael Stahl, Oliver Rau, and Svante Schubert, Axel Howitz has been granted commit rights, strengthening the project’s long-term sustainability and development capacity. Axel’s contributions since joining last year have been instrumental in maintaining the project’s momentum toward its 1.0.0 goals.

Availability

The ODF Toolkit 0.13.0 is available via the official project page.

About the ODF Toolkit

The ODF Toolkit is a community-driven, open-source Java library for creating, scanning, and manipulating OpenDocument Format (ODF) files. By providing a lightweight API that operates independently of any office suite, it remains a preferred choice for server-side document automation.

European Commission’s use of Microsoft 365 breaches data protection law for EU institutions and bodies

The European Data Protection Supervisor (EDPS) has found that the European Commission (Commission) has breached several provisions of Regulation (EU) 2018/1725, the EU data protection law for EU institutions (EUIs), in its use of Microsoft 365, including those relating to the transfer of personal data outside the EU and the European Economic Area (EEA). The EDPS is imposing corrective measures on the Commission.

In particular, the Commission has failed to provide adequate safeguards to ensure that personal data transferred outside the EU/EEA are afforded the same level of protection as that guaranteed within the EU/EEA.
Furthermore, in its contract with Microsoft, the Commission did not sufficiently specify the types of personal data to be collected and for what explicit and specified purposes when using Microsoft 365. The Commission’s breaches as data controller also relate to data processing, including the transfer of personal data, carried out on its behalf.

The EDPS has therefore decided to order the Commission to suspend, with effect from 9 December 2024, all data flows resulting from the use of Microsoft 365 to Microsoft, its subsidiaries and sub-processors located in countries outside the EU/EEA that are not covered by an adequacy decision.

In effect, the EDPS has confirmed what we have been arguing for years, namely that the only individual productivity solutions that also guarantee data protection and support the concept of Europe’s digital sovereignty – technological independence from the commercial decisions of high-tech companies, especially from the US – are FOSS solutions such as LibreOffice combined with a standard, open and independent data format such as the Open Document Format.

The EDPS, though, has also decided to order the Commission to bring the processing operations resulting from its use of Microsoft 365 into compliance with the EU Regulation 2018/1725. The Commission has until 9 December 2024 to demonstrate compliance with both orders.

The EDPS considers that the corrective measures it imposes (described in the document annex [1]) are appropriate, necessary and proportionate in light of the seriousness and duration of the infringements found.
Many of the infringements found concern all processing operations carried out by the Commission, or on its behalf, when using Microsoft 365, and impact many individuals.

Unfortunately, all the remedies identified by the EDPS relate to Microsoft 365, and therefore do not address the root of the problem by suggesting the use of FOSS solutions such as LibreOffice and the only truly standard, open and independent document format, the Open Document Format.

It is highly likely that Microsoft’s solution will be the usual ‘sticking plaster’ that hides the problem without addressing it, and that the lobbyists – who I am sure are already at work – will make it look appropriate in the eyes of politicians.

And if we continue to protest, knowing that we will not be heard because we do not have the same firepower as the lobbyists of the big US hi-tech companies who are present in Brussels with hundreds of professionals, we will always hear the same thing: “They all do the same…”.

[1] https://www.edps.europa.eu/press-publications/press-news/press-releases/2024/european-commissions-use-microsoft-365-infringes-data-protection-law-eu-institutions-and-bodies_en

Announcing the ODF Toolkit 0.12.0 release

Open Document Format logo

ODF is the Open Document Format, the native format used by LibreOffice (and supported by many other apps too). It has various sub-formats such as .odt for text files, .ods for spreadsheets, and .odp for presentations.

Meanwhile, the ODF Toolkit is a set of Java modules that allow programmatic creation, scanning and manipulation of ODF files. And at the end of last month, the developers announced a new version: 0.12.0!

Big changes include a new ODF 1.3 mimetype “Text master template”, while the API for Text Selection was completely refactored. In addition, there were many fixes to improve reliability and security.

Check out the full announcement and link to the release notes here

Custom Shape Tutorial

Have you ever tried to draw special and complex shapes beyond the basic offerings of LibreOffice? A custom shape of the Fibonacci spiral defined by its equation and properties with handles to reshape size? Thanks to Regina Henschel, now you have a tutorial for drawing custom shapes of your own and use them in LibreOffice.

Currently, LibreOffice provides a lot of predefined custom shapes. They are grouped to the sets ‘Basic Shapes’, ‘Block Arrows’, ‘Symbol Shapes’, ‘Stars and Banners’, ‘Callouts’, and ‘Flowchart’. And all shapes from the ‘Fontwork Gallery’ are custom shapes too. But you can do more, much more.

Custom Shapes Tutorial

(more…)