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.

Insights from the InstallFest 2026 Conference in Prague

InstallFest banner

Petr Valach from the Czech LibreOffice community writes:

On the last weekend of March 2026, the regular InstallFest 2026 conference took place. Here is a summary of the news and insights we gained at the event.

New venue

What every visitor noticed immediately upon entering was the change in the location of the conference spaces. Instead of Building E in the courtyard of the Faculty of Electrical Engineering complex, visitors headed up the stairs directly inside Building A from the reception. The conference thus gained larger premises (three floors were allocated), which visitors likely appreciated, as there was no crowding anywhere.

As I mentioned in my report from the previous year, I personally prefer historic spaces over modern architecture like that of LinuxDays. Its design is also very interesting, with a certain intended rawness and practicality, but historic buildings hide their own charm and the mystery of bygone times.

However, the placement of most booths was problematic. They were (as last year) located in a single room. If visitors didn’t know about them, they wouldn’t go there on their own – they had to deliberately search and find them (although there were signs everywhere and the magnetic navigation system deserves praise). Booths should rather be placed in hallways where they are visible. On the other hand, it must be acknowledged that due to echo, such placement would increase noise levels in the corridors, which could be disturbing. In any case, there were very few visitors at the LibreOffice booth – much fewer than at LinuxDays. Therefore, the list of observations will be brief.

At the The Document Foundation / LibreOffice booth

LibreOffice booth

At the booth, in addition to providing information and advice, we offered traditional promotional items such as stickers, beer coasters, and flyers. New this time were badges that visitors could pin to their lapels, and interest in them was surprisingly high.
A small contest in the form of a fill-in puzzle was again prepared for visitors. Clues were distributed across two floors where the conference took place.

Contest sheet

This year, only one member of The Document Foundation attended InstallFest. A significant reinforcement, however, was thirteen-year-old Matěj, who helped mainly with carrying things and staffing the booth. He also attended a lecture focused on FreeCAD and its related workshop (plus one more). Matthew is a high-functioning autistic with interests in physics, astronomy, photography, and IT, and he will newly contribute to LibreOffice translations. We’ll see how he does.

Workshop

Topics and insights

Just a few days before the conference, the German government issued a directive mandating the use of the ODF format in public administrations. ODF is one of the required formats (alongside XML, PDF, etc.). The OOXML format is entirely absent, meaning it is not supported at the federal level in Germany. This has clear consequences and signals a move away not only from OOXML but also from Microsoft Office, as its compatibility with ODF is not good.

This information (along with recent implementations, for example in Denmark, Austria, Schleswig-Holstein, etc.) generated significant interest among visitors. These implementations demonstrate that governments (regional or national) take LibreOffice seriously. They send a signal that LibreOffice is a high-quality suite capable of meeting governmental needs.

For this to be the case, LibreOffice must meet certain criteria. Perhaps the most important is functionality – it must be able to do what governments require. Equally important, however, is security. As we know, using Microsoft 365 (the cloud version of Microsoft Office) is problematic because it conflicts with GDPR regulations. Users do not have control over their data when using this application. This issue does not arise when using the desktop or online version of LibreOffice; here, users have full control over their data. For institutions that process sensitive personal data, this is a crucial requirement that cannot be taken lightly.

It was interesting to observe how important privacy and security are to booth visitors (mostly young students). But not only to them. One student from the Faculty of Social Sciences at Charles University mentioned that using Google Workspace is prohibited at their school due to data protection concerns; however, it is curious that Microsoft 365 is still allowed (even though the same policy issues apply).

The students we spoke with are generally satisfied with LibreOffice and use it for standard office tasks. In addition to Writer and Calc, Impress is also used – students are satisfied with it, although it is often considered the weakest module of LibreOffice. They agreed that it would be very useful to directly label objects on slides automatically, which would improve clarity when editing animations; users would immediately see the order of actions applied to specific objects (as in PowerPoint).

One student also asked about morphing between slides (as in PowerPoint); Impress does not support this feature, and subjectively it is not essential – more of an unnecessary “visual effect.”

This time, far fewer people participated in the contest than at LinuxDays – only seven completed entries were submitted, which is even fewer than last year at InstallFest. Nevertheless, three successful participants were drawn and won T-shirts and a printed color translation of the Writer manual. As always, participants could add questions or comments – only one participant did so, with two questions:

T-shirt winners

  • The first concerned dark mode support. This is not new in LibreOffice; it can be selected under Tools | Options in the LibreOffice | Appearance section. Since LibreOffice 25.8, users can not only switch between light and dark themes but also install themes that completely change the interface colors.
  • The second question was about support for cloud services in LibreOffice. LibreOffice allows connections to various cloud services such as OneDrive, Google Drive, WebDAV, and others. This option is available under File | Open Remote.

Screenshot of LibreOffice's Appearance preferences

The InstallFest 2026 conference is now behind us. We’ll have to wait until October for the next IT conference – LinuxDays 2026. Will we meet there?

Help us to improve LibreOffice’s Swahili translation!

Image of globe

In the LibreOffice project, our goal isn’t to just make a powerful office suite – but to also make it usable for as many people as possible. And a big part of that is translating the user interface, help content and websites. LibreOffice (the app itself) is available in over 120 languages, thanks to our worldwide translation and localisation communities. But we want to do more!

Some translations need more work, for example – such as Swahili (also known as Kiswahili). This language has an estimated 150 – 200 million native and second-language speakers, primarily in Tanzania and Kenya. Swahili is one of three official languages of the East African Community countries, and one of the working languages of the African Union.

LibreOffice’s Swahili (Tanzanian variant) translation is currently 33% complete, so we’d love to get some more help here. If you speak the language, you can help to improve it:

Thank you in advance for any help you can give! And of course, we’re always happy to see translations of LibreOffice in other languages too. So if the software is missing your language, please let us know and let’s improve it 😊

The Foundation Is Strong: What TDF Is, Why It Matters, and Where It Is Going

The Document Foundation was created in 2010 with a single, non-negotiable premise: that a free, fully-featured office suite, built on open standards and governed in the public interest, is infrastructure for democracy. Not a product. Not a market position. Infrastructure, the kind that belongs to everyone and can be taken from no one.

Sixteen years later, that premise is under pressure. And it is worth stating clearly, on the record, what TDF is, what it has done, what it is doing, and why the decisions it has made – including the difficult ones – follow directly from the founding commitment rather than betraying it.

What a Foundation Is For

Our foundation, like many others, exists to hold something in trust. Not for its current contributors, not for its most prolific developers and not for the companies that build products on top of its work, but for the public, across time. That is not a bureaucratic abstraction. It is a legal and ethical obligation that governs every decision the Board of Directors makes.

In Germany, where TDF is registered, such obligations are enforced by law. A gemeinnützige Stiftung – a foundation with charitable status – operates under strict rules designed to prevent any private interest from capturing a public asset. When those rules are tested, the foundation has no discretion: it must act to protect its status, its assets, and its mission, or it ceases to exist in any meaningful sense.

This is the context in which recent governance decisions must be understood. Not as a power struggle and not as the revenge of administrators against engineers, but as the fulfillment of a legal and institutional duty that TDF’s founders accepted when they chose this structure in 2010.

What Actually Happened

Over several years, independent lawyers identified two main areas in which decisions made by board members associated to ecosystem companies created conflicts of interest serious enough to endanger TDF’s charitable status.

These were not hypothetical risks or bureaucratic hair-splitting. They were documented, in writing, by multiple qualified professionals with no stake in the outcome.

Attempts to address these problems through internal policy reform began as early as 2021. A conflict-of-interest policy was introduced. However, the version that was ultimately approved was weaker than what TDF’s legal advisors had recommended. The stronger version was not approved by a board that included representatives of the companies whose conduct was in question. Unfortunately, the milder version proved insufficient.

By 2023 and 2024, the problems were confirmed in successive audit cycles. The Board’s current composition – which no longer includes employees of ecosystem companies – then proceeded to adopt governance reforms, as a change of behavior was urged for repeatedly by lawyers. Amongst the changes introduced, a bylaw provision that suspends membership for individuals whose employers are involved in legal proceedings that directly threaten the foundation’s existence.

The scope of this provision is narrow and specific: it does not apply to ordinary commercial disputes, but only to situations in which the foundation’s charitable status, assets or legal standing are at risk.

The suspension of membership for more than thirty individuals employed by one ecosystem partner followed the activation of this provision, but was announced in detail by two different messages which were clearly outlining the consequences for TDF Members.

The individuals remain welcome in the LibreOffice community. They retain their roles in the Engineering Steering Committee and other technical bodies. They are invited to TDF events. The suspension applies to formal TDF membership and the governance rights that come with it, for the entire duration of the legal consultation process.

This is not a purge. It is a governance safeguard doing exactly what governance safeguards are designed to do.

What TDF Is Building

It would be a mistake to read the current moment as purely defensive. While managing a governance crisis that it did not choose, TDF has continued to invest in the software and the community that give the foundation its purpose.

In the past twelve months, TDF’s eight staff developers contributed 4,077 patches to LibreOffice. Two additional developers have recently joined TDF staff, with one specifically assigned to LibreOffice Base, a module that has been under-resourced for years. Also, work is underway on deeper code modernization: architectural improvements that have accumulated for decades and that require sustained, focused effort rather than feature-driven patch contributions. Announcements on this work are forthcoming.

TDF is also actively developing its thinking on LibreOffice Online. The community has expressed clear interest in a genuinely community-governed online editing capability, distinct from the commercially driven fork that currently occupies that space. This is early-stage work, responsive to community demand, and it will proceed on the community’s terms.

On the standards and policy front, TDF continues its advocacy for ODF as the native document format for public administration software procurement. The Deutschland-Stack mandate, Brazil’s Lei 15.211/2025, and the ongoing digital sovereignty conversation in EU institutions all represent vindication of positions TDF has held and argued for years. This work – unglamorous, slow, and essential – is what a foundation does that a company cannot.

The Question of Meritocracy

The argument has been made, loudly and repeatedly in recent weeks, that TDF has betrayed the meritocratic principles on which LibreOffice was founded, that by limiting the governance role of the most prolific code contributors, the foundation has handed control to people who do not deserve it.

This argument deserves a serious answer rather than dismissal. Meritocracy, as a governance principle, requires that merit be defined in terms of the goals of the organization.

In a commercial software company, lines of code and commit counts might be reasonable proxies for value. In a public-interest foundation whose mission is to protect free software as a commons, merit includes legal compliance, community stewardship, standards advocacy, documentation, translation, user support, and long-term protection of the assets against capture by any single interest, including the most technically capable one.

The original sin of the meritocracy argument as applied here is the assumption that writing code confers the right to govern a foundation. It does not – any more than being the largest donor confers the right to direct a charity’s strategy, or being the most productive employee confers the right to override a board’s fiduciary decisions. These are different roles, each one with a different accountability, and conflating them is not a defense of meritocracy, but an argument for capture.

TDF values its developer community without reservation. It is investing in growing that community, both inside the foundation and across the broader ecosystem. But a foundation even partially governed by the people associated with its largest commercial contributor is not a foundation but a subsidiary.

The Road Ahead

LibreOffice is healthy. Its codebase is actively maintained, its release cadence is regular, its user base is growing in the sectors – public administration, education, and civic infrastructure – where free software matters most. The governance difficulties of recent months have been painful and public, but they have not compromised the software.

TDF is not complacent about the challenges ahead. The competitive landscape is more demanding than ever. Microsoft’s AI integration, although problematic under many points of view, raises the stakes for interoperability. The digital sovereignty moment in Europe creates both opportunities and obligations. The foundation’s technical roadmap must match the ambition of its policy positions.

What TDF will not do is resolve these challenges by abandoning the principles that make it worth defending. The foundation holds, not out of stubbornness, but because the alternative is to become something that no longer serves the purpose for which it was built.

Sixteen years ago, a group of sixteen people decided that the world needed office software that belonged to everyone. That decision has not aged at all. It has, if anything, become more important, and TDF exists to honor it.