The 14th Anniversary of Our Foundation

17 February 2026 marks the 14th anniversary of The Document Foundation’s recognition as a non-profit organisation under German law. The foundation is focused on developing free and open-source software for individual productivity.

This focus has guided the development of LibreOffice and the software tools for liberating proprietary formats released by the Document Liberation Project. These tools are used by LibreOffice and other open-source and proprietary software.

This growth would never have been possible without the invaluable contributions of the many individuals and companies that have been involved over the years. Today, we celebrate this important milestone and prepare for further growth.

Indeed, given the current geopolitical situation and the push towards digital sovereignty — or independence from major US technology companies — the educational function of LibreOffice and the Open Document Format standard is more important and relevant than ever.

The open-source engine of LibreOffice, known as LibreOffice Technology, is now the only development platform for software solutions — desktop, mobile, or cloud — that can guarantee users true independence from companies and total control over their content, now and forever.

This is all thanks to the principles that have guided The Document Foundation since day one and will continue to provide a reference point for the project’s future evolution.

Why ODF and not OOXML

Many interpreted the last article in this series as an attack on Microsoft for using the OOXML format against users’ interests. However, this was only one of my objectives, as I also wanted to raise users’ awareness of fake open-source software, such as OnlyOffice, which partners with Microsoft in a strategy to lock users in.

Users are already aware of the advantages of standard, open formats because they access sites every day whose content is accessible thanks to the HTML format. This is a standard, open format that was first developed and then defended by its inventor, Tim Berners-Lee. He prevented Microsoft from transforming it into a proprietary format with Internet Explorer 6. This forced users to have two versions of a site: one in a standard format and one in a proprietary format.

Fortunately, Microsoft’s strategy failed in the case of HTML because the W3C – unlike the ISO – never recognised the changes to the format “forced” by Internet Explorer as valid. This was because Internet Explorer did not display sites in the standard format correctly. Ultimately, this forced the company to develop a browser that complies with all standards, thus allowing users to choose their preferred browser to access any site.

Had the same thing happened with OOXML, which was recognised by ISO as a standard despite never having been one, users today would be forced to use the Microsoft browser to view sites correctly and would have to tolerate problems with other browsers. The same applies if they want to read and write DOCX, XLSX and PPTX files with open-source software.

However, using a proprietary format for documents also has other drawbacks for users. In this way, they entrust the keys to their own content to someone they do not know, whose interests differ from their own. In the best case scenario, the content is shared, and in the worst case scenario, it is at risk, as the Chief Prosecutor of the International Court of Justice unfortunately learned when Microsoft closed his email account on the orders of the President of the United States.

The same could happen to users of Microsoft 365 if the proprietary format were modified to render it unreadable or readable only by those with a specific version of the software. Is this something that could never happen? Why live with doubt when a standard, open format is available that no country or company can use as a weapon and which anyone can access using software that handles it correctly?

LibreOffice currently handles ODF files perfectly and handles OOXML files better than Windows 365 and other software handle ODF files. Poor handling of ODF files “forces” users towards OOXML files, thus pushing them towards lock-in and protecting a business worth around $30 billion (because lock-in functions like a pair of handcuffs).

We would like all software to adopt ODF as the reference format and handle it correctly in order to offer users true freedom of choice based on software functionality — as would be right in a world based on free competition and innovation, at least in theory.

Celebrating “I love Free Software day”

I love FS Day banner

LibreOffice is free software – but “free” is about way more than just being zero-cost. It’s about giving users fundamental freedoms in how they run, share, study and improve their software and computers – giving control back to them.

Four freedoms infographic: run, share, study and improve

For example, the source code for LibreOffice – that is, the human-readable “recipe” behind the program – is available for everyone to see, study and modify. You can download this code, see what it does, change it for your needs, and then turn it back into an executable version for your computer. Many hundreds of people have done this already, contributing back important changes and updates to LibreOffice. And then you’re free to share the changes with other users.

This is in contrast to most other office suites, which don’t give users these freedoms; they are “closed”, so users can’t look under the hood, can’t study how they work, can’t make changes, and can’t share the software. Users become restricted and trapped, controlled by and locked into specific software from a specific company – the very opposite of freedom.

So today, on “I love Free Software Day“, we at The Document Foundation would like to say a huge thank you to everyone who works on free software such as LibreOffice. Whether you’re involved in development, QA, design, translations, marketing, infrastructure or any other projects – we ❤️ your support.

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.

LibreOffice project and community recap: January 2026

Monthly recap banner

Here’s our summary of updates, events and activities in the LibreOffice project in the last four weeks – click the links to learn more…

Banner saying Updated Conflict of Interest policy

ODF logo

  • Then there was the LibreOffice Podcast, Episode #6 – discussing language support with Jonathan Clark from TDF. (The episode is also available on PeerTube.)

Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party.

YouTube privacy policy

If you accept this notice, your choice will be saved and the page will refresh.

  • Finally, we prepared for FOSDEM 2026 which took place in Brussels. More about the community’s activities there soon!

LibreOffice merchandise at FOSDEM

Like what we do? Support our community with a donation – or join our community and help to make LibreOffice even better! Also keep in touch – follow us on Mastodon, Bluesky, X (formerly Twitter), Reddit and Facebook.

Video: New features in LibreOffice 26.2

Here’s a selection of new features in LibreOffice 26.2, which we released on Wednesday. (This video is also available on PeerTube.)

Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party.

YouTube privacy policy

If you accept this notice, your choice will be saved and the page will refresh.