Projects selected for LibreOffice in the Google Summer of Code 2026

The LibreOffice Google Summer of Code projects have been selected for 2026.

  • Aya Jamal – OpenType MATH: this project aims to add support for OpenType fonts that contain a MATH table. Data from the MATH table will be used to layout math formulas.
  • Manish Bera – Improve word processor test coverage: Writer is the most complex application in LibreOffice. The tests written in the scope of this project will make for a better developer experience. One aim is to restart the automated generation of LCOV test coverage reports.
  • Jesus Solis – JPEG XL import support: while JPEG XL has only recently started to be adopted by web browsers, it is already used in fields such as medical imaging, professional photography, PDF & EPUB authoring and handling geospatial and archival data. Having support for it in LibreOffice would therefore make for a smoother experience for the users who rely on the format.

Good luck to the contributors – we appreciate their work on these important features and improvements! And thanks to our mentors for assisting them: Khaled Hosny (Alif Type); Jonathan Clark and Xisco Faulí (TDF).

Between August 17 and 24, contributors will submit their code, project summaries, and final evaluations of their mentors. Find out more about the timeline here, and check out more details about the projects on this page.

Twenty Years On, ODF Is Still the Only Open Standard for Office Documents, and the Only One Governments Can Trust

Berlin, 8 May 2026 – Twenty years ago this week, on 3 May 2006, the Open Document Format cleared its Draft International Standard ballot at ISO/IEC JTC 1/SC 34 with unanimous approval. On 30 November 2006 it was published as ISO/IEC 26300. Two decades later, ODF remains what it was on the day of its ratification: the only open, vendor-neutral, freely implementable international standard for office documents in existence.

Everything else on the market is a vendor format with a standards number attached.

That distinction was contested in 2006. It is not contestable in 2026. The competing format pushed through ISO in 2008 – under a fast-track process whose abuses are now part of the documentary record of standards governance – has since splintered into a Strict variant almost no implementation actually uses and a Transitional variant that preserves, by design, the undocumented behaviours of a single vendor’s legacy products. A standard that exists to encode one company’s bugs is not a standard. It is a moat with a certificate.

ODF has no Transitional mode. It has no undocumented behaviours. It has no vendor whose commercial roadmap can quietly rewrite what conformance means. The specification is publicly available at no cost from ISO and from OASIS. The schemas are auditable. The implementations are multiple, independent, and free. This is not advocacy language. It is the working definition of a standard, and ODF is the only office-document format that meets it.

The political weather has finally caught up with the technical reality. Germany’s federal administration has mandated ODF through the Deutschland-Stack. The European Commission’s own services are under sustained pressure – including from this Foundation – to align procurement with the open-standards commitments the Commission itself has signed. Brazil has legislated open formats into its educational system through Lei 15.211/2025. The pattern is the same on every continent where public bodies have stopped to ask the only question that matters: in what format does a society keep its own records, and who decides when that format changes?

For twenty years, the answer to the second question – for any administration that chose ODF – has been: we do. For any administration that chose the alternative, the answer has been: the vendor does, and the administration will be informed.

“ODF is the document format of a public that has decided not to outsource its memory,” said Florian Effenberger, Executive Director of The Document Foundation. “The governments now mandating ODF are not making a technical choice. They are reclaiming a sovereignty they should never have surrendered.”

The implementation landscape reflects the same divide. LibreOffice, developed by The Document Foundation and a global community of contributors, uses ODF as its native format and is the reference implementation of the standard. Collabora Online extends ODF support to enterprise and cloud deployments. Together they constitute the working core of the ODF ecosystem. Other office suites – including those that market themselves with the vocabulary of openness while defaulting to a competitor’s vendor format – are not part of that ecosystem and should not be confused with it.

The Document Foundation will mark the twentieth anniversary across 2026 with a programme of publications, policy briefs, and community events. The LibreOffice Conference will dedicate a full track to ODF, coordinated with the OASIS Technical Committee, which is currently advancing version 1.4 of the specification. Material on the history, the structural design, and the policy implications of ODF will be published throughout the year on the TDF blog.

A standard is worth what it still does after the people who wrote it have moved on. ODF is read, written, and trusted by software none of its original authors imagined, on hardware none of them could have specified, in jurisdictions none of them lobbied. It has aged the way public infrastructure is supposed to age: quietly, reliably, and in everyone’s hands.

That is the anniversary worth marking. Not the certificate from 2006, but the twenty years of evidence since: evidence that the open-standards bet was the right one, that the alternative was the trap its critics warned it would be, and that the governments now choosing ODF are not innovating. They are catching up.

Announcing the new LibreOffice website!

LibreOffice logo, laptop and globe

LibreOffice’s website is the main source of information about the software (and project), and typically has 45,000 – 65,000 visitors every day. It is also the place to download the suite, of course, and make donations to support the community.

Our website was looking rather old and becoming difficult to maintain, so the team at TDF – with help of the wider LibreOffice community – has been working on a redesign, based on newer technology (Hugo, an open source static site generator). This is built on design work from a few years ago – so thanks again to Dan Gallagher, Cat de Leon, Irene Geller, Helen Tran, Zarema Ross and IBIS Design for their help!

And now, the new website is live! It’s currently available in English, Dutch, Spanish, French, Portuguese (Brazil), Finnish, Esperanto, Italian, Kazakh, Ukrainian and Chinese (traditional) – but we’re working on adding more. If you speak a language for which the new website is not yet available, please give us a hand! Join our website mailing list and we can help you to get started. Or start translate immediately in your language: just select your language on this page and select the website project and the “LibreOffice site (Hugo)” component. If you don’t see the component in Weblate, let us know on the mailing list and we’ll add it for your language.

Instructions for using Weblate are on our wiki. And in any case, let us know if you find any glitches or missing links that we can fix. Thank you 😊

Visit the new website

LibreOffice at the Augsburger Linux-Infotag 2026

LibreOffice stand at the Augsburger Linux-Infotag 2026

Most of the work in the LibreOffice project takes place online – in our Git repository, on mailing lists, on IRC and other places. But where possible, we like to meet in-person as well, at events around the world! Last weekend, for instance, we were at the Augsburger Linux-Infotag in southern Germany.

As the name suggests, this event is all about Linux and free and open source software (FOSS). The LibreOffice community was present with a stand, and we had a laptop to demonstrate the software, along with merchandise: flyers giving reasons to use LibreOffice; flyers explaining what The Document Foundation does; stickers; and beer/coffee mats.

LibreOffice stand at the Augsburger Linux-Infotag 2026

Most of the visitors to our stand were already familiar with LibreOffice – as is expected at such an event. But visitors also had lots of questions, like:

  • Where is LibreOffice being widely used now?
  • How can I customise the user interface?
  • Where can I report a bug?

We also talked to several people helping to roll out LibreOffice in companies and local administrations, so we hope to have more news about those migrations soon. Thanks to everyone who stopped by, and our next planned event in Germany is FrOSCon, so see you there!

Thank you, on behalf of ODF

Recently, The Document Foundation published an open letter to European citizens. We asked Euro-Office – the new coalition forming around a European alternative for productivity – whether ODF (the Open Document Format) would be its native document format.

Unfortunately, we have not yet received a reply, and this confirms – at least in part – the suspicion that Euro-Office will join Microsoft’s allies in a strategy to lock in European citizens, who will see their content snatched away by a company that – in words only – presents itself as a defender of digital sovereignty.

With the open letter, we have raised an issue that the general debate is not yet grasping: digital sovereignty is not determined solely by the terms of the licence and the location of the server, but by the format in which documents are created, stored and exchanged.

We were able to pose our question publicly, with confidence, because we represent something extremely solid – support for the single open and standard format: ODF – which has been built up over twenty years by many people, whose names rarely appear in press releases.

The foundations underpinning the political moment

Germany has established by law that ODF is the mandatory format for public administration, whilst the Interoperable Europe Act has made open standards a legal obligation across all EU Member States. Consequently, policymakers in Berlin and Brussels are now championing arguments that once circulated only on technical mailing lists and in standardisation committee rooms.

None of this came out of nowhere.

Before there were mandates, there were organisations funding the development of ODF when no politician and no law required it. Here, The Document Foundation has always been at the forefront, alongside various companies in its ecosystem.

Before there were legislative victories, there were the members of the OASIS ODF Technical Committee, who maintained, defended and evolved the specification against all odds: hostile standardisation battles, years of institutional indifference, and a market that had decided – in deference to monopolistic positions – that the matter had already been settled in favour of the proprietary OOXML format.

Before there were announcements of coalitions and summits on sovereignty, there were users who chose ODF and continued to choose it, year after year, accepting the challenge of the incompatibility scientifically imposed by OOXML as a price worth paying to retain control and ownership of their own content.

This is the foundation upon which every recent political achievement rests.

The legislation cites a standard that exists and is maintained. The arguments on interoperability point to a format that works, is implementable and has a community behind it. The questions we are now able to ask publicly – of institutions, coalitions and the ecosystem – are possible because the answer to the question “does open document interoperability work?” has been provided by all those people who did not wait for institutions to wake up after years of hibernation to prove it.

The funders of the ODF format

Developing and maintaining an international standard is not a free labour of love. It requires legal infrastructure, technical expertise, constant organisational commitment and the patience to operate on timescales that no quarterly reporting cycle would recognise as rational.

The organisations that funded the development of ODF – The Document Foundation and its predecessors and partners – have made a long-term commitment to the principle that the infrastructure of written communication must not be the proprietary asset of a single supplier. A commitment that is now being confirmed at a legislative level, the credit for which goes – largely – to all those who made it before it was available.

The OASIS ODF Technical Committee

Standards do not maintain themselves. Behind every version of the ODF specification – from the initial 1.0 to the current 1.4 – there are people who have dedicated their time and professional expertise to a slow process largely invisible to all those who ultimately benefit from its results.

The OASIS ODF Technical Committee worked both during the controversies over ISO standardisation – the period when the approval of OOXML threatened to render the entire ODF effort politically irrelevant – and during the long years when market share data offered little encouragement.

Despite this, it produced a technically coherent specification that is genuinely implementable and designed – unlike its rival – with interoperability as a fundamental principle rather than an afterthought.

Today, when a politician identifies ODF as the standard to be adopted by their administration, they are honouring the results of that work, which deserves to be mentioned and recognised in all its importance.

The users who chose ODF

All the people who saved in ODF format when it would have been easier and more convenient to use OOXML.

All the people who explained to colleagues, clients, and procurement officers why document format is a fundamental issue.

All the people who put up with the problems – requests for files in “Word” format and questions about compatibility – but still chose the harder but more consistent path.

All these users have kept ODF alive as a living format, not just as a specification. They have generated interoperability experiences, reported bugs and provided real-world usage data. They have demonstrated that ODF is not just a theoretical commitment but a practical daily reality for hundreds of thousands of people in every sector and every country.

All these users were, in the strictest sense of the term, ahead of their time. They were already implementing the policy that Germany has just legislated. They were practising the interoperability that the EU is now making mandatory.

And they arrived at this through personal conviction rather than institutional duty, and then held their ground for twenty years, whilst the institutions caught up with a culpable delay.

Thank you

To the funders, the members of the technical committee and the users: what is happening today at a political level is a belated public recognition of the work you have carried out in silence, without fanfare and without thanks, and silently enduring the comments of those who did not understand, or perhaps did not want to understand.

You are no longer a niche group. You are the vanguard that has proven the validity of a concept, and that has made it possible for those politicians who realised that your example was the one to follow – and not that of the lock-in loyalists – to make their case.

Today, The Document Foundation can stand before the European institutions, coalitions and the wider ecosystem, and ask difficult questions about the sovereignty of formats because you have built the foundations upon which we stand. The rest of the world is catching up to a position that you have held for twenty years.

All of this deserves recognition. Thank you.

LibreOffice project and community recap: April 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…

Writer Guide cover

State of the project banner

Screenshot of LibreOffice Bookshelf

Chemnitzer Linux-Tage banner

Document Freedom Day cake

  • And there’s more: we attended the Grazer Linuxtage and gave a talk about what LibreOffice is, where it’s going, and how anyone can get involved to improve it.

First slide from the presentation, with the title What we're doing, and how you can help

  • We have a new developer in The Document Foundation team! Vissarion Fisikopoulos joins us to work initially on LibreOffice Base and databases more broadly, with a focus on Base itself and the ways database functionality connects with the rest of the suite.

Vissarion Fisikopoulos

  • Jiajun Xu wrote two articles looking back at the LibreOffice Asia Conf 2025, specifically the Panel: Lessons from Open Source Business – part 1 and part 2.

Panel discussion from LibreOffice Asia Conf 2025

  • LibreOffice is available in over 120 languages, but we need help maintaining the translations (and adding more). We reached out for Swahili speakers – and have already heard from volunteers, so a big thank you to them! 😊 Of course, everyone is welcome to localise LibreOffice in languages that they know…

Banner with globe

InstallFest banner

LibreOffice 26.2 banner

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