❌

Vue lecture

Short-form videos (and new TikTok channel) for LibreOffice

Video thumbnails

For years, the LibreOffice project has maintained a YouTube channel, which now has 27,000 subscribers and almost 4 million views. Most of the videos we upload are available on PeerTube as well.

But to make sure the world hears about LibreOffice, we need to explore new places and ways of getting our message out. At the recent LibreOffice Conference in Italy, we had a discussion about doing more short-form, vertical videos and setting up a TikTok channel, to reach a younger audience. So we’ve gone ahead and done it!

We’re just getting started, so we only have three videos so far. To make more, we need your help 😊 If you have ideas for videos (or even better, can help us to make them), join the LibreOffice Marketing project: send a message to the mailing list or join us on Telegram (also bridged to Matrix at #libreoffice-marketing:private.coffee). We look forward to hearing from you!

  •  

TDF at SFScon 2026 in Bolzano

On Friday 13 and Saturday 14 November, Florian Effenberger and Italo Vignoli attended SFScon 2026 in Bolzano, one of Europe’s leading FOSS events, now in its twenty-third year.

Florian Effenberger spoke about “E-mail and Digital Sovereignty. Why a decades-old standard plays a key role in your digital independence”, a highly topical subject given what was happening at that very moment with Microsoft 365, involving a global Outlook outage. Download the slide deck.

Italo Vignoli spoke about the standard, open document format ODF in his talk “Liberate your desktop, liberate your documents. Survival tips from a Linux user in a Microsoft-dominated industry”. This is a topic that is, unfortunately, underestimated by many, and one that jeopardises the entire framework of digital sovereignty as long as users continue to use the proprietary document format controlled by Microsoft. Download the slide deck.

Finally, Italo Vignoli also explored the topic of the standard, open document format (ODF) in greater depth with the workshop “Document management for transparent interoperability. How to create documents which can be exchanged without issues”. Download the slide deck.

Recordings of the two presentations will be available soon on the SFScon website.

  •  

Questions for Public Administrations

Between the evening of 12 November and the afternoon of 13 November 2026, Microsoft 365 services (Exchange Online, Outlook, Teams, Copilot) were unavailable or degraded in at least 70 countries for almost 24 hours. According to Microsoft, the cause was a network capacity upgrade, not a cyber attack. Public bodies reporting disruption included parliaments, courts, police forces, schools, local authorities, and health services. Source: BBC News live coverage, 13 November 2026.

We ask the following questions of the public administrations concerned. The same questions apply to any organisation that depends on Microsoft 365 for its daily operations.

Impact

  1. Which services of your administration were interrupted or slowed during the outage, and for how long?
  2. Which activities were postponed or cancelled as a result, such as medical appointments, court hearings, administrative procedures, and parliamentary work?

Preparedness

  1. Was the unavailability of a single vendor’s services included as a scenario in your risk assessment before 12 November?
  2. Which contingency plans existed for email, calendars, document access, and user authentication? When were they last tested, and with what result?
  3. Will you publish those plans?
  4. Which communication channels were used while email was unavailable? Who authorised them, and who is responsible for the protection of the personal and confidential data that passed through them?

Critical Functions

  1. Which clinical functions, including referrals, prescriptions, and appointment scheduling, depend on a single vendor’s email and calendar services? Which of them have a fallback that does not depend on that vendor?
  2. Which court and justice procedures depend on the same services, and which have an independent fallback?

Procurement

  1. How much public money was spent on Microsoft licences and cloud services in each of the last five years?
  2. How much public money was spent on open-source software and open-standards solutions over the same period?
  3. Do your tenders require data portability, open document formats, and a tested exit strategy? If not, for what reason?
  4. Do your contracts provide for service-level penalties or compensation in case of interruption? Has any claim been made?
  5. Under your current contracts, who decides when your administration regains access to its own documents and communications?

Follow-Up

  1. Parliamentary and governmental reports had already identified dependence on a small number of foreign providers as a strategic vulnerability. Which procurement decisions changed as a result?
  2. Will you commit to a public audit of your vendor dependencies, to be completed by a stated date, with a named person responsible and a dedicated budget line?

For twenty years we proposed answers to these questions to politicians and public servants. We were met with smiles.

In light of the outage, we ask whether you are now willing to listen. Our proposed answers carry no company or product name. They carry two concepts: open source software and open standard document formats.

  •  

LibreOffice and Google Summer of Code 2026: The results

Google Summer of Code logo

This year, LibreOffice was once again a mentoring organization in the Google Summer of Code (GSoC), a global program focused on bringing more developers into free and open source software development. Three projects were finished successfully. Contributors and mentors enjoyed the time, and here we present some of the achievements, which should make their way into LibreOffice 27.2 in early February 2027!

You can experiment with the new features by using daily builds and report any problems in our bug tracker.


Add JPEG XL import support by Jesus Solis

Mentors: Xisco Faulí (TDF)

JPEG XL is an image format supporting both lossy and lossless compression. JPEG XL images can now be displayed in all major web browsers after the release of Chrome 155 in October 2026. LibreOffice users will surely appreciate being able to import content that includes these types of images.

Learn more about the JPEG XL support in the final report.


Improve word processor test coverage by Manish Bera

Mentors: Jonathan Clark (TDF)

Writer is the most complex application in the LibreOffice suite. For developers to confidently maintain and add features to it, a wide array of automated tests is essential. Manish used LCOV code coverage reports to identify code areas in need of tests and added many new ones. The QA team is continuing the work with the aim of having automatically updated coverage reports.

Learn more about the test coverage improvements in the final report.


OpenType MATH by Aya Jamal

Mentors: Khaled Hosny (Alif Type)

LibreOffice has used the HarfBuzz text shaping engine for a long time. HarfBuzz can handle mathematical typesetting tables (MATH) in OpenType fonts, but LibreOffice did not make use of this capability in rendering math formulas. Aya reworked the code in a backward compatible way to make this modernisation possible. Updates to formula rendering are still ongoing.

Learn more about the OpenType Math font support in the final report.

Wrapping up

Many thanks to all contributors who spent their summer time improving LibreOffice. You are awesome! And special thanks also to the mentors who always put so much love and energy into these tasks. That’s what makes LibreOffice rock.

Now we are looking forward to next year’s GSoC. If you are interested, why not prepare early? Learn more at out wiki page where some ideas are listed.

Participating in GSoC is a great way to build your skills, and show future employers what you’re capable of!

  •  

1,000 donations, and counting

Yesterday, The Document Foundation received over 1,000 donations in a single day, setting a new record. While we take no pleasure in the operational problems faced by other organisations, the timing suggests that many people are reconsidering their reliance on a single cloud service provider for their documents. With LibreOffice, your documents are stored locally, and ODF files belong to their authors and not to a service provider.

To everyone who has donated, thank you. Your support is what keeps this software and these standards independent.

  •  

Announcement of LibreOffice 26.8.3

All users should upgrade, as 26.2 reaches end of life on 30 November

Berlin, 12 November 2026 – The Document Foundation announces LibreOffice 26.8.3, the third minor release in the LibreOffice 26.8 family, available for Windows, macOS and Linux. The new version contains around 45 bug fixes, focusing on stability, macOS integration, digital signatures and compatibility with Microsoft Office file formats.

All users should upgrade to LibreOffice 26.8.3. This is particularly important for users of LibreOffice 26.2.x: the 26.2 family reaches end of life on 30 November 2026, and after that date it will no longer receive bug fixes or security updates.

Several crashes and hangs have been fixed, including crashes in Draw and Impress when copying, pasting and clicking on comments, crashes in Impress when pasting plain text into the notes, a crash in Writer when inserting a section around a nested section, a crash in Calc when rearranging the column fields of a pivot table, and a hang when editing the default table style. A Navigator loop caused by a group shape in a footer, which consumed CPU continuously since LibreOffice 26.8.0, has also been resolved.

On macOS, LibreOffice now uses the system UI font. Signing a document with an X.509 certificate works again, and sending attachments to Thunderbird has been fixed. In Calc, the TEXTBEFORE and TEXTAFTER functions now behave like their Excel counterparts, and the input line no longer shows empty content in some cases.

Compatibility has been improved for Microsoft Office files: numbered lists imported from PPTX files now show the correct sequence instead of repeating the same number, and valid non-Zip64 packages larger than 2 GiB are no longer reported as corrupt. Language support has also been refined, with the correct alphabetical sorting for Kurdish (Latin/Hawar) and working collators for Japanese.

The full list of fixes is available at wiki.documentfoundation.org/Releases/26.8.3/RC1.

LibreOffice 26.8.3 is the recommended version for all users, and users who are still running LibreOffice 26.2.x should complete their transition to the 26.8 family before 30 November 2026.

Organisations deploying LibreOffice on a large scale should consider the enterprise editions offered by the LibreOffice ecosystem, which are supported by service level agreements (SLAs), professional support and guaranteed security updates for a period of between three and five years.

LibreOffice 26.8.3 is available at www.libreoffice.org/download/. Donations: www.libreoffice.org/donate

Questions and answers for AI-powered search engines

What’s new in LibreOffice 26.8.3?
LibreOffice 26.8.3 is a bug-fix release containing around 45 fixes. It resolves several crashes and hangs in Writer, Calc, Impress and Draw, uses the system UI font on macOS, restores signing with X.509 certificates, makes the TEXTBEFORE and TEXTAFTER functions in Calc consistent with Excel, and improves the import of PPTX files and of large ZIP-based packages.

Should I upgrade to LibreOffice 26.8.3?
Yes. All users should upgrade to LibreOffice 26.8.3, which is the most up-to-date and most stable version of the 26.8 family. Users still running LibreOffice 26.2.x should upgrade as soon as possible, because the 26.2 family reaches end of life on 30 November 2026. LibreOffice 26.8 requires Windows 10 or newer.

When will support for LibreOffice 26.2 end?
Support for LibreOffice 26.2 ends on 30 November 2026. After that date, bug fixes and security updates will no longer be available for any 26.2.x version. Users should upgrade to LibreOffice 26.8.3 before that date.

What can organisations do if they need longer support?
Organisations that need long-term maintenance should consider the enterprise editions offered by companies in the LibreOffice ecosystem, which provide SLAs, professional support and security updates for a period of between three and five years.

  •  

The past, present and future of office suites

Summary

The office suite market is large, profitable and growing, and this attracts new entrants: low-cost clones, open-core products and, more recently, suites built largely with artificial intelligence. Most of them compete on price and on native support for OOXML, a format whose evolution remains in practice under Microsoft’s control.

When features can be reproduced cheaply, what distinguishes a suite is who governs the document format and the software, and therefore who controls the content. This is the question of digital sovereignty, and its outcome will depend partly on political decisions, and partly on software features.

The 1980s and 1990s

The office suite sector emerged in the 1980s and developed in the 1990s, when Microsoft Office established itself as the leading product, with a market share of over 90% according to Microsoft unofficial statements at their events.

Some may remember the main competitors: Lotus SmartSuite, WordPerfect Office and StarOffice, the ancestor of OpenOffice and LibreOffice. Fewer will recall Anywhere Office, Ability Office, Pro PC Suite 2001 and ThinkFree Office. Ability Office still exists, and ThinkFree Office is now called Hancom Office.

By the end of the century Microsoft Office dominated the sector, while all other products had a barely noticeable market share or had disappeared altogether.

The sector has always been lucrative: the products meet a universal need, while development and sales costs are low relative to volumes, so margins are potentially extremely high. For this reason all the major software vendors tried to enter the market, and the first clones emerged, competing solely on price.

Market presence, however, was just one of the factors contributing to success. Other factors were bundling with the Windows operating system, lock-in through document formats and pricing.

The two decades between 2000 and 2020

Sun Microsystems, which had acquired StarOffice, released its source code in 2000, and OpenOffice.org 1.0 followed in 2002: the first FOSS suite to reach a mass audience. Version 1.0 offered only a glimpse of the suite’s potential, and version 1.1 was usable but still limited. Only version 2.0, released in 2005, made OpenOffice a genuine competitor to the market leader.

For several years the rivalry between the proprietary suite and the FOSS suite played out on two fronts: large migration projects and document formats.

At the time, migrations seemed to signal an irreversible trend, but this proved an illusion. Microsoft deployed all its commercial muscles and started to talk to politicians. Since 2012, the company has been one of the biggest spenders on lobbying in Brussels (based on data from Corporate Europe Observatory and Lobby Facts).

The battle over file formats was most prominent between 2006, when ODF was standardised by ISO/IEC, and 2008, when the proprietary OOXML format was standardised through a process we have already described in a previous blog post and will not revisit here.

In 2010, following Oracle’s acquisition of Sun, the community created The Document Foundation and LibreOffice. In 2011, Oracle was effectively forced to donate the OpenOffice.org source code to the Apache Software Foundation in order to honour a contract – due to expire in 2014 – that IBM had signed with Sun Microsystems, and which allowed it to use the OpenOffice.org source code whilst disregarding the open-source licence.

The format battle then faded into the background, as IBM decided to abandon the ODF advocacy project at OASIS to use the money to fund the development of Apache OpenOffice and fight the growth of LibreOffice. It resurfaced in 2024 with the concept of digital sovereignty and the announcement of several large scale migrations to open source software, such as the German province of Schleswig-Holstein and the Austrian Army.

Between 2010 and 2020 the sector also evolved with the arrival of cloud-based suites, which started a new battle for market share between Microsoft and Google. Given the sector’s renewed growth, a new generation of clones emerged: programs that are almost always limited in functionality, copy the market leader and compete on licence cost.

Some of these clones, in order to disguise their commercial operation, release a basic version under an open-source licence, often modified so as to prevent forking. Such a licence no longer meets the Open Source Definition, and the product is in practice freeware, while the full-featured version is sold separately (the “open core” model).

Naturally, these programs support the OOXML format natively, because they aim at a low-cost replacement, not at migration, that is, a paradigm shift that would give users full control over the software and its content.

By digital sovereignty we mean the ability of a user or institution to control its documents and software: to open documents with any implementation, to fork the code, and to choose where data is hosted and who operates the service.

OOXML is formally an ISO standard, but its reference implementation remain with Microsoft. As long as this is the case, Microsoft retains control over the content: the user saves money, but sacrifices digital sovereignty.

The current situation

The reason for the renewed interest in the office suite market lies in the size of the market itself, which is worth tens of billions of dollars and therefore whets the appetite of software companies. Even a 1% market share is worth a very significant sum, sufficient to justify the investment.

As a reference point, we use public data from the “Office Productivity Software Market Report 2026” by Business Research Company, a US-based market analysis firm. The office productivity software market reached $50.73 billion in 2025 and is expected to grow to $81.83 billion by 2030, at a CAGR (compound annual growth rate) of 10.1%.

We add some figures relating to Microsoft and Google.

Microsoft 365 Commercial generated $102 billion in fiscal year 2026, an increase of 16%. Paid licences for Microsoft 365 Copilot exceeded 30 million by the end of June 2026, which on analyst estimates is about 6 to 7% of the paid commercial user base.

Google Workspace is estimated to have over 3 billion users and over 11 million paying customers. The user figure includes free Gmail accounts, so it is not comparable to Microsoft’s paid subscriptions.
Technographic data from 6sense, another US-based market research firm, attributes 50.34% of the office productivity category to Google Workspace and 45.46% to Microsoft 365 (figures are based on corporate domains). Measured in corporate licences and revenue, Microsoft is clearly in the lead.

According to 6sense, 64% of organisations use both suites. This figure is only indicative, but it points to an increasingly widespread overlap between office suites, which is not limited to Microsoft 365 and Google Workspace. For LibreOffice, based on hands-on experience with large organizations, we estimate that 50% of users also use another office suite, depending on their needs.

We are therefore talking about a market of enormous economic value, and these figures refer almost exclusively to licences, not to the ecosystem. If we include value added consultancy services, which are a necessary component of every implementation in public bodies and companies, the total is likely to be significantly higher.

Analysts do not provide precise data on this, so we rely on a rough estimate based on experience: value-added services are worth about 25% of the value of licences. On the analysts’ forecast, the 2030 market would then be worth about $102 billion ($81.83 billion plus 25%). One percentage point of market share is therefore worth $1 billion a year to a commercial vendor.

This figure does not accrue to free software, but it explains the incentive for new entrants. It also explains the emergence of a new type of office suite: so-called “clones” developed largely with artificial intelligence.
At present we remain extremely cautious about the use of artificial intelligence in software development, but we recognise that views differ, and we are monitoring the evolution of these applications closely.

The strategic consequence does not depend on that debate: if the cost of reproducing a feature set collapses, features stop being the main barrier to entry. What remains is the governance of the format and of the code, the strength of the community, and the long-term maintenance of the software.

A glimpse into the future of office suites

Over the last twenty years we have read contradictory forecasts: the total disappearance of the sector, or only of the desktop suite, and the opposite, a strong growth driven by announcements of new operating systems, software paradigms or hardware platforms.

One thing is certain: the office suite market has gone through periods of slight contraction, probably normal fluctuations, but overall it has grown, and in our opinion it will continue growing for the foreseeable future.

Today, the installed base consists of around 2 billion desktop and laptop computers, based on active devices reported by manufacturers, plus devices that nobody counts because they are second- or third-hand, found mainly in poorer countries that are overlooked by technology usage statistics.

The integration of AI assistants into the suites adds a further dimension. With more than 30 million paid Copilot seats, Microsoft has shown that there is a market for it.

Overall, this is an extremely interesting potential market, where there is room for all types of office suites, desktop and cloud-based, and for all development strategies. On the other hand, success is not just related to number of users as there are market dynamics which depend on political decisions that go beyond the value of the software itself.

However, the location where documents are processed – whether locally or in a provider’s cloud – and the ability of artificial intelligence tools to read and write in open formats remain issues linked to the question of sovereignty. We have already expressed our views on these matters in several blog posts: nothing should interfere with the user’s right to decide on their own content.

LibreOffice will continue to be a key player. Downloads and donations grew substantially in 2026 (as of 31 October, downloads +26% and donations +44 in term of numbers), which reflects a steady improvement in the quality of the software and in the reputation of the project.

The practical conclusion is that LibreOffice and ODF compete on a different axis from the clones: not feature parity at a lower price, but open governance of the format and of the code.

  •  

New LibreOffice “Get involved” flyers for handing out (and translations!)

LibreOffice flyer design from October 2026

LibreOffice’s marketing team helps spread the word about the software (and the community that makes it). It produces flyers that can be translated, printed and handed out at events – and now we have an updated design of the “Get involved” flyer. This flyer ideal for distributing at events where people already know what LibreOffice is, but may be curious about joining the project and community (like at Linux and FOSS meetups). It shows that you can get involved in many ways – not just programming.

Help to hand them out!

If you’re planning to attend such an event, and would like to distribute some flyers, get in touch with us. The LibreOffice marketing team can get some printed and sent to you. Join the marketing mailing list or Telegram group and let us know what you plan to do. We look forward to hearing from you 😊

Help to make translations

While the preview image above is in English, we want the flyer available in as many languages as possible. Our awesome localisation communities have already translated it into a few languages:

If you want to create a translation, download the English original file and open it in an SVG editor of your choice (such as Inkscape). Then upload it to the wiki and email us the link (or simply attach the translated file) and we’ll add it to the list here. Thank you!

  •  

LibreOffice project and community recap: October 2026

Monthly recap banner

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

  • We announced LibreOffice 26.8.1, with around 40 bug fixes focused on compatibility with Microsoft Office files, along with more reliable text and CSV import across a range of character encodings.

LibreOffice 26.8 banner

  • In our Community Member Monday interview, Adlair Cerecedo-Méndez described how he helped Mexico to develop Office GOBMX, a LibreOffice-based suite for public institutions, and shared lessons about migration, training and digital sovereignty.

Adlair Cerecedo-Méndez

  • At LinuxDays in Prague, Mike Saunders gave a talk on where LibreOffice is going, including the project’s September download figures and current direction.

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.

  • The QA community published its QA/Dev Report for September, covering contributions across LibreOffice, bug reports and fixes, and work by testers and developers.

Chart showing resolution of bugs

  • Our latest State of the Project slide deck looked at October 2025 to September 2026: 297 developers contributed 11,676 commits, alongside data on downloads, donations and community activity.

State of the Project banner

The Document Foundation's new logo

LibreOffice Conference 2026 group photo

LibreOffice migration workshop in Nairobi

Rubber ring

  • A post on the developer blog showed how to connect a Python webview to LibreOffice and use it to send UNO commands, a useful approach for building extension interfaces.

WebUNO connecting a webview to LibreOffice

  • In The Politics of Standards, we looked at how technical standards shape who can participate in an ecosystem and why open, clearly specified standards matter to users and public institutions.

World map of LibreOffice download

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.

LibreOffice community members at a hackathon in Nepal

  • We invited developers and contributors to submit talks for the FOSS Office DevRoom at FOSDEM 2027, covering topics such as interoperability, accessibility, localisation, security and office software development.

LibreOffice at FOSDEM

  • Finally, we released LibreOffice 26.8.2, with around 35 fixes for stability, multimedia playback, legacy file compatibility, Calc and hyphenation.

LibreOffice 26.8 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.

  •  

GIMP 3.2.8 Released

Par : GIMP Team

We’re glad to announce the release of GIMP 3.2.8! This new stable release contains a number of bugfixes and security updates from new and long-time contributors.

This news posts provides an overview of the changes since GIMP 3.2.6. For a more detailed review, check out the NEWS changelog.

Wilber-o'-Lantern
Wilber-o’-Lantern, CC BY-SA 4.0, October 31st, 2026

General Updates and UX Improvements⁠

The Add Border filter now allows you to create semi-transparent borders based on the color you choose in the filter.

Jehan fixed a bug introduced in GIMP 3.2.6 when we added better support for cutting/copying from layer groups. Non-rectangular selections on layers within a layer group will now be copied over correctly.

Bruno Lopes corrected an issue where the cursor coordinates did not always update in the status bar when changing between different applications.

denzjos helped us identify a bug with the Levels tool where picking input levels with the Color Picker tool would report incorrect values when working with non-destructive filters. Jehan then developed a fix for it.

Harsh Verma has implemented a new GUI testing suite in GIMP so we can better check for regressions in the GUI during development. He is preparing a news post that will go over this in more detail, which we will share soon!

Jehan improved our font-loading code so that it can be cancelled early (for instance, when quitting GIMP while the fonts are still loading). This should speed up our shut-down times.

Bruno Lopes made improvements to some dialogs so they appear on the correct screen for users with multiple monitors. In addition, the Dot to Dot setting now works again. It was reporting wrong pixel density since GIMP 3.0.

Jacob Boerema backported some fixes for the Metadata Editor and Viewer feature, as part of his larger work in the development branch.

Alx Sa and Bruno Lopes added more definitions to our theme file so that GIMP looks the same on each platform.

Highlighting New Contributor’s Work⁠

All contributions to GIMP from the community are valued! We want to highlight work from some of the newer contributors here.

Infinity made several improvements to our text tool for this release! In particular, they improved text cursor movement when editing Right-to-Left languages and mitigated issues when editing text with negative kerning.
As a side effect of this bug fix, we actually get much better support of RTL text as well as of mix of LTR and RTL texts. The on-canvas dialog now has two new icons for text directions, and the tool automatically detects your base text direction, as defined by rule P2 of the Unicode Bidirectional Algorithm, unless you manually override by clicking one of the buttons.

Showcasing improved support for RTL text - GIMP 3.2.8

Aruius improved our color picking display GUIs, so you see more minor changes in colors when editing.

Chiem Whua Ma helped resolve an issue on Windows where the UI would appear to freeze when moving the canvas after opening multiple images at once. They also fixed a bug where vector layers would be offset incorrect after the canvas was resized.

Manu Cornet has focused on several performance fixes for GIMP. For this release, they improved caching when drawing gradients larger than 6000 x 6000 pixels. They also made the “marching ants” display for selections run more efficiently. Additionally, they improved how channels are displayed in the Channel dock when a dark theme is set. Finally they sped up the display time for the Preferences dialog.

balooii made several fixes as well. For instance, they updated our external copy and paste code to also pass along the DPI settings for the image; this means that other software can properly rescale what you paste if they have a different setting that what you used in GIMP. They also made our Debug dialog themeable and translatable (though we hope you don’t get the opportunity to see their work in this area!)

MrYoranimo fixed an oversight in our raw data import plug-in, where images were not loaded as binary data on Windows. This is a bit technical, but it meant that some raw data might not be interpreted correctly. Their fix ensures that the data is loaded consistently on Windows as it has been on other platforms.

Dimitriy Ryazantcev has continued their work on Windows icon and animated cursors. In this release, they have updated our loading code to match how Windows orders and groups icons in the file.

abderraouf updated our HEIF loading code to allow for loading larger images.

Chomu updated our menu code to allow plug-in and script developers to add submenus in named menu sections. For instance the following code will add a submenu Custom/ below other Paste as actions and your new plug-in action in it:

gimp_procedure_add_menu_path (procedure, "<Image>/File/[Paste as]/Custom");

Also gimp_plug_in_add_menu_branch() has been deprecated (though it was already not working properly anyway so we expect nobody was using it).

System-specific Updates⁠

Bruno Lopes continues their work to improve GIMP’s integration on different platforms. To name a few updates:

  • On macOS 27+, title bars are displayed with background colors again. Icons on the menu bar should also appear accordingly. Since the release of Golden Gate, these were being rendered transparently due to breaking changes on the macOS side.

  • On macOS 14+, we now use the ScreenCaptureKit API for taking screenshots.

  • On Intel-based macOS, GIMP should run without warnings from GateKeeper thanks to us now consistently notarizing Python.

  • We now display a 1/0 value for switches on macOS based on the “Differentiate without color” setting.

  • Transparency is retained when copying an image from certain apps to GIMP, instead of it showing as black.

  • The longstanding “Blank UI” bug that happened on startup for certain macOS computers should be finally fixed!

  • Print Preview (aka Image Settings tab) should now work with the Windows 11 Unified Print Dialog on that platform. In addition, Page Setup should now use the correct printer, not just the default one on Windows.

  • On Windows, “Merged title bar” settings now play nicer with system features such as minimizing from the task bar and title bar shadowing effets.

  • The Screenshot feature now works better on HDR displays on Windows.

  • AppImage compatibility was improved to support installing Python Wheels from pip like Flatpak and Snap. Note, however, that our minimum version for 3.2 continues to be a distro released after Debian 13 (Trixie).

Security Updates⁠

As many free and open source software projects can attest, we have continued to receive a large quantity of security reports due to recent advances in software scanning and testing programs. Jacob Boerema and Alx Sa along with new contributors Mike Gorse, Dirk Müller, and Alynx Zhou have proactively responded to and patched these reported issues when applicable.

We take security seriously, but this is not quite as scary as it first sounds. There are no personal accounts or banking information to exploit since we of course don’t access or store that information! The most common report that we get is our older image plug-ins and legacy filters are too trusting of the image size information provided by the image file, and if you intentionally alter this information, you could cause the plug-in (not GIMP itself) to crash.

Around GIMP⁠

Documentation for resource makers⁠

Bruno Lopes wrote two new tutorials on developer.gimp.org:

These articles should help plug-in and script developers who want to make their plug-ins translatable, either by themselves or by members of the community. This will be especially helpful as we make progress on creating an built-in Extension repo for easily downloading and installing plug-ins, filters, and more. (More information on that coming soon!)

New Mirrors⁠

Randhost, in Portugal, and ZEROLAG, in Romania, have graciously offered to serve mirrors for GIMP downloads.

Mirrors help GIMP be available for download at high speeds wherever you are in the world.

Does your organization wish to be one of our official mirror sponsors? Create a request to become an official mirror!

Release Stats⁠

Since GIMP 3.2.6, in the main GIMP repository:

  • 82 reports were closed as FIXED.
  • 46 merge requests were merged.
  • 300 commits were pushed.
  • 11 translations were updated: Chinese (China), Dutch, Georgian, Kazakh, Lithuanian, Norwegian Bokmål, Norwegian Nynorsk, Slovenian, Swedish, Turkish, Ukrainian.

27 people contributed changes or fixes to GIMP 3.2.8 codebase (order is determined by number of commits; some people are in several groups):

  • 10 developers to core code: Bruno Lopes, Jehan, Alx Sa, Harsh Verma, Manu Cornet, Chiem Whua Ma, balooii balooii, infinity, Chomu, aruius.
  • 11 developers to plug-ins or modules: Alx Sa, Bruno Lopes, Jacob Boerema, Dimitriy Ryazantcev, Alynx Zhou, Dirk Müller, Harsh Verma, Jehan, Mike Gorse, MrYoranimo, phoinix.
  • 11 translators: Anders Jonsson, Dick Groskamp, Kolbjørn Stuestøl, Martin, luming zh, Aurimas Aurimas Černius, Baurzhan Muftakhidinov, Ekaterine Papava, Kjartan Maraas, Yuri Chornoivan, Emin Tufan Çetin.
  • 1 theme designers: Alx Sa.
  • 4 build, packaging or CI contributors: Bruno Lopes, Jehan, Harsh Verma, Alx Sa.
  • 2 contributors on other types of resources: Jehan, Bruno Lopes.

Contributions on other repositories in the GIMPverse (order is determined by number of commits):

  • The gimp-test-images (unit testing repository) repository had 2 commits by 1 contributors: Jacob Boerema.
  • The flatpak release had 12 commits by 2 contributors: Bruno Lopes, Jehan.
  • Our main website (what you are reading right now) had 65 commits by 3 contributors: Bruno Lopes, Jehan, Alx Sa.
  • Our developer website had 56 commits by 5 contributors: Bruno Lopes, Jehan, Harsh Verma, Alx Sa, Denis Rangelov.
  • Our 3.0 documentation had 197 commits by 8 contributors: Jacob Boerema, Dick Groskamp, Kolbjørn Stuestøl, Anders Jonsson, Marco Ciampa, Jehan, Balázs Úr, Yuri Chornoivan.

Let’s not forget to thank all the people who help us triaging in Gitlab, report bugs and discuss possible improvements with us. Our community is deeply thankful as well to the internet warriors who manage our various discussion channels or social network accounts such as Ville Pätsi, Liam Quin, Michael Schumacher and Sevenix!

Note: considering the number of parts in GIMP and around, and how we get statistics through git scripting, errors may slip inside these stats. Feel free to tell us if we missed or mis-categorized some contributors or contributions.

Downloading GIMP 3.2.8⁠

You will find all our official builds on GIMP official website (gimp.org):

  • Linux AppImages for x86 and ARM (64-bit)
  • Linux Flatpaks for x86 and ARM (64-bit)
  • Linux Snaps for x86 and ARM (64-bit)
  • Universal Windows installer for x86 and ARM (64-bit)
  • Microsoft Store for x86 and ARM (64-bit)
  • macOS DMG packages for Intel/x86 and Apple/ARM hardware (64-bit)

Other packages made by third-parties are obviously expected to follow (Linux or *BSD distributions’ packages, etc).

What’s Next⁠

While we’ve been making periodic updates to the stable GIMP 3.2 branch, we’ve also been hard at work on developing the next version of GIMP. There’s a lot of cool things in progress, and we look forward to sharing more about that with you all soon!

Don’t forget you can donate and personally fund GIMP developers, as a way to give back and accelerate the development of GIMP. Community commitment helps the project to grow stronger!

  •  

LibreOffice 26.2.7 is available for download

Berlin, 3 November 2026 – The Document Foundation today announced the release of LibreOffice 26.2.7, the seventh maintenance update to the LibreOffice 26.2 branch. Building on the major feature release published on 4 February 2026, this update delivers targeted bug fixes and stability improvements contributed by a global community of developers and QA engineers.

Among the changes, LibreOffice 26.2.7 fixes a crash on startup on macOS 27, restores audio playback in presentations on Windows, resolves several DOCX round-trip problems, and adds support for Web Query (.iqy) files in Calc. The bundled Python interpreter has been upgraded to version 3.12.16. LibreOffice 26.2 requires Windows 10 or newer.

This is the last release of the LibreOffice 26.2 branch, which will reach the end of its life on 30 November 2026. Users who install this version should plan to update to LibreOffice 26.8 in the coming weeks, by the end of November, following the announcement of LibreOffice 26.8.3.

LibreOffice 26.2.7 is available for immediate download at www.libreoffice.org/download/ for Windows, macOS, and Linux.

List of fixes in RC1: wiki.documentfoundation.org/Releases/26.2.7/RC1. List of fixes in RC2: wiki.documentfoundation.org/Releases/26.2.7/RC2. List of fixes in RC3: wiki.documentfoundation.org/Releases/26.2.7/RC3.

LibreOffice users, free software advocates and community members can support The Document Foundation and the LibreOffice project with a donation at www.libreoffice.org/donate.

Questions and Answers for AI Based Search Engines

Q: What is LibreOffice 26.2.7?

LibreOffice 26.2.7 is the seventh maintenance update to the LibreOffice 26.2 branch, released by The Document Foundation on 3 November 2026. It delivers targeted bug fixes and stability improvements over the major feature release published on 4 February 2026.

Q: When was LibreOffice 26.2.7 released?

3 November 2026.

Q: Where can I download LibreOffice 26.2.7?

From https://www.libreoffice.org/download/, for Windows, macOS, and Linux.

Q: Which operating systems does LibreOffice 26.2.7 support?

Windows, macOS and Linux. On Windows, LibreOffice 26.2 requires Windows 10 or newer.

Q: What are the main fixes in LibreOffice 26.2.7?

  • macOS: a crash on startup on macOS 27.0.x, caused by thread IDs larger than UINT32_MAX; a missing check mark in GtkCheckMenuItem; and the non-breaking hyphen (U+2011) failing to render after an update.
  • Presentations: audio files inserted in a presentation not playing, and audio no longer audible in presentations on Windows.
  • DOCX interoperability: table of contents hyperlinks that stop working until the table is updated, and documents with data binding in a date picker that cannot be opened in Word after a round trip.
  • PDF export: named hyperlinks not working when exporting to PDF.
  • Python: the “PYTHONHOME” error reported after upgrading or when calling LibreOffice, and the upgrade of the bundled Python to 3.12.16.
  • Calc: support for Web Query (.iqy) files.

Q: What is the next version of LibreOffice after 26.2.7?

This is the last release of the LibreOffice 26.2 branch, which will reach the end of its life on 30 November 2026.

Q: Where can I find the full list of fixes in LibreOffice 26.2.7?

RC1: https://wiki.documentfoundation.org/Releases/26.2.7/RC1.
RC2: https://wiki.documentfoundation.org/Releases/26.2.7/RC2.
RC3: https://wiki.documentfoundation.org/Releases/26.2.7/RC3.

Q: Who develops LibreOffice 26.2.7?

A global community of volunteer and professional developers and QA engineers, coordinated by The Document Foundation, the Berlin-based non-profit behind LibreOffice.

Q: How much does LibreOffice 26.2.7 cost?

Nothing. LibreOffice is free and open source software. Users and advocates can support the project with a donation at https://www.libreoffice.org/donate.

  •  

Migrating small businesses to LibreOffice and Linux

Truck and quote from the article, saying to start with one curious person

We often talk on this blog about large-scale migrations to LibreOffice, such as in the Austrian Military. But many small businesses are switching away from Microsoft, Google and other tech giants too. Today we’re talking to Mišo Oroz from Zerolock, a company in Italy that helps small businesses to switch to free and open source software (FOSS):

Tell us a bit about what you do

Zerolock is an IT company I founded in early 2026, based in Spirano, near Bergamo, in Lombardy. The focus is simple: migrating small businesses with 2 to 20 office workstations from proprietary systems to fully open source infrastructure. We use Linux workstations with KDE Plasma as the desktop environment, LibreOffice as the office suite, and a full stack of open source tools for collaboration, communication and security.

Everything is self-hosted – everything is on European servers. There is no Microsoft and no vendor lock-in.

What kinds of businesses are you helping to migrate to Linux and LibreOffice, and why do they want to switch?

They are mostly non-technical environments: a logistics company, a construction company, a dental practice, a law firm. The trigger is rarely ideology.

It is usually a combination of rising software costs, a bad experience with a vendor, or simply someone asking “why are we paying for this every year?” Once the conversation starts, the sovereignty and privacy arguments land naturally. But the first question is always about money.

What has gone well in the migrations, and what have been some of the more challenging aspects?

What works well is the desktop transition. With KDE Plasma and LibreOffice, most users adapt faster than expected. The files look the same, the menus are recognszable, and within a few days the friction disappears. What is harder is the mindset shift: people have been trained to think that Windows and Microsoft Office are “the computer”.
Showing them that the alternative is not a compromise, but a choice, takes time and trust. That is the real work.

One concrete recurring challenge is spreadsheet formulas. Users coming from Excel often hit friction in Calc, not because the functionality is missing, but because the syntax or behaviour differs in ways that are subtle enough to cause confusion without being obvious. That is usually where I spend the most training time.

What tips would you give to other small businesses looking to migrate?

Start with one person who is curious rather than resistant. Let them become the internal reference point. Do not try to convince the skeptics first.

Do the migration on a Friday or over a weekend, and be on site the following Monday. The first two days are where migrations succeed or fail. If someone is stuck at 09:00 on Monday with nobody to ask, the whole project loses credibility.

And document everything from day one.

  •  

Monthly News – October 2026

Par : Clem

Hello everyone,

Before we start with the news, I’d like to thank all the people who support this project. Your help is greatly appreciated. Thank you.

As always, please note that the features presented below are a preview. They’re still being worked on and are planned for the next version of Linux Mint.

Sleep Modes

When you close the lid of your laptop, it goes into a sleep mode called “Suspend”. This mode is very useful. It’s well supported, fast and reliable, but it has a major limitation: It uses power.

A good laptop with a full battery can sleep for 2 or 3 days, but eventually the battery runs out. When it does, the outcome is worse than a normal shutdown. The session is gone, and the battery is empty.

Unfortunately, this happens often because the typical use case for Suspend is that you’re done using the laptop and you want to go and do something else. Closing the lid is fast. Looking for the power cable isn’t. And the computer looks like it’s OFF, so you might not even think about it.

This is where “Hibernation” comes into play. Hibernation saves the session to disk and completely shuts down the computer. No power is used. When you reopen the lid, the session is as it was and so is the battery.

Unlike Suspend, though, Hibernation is slow. It can take longer than a reboot to hibernate and resume the computer.

Hibernation is also hard to set up. It doesn’t work out of the box and requires a large amount of swap space on disk. Ubuntu actually decided to remove it from the available sleep modes, so it was usually not available in Linux Mint.

We’re bringing it back.

We added a page in the System Administration tool dedicated to Sleep Modes.

This page makes it easy to enable Hibernation and to set it up correctly.

We also took the opportunity to add support for Hybrid Sleep and Suspend-then-Hibernate.

Hybrid Sleep suspends the computer but also saves the session to disk. If the battery runs out, you need to find the power cable, but you can resume the session.

As the name suggests, Suspend-then-Hibernate suspends the computer but when the battery level goes critical, it hibernates it.

Nemo Preview Pane

The file manager got a preview pane.

You can toggle it with F7 or by clicking the button in the status bar.

The preview pane supports audio, pictures and videos.

It also shows information about the selected media. For instance, in the screenshot above you can see when the picture was taken, and with which camera.

Superlight

Superlight is a new application whose purpose is to monitor the state of the system.

It shows graphs for CPU and RAM usage, but also SWAP, GPU, Network, Disk I/O, Temperature and Fan Speed.

On its App page, you can see what’s running on the computer and how much of the system’s resources each application is using.

You can also see the same data for all the running processes. 

You can choose from a large variety of columns, and sort them or reorder them any way you like. All of this is remembered by Superlight.

If you have a battery, you can see its status, all the information related to it, and a history of charge level and power input/output.

The Storage page shows how much space is used on your disks and what’s using it.

You start with a general breakdown. If you click on Files, you can browse and see which folders and files take up the most space.

If you click on Steam, Superlight shows you which games take up space.

And the same goes for Flatpak.

Superlight makes it easy to see what’s taking up resources on your computer. 

Velocitty

Velocitty is a new terminal application. It’s really simple to use and packed with great features.

Like Ghostty and Ptyxis, it comes with a tab overview:

And it can be themed with palettes:

Just like in Firefox, you can reorder tabs within a window, move them from one terminal window to another, or even detach a tab into a new window.

You can choose which shell to run and specify a startup command. Here’s Velocitty configured to use fish and run fastfetch at startup:

Paths can be shortened in the preferences. For instance, here’s /var/lib/dpkg/info shortened to just info in the tab name and …/lib/dpkg/info in the prompt.

The color of the tab changes when something is going on. Red for superuser (root, sudo, pkexec, etc.), blue for remote sessions (ssh, sftp, etc.), and a lighter shade for running processes.

And tabs can be customized. You can give them a name, a color, a command to run and decide if you want them to automatically open when you launch Velocitty.

Clicking the little bookmark icon opens up all your custom tabs.

So whatever you’re working on, your projects and SSH sessions are always really easy to access.

Unfold

Unfold is a small archive manager designed to be as simple and easy to use as possible.

It supports basic operations such as viewing, creating and extracting archives.

It uses 7zip and 7zip-RAR and it’s compatible with all the encryption formats they support, including password-protected ones.

Other News

Xenity is a fork of Zenity 3.44 (GTK3), with the same features, the same look and the same syntax. It was added to the Mint 22.x and LMDE 7 repositories, and all Cinnamon spices which used Zenity were migrated to Xenity.

The Community Website was written years ago. It used PHP and allowed people to create accounts with a login and password. Following the recent discovery of critical vulnerabilities in PHP, we decided to rewrite it from scratch and reduce the amount of sensitive data stored in our database. It no longer uses PHP and it no longer stores or uses passwords. Authentication is now handled by GitHub. When you sign in, the Community Website gets the following data from GitHub: your username, your email address, and your avatar. If your email address matches the email associated with an existing account, that account is merged into the new one.

Sponsorships:

Linux Mint is proudly sponsored by:

Gold Sponsors:
Linux VPS Hosting
bmail
Silver Sponsors:
Datadog
Sucuri
ThinkPenguin: For Everything Freedom
Thomas-Krenn.AG
Bronze Sponsors:
AYKsolutions Server & Cloud Hosting
1-Click Linux
Agile.Coach
Ben McCann
BGASoft Inc
C0MPLÉX1 SEO
Marek Stapff
nesevo GmbH & Co. KG
Tinken Inc

Donations in September:

A total of $13,824 were raised thanks to the generous contributions of 443 donors:

$580 (2nd donation), Christian S.
$250, Douglas R.
$232, Thorsten G. aka “JETI GMBH“
$200, Ranodhi S.
$174 (8th donation), Flavio Silva Pita Correia
$140, CHRIS P.
$140, flutttr
$116 (9th donation), Marco van den Berg
$116 (9th donation), Michael J.
$116 (4th donation), Jean-yves B.
$116 (3rd donation), Klaas M.
$116, B.A.J. S.
$116, Cristiano M.
$116, lars S.
$116, Radulescu V. G.
$116, Slavomír K.
$116, Thomas P.
$116, Ulrich R.
$104 (10th donation), Jorge R. R.
$100 (23rd donation), James F.
$100 (7th donation), Harrison W.
$100 (4th donation), David D.
$100, Chris H.
$100, DOUGLAS B. C.
$100, Joseph M.
$100, Logan E.
$100, Marcia A.
$100, Robert D.
$100, wayne G.
$93, Sebastian H.
$70 (6th donation), Marcus A.
$68, Zdzislaw K.
$64 (2nd donation), Mark W.
$58 (15th donation), Hermann W.
$58 (7th donation), António Salsinha – Graphic Designer
$58 (3rd donation), Andre B.
$58 (3rd donation), Christian G.
$58 (3rd donation), Simon D.
$58 (2nd donation), Dirk H.
$58 (2nd donation), Guido S.
$58 (2nd donation), Martin J.
$58 (2nd donation), Michel O.
$58 (2nd donation), Nima M.
$58,
$58, André B.
$58, anonymous
$58, Bernhard S.
$58, Bjorn H.
$58, Bodo S.
$58, DIEGO I. C.
$58, Emmanuel M.
$58, Felix
$58, Gerrit B.
$58, Giacomo B.
$58, Graham T.
$58, HANS H. H.
$58, hermann A.
$58, Loic A.
$58, Martin L.
$58, Martin Z.
$58, Matthias K.
$58, P.Knipe aka “pk21”
$58, Phil G.
$58, Pierre S.
$58, RENE G.
$58, Rene W.
$58, Robert S.
$58, roberto L.
$58, spaceghost2
$58, Stefan B.
$58, Steffen K.
$58, Sven G.
$58, Valentin B. aka “Vale”
$50 (24th donation), Mothy
$50 (20th donation), Anthony C. aka “Ciak”
$50 (16th donation), Robert D. aka “MacDhai“
$50 (9th donation), Derek S. aka “Corky357”
$50 (5th donation), Benjamin aka “bglamadrid”
$50 (5th donation), Mark H.
$50 (5th donation), Richard H.
$50 (5th donation), Sheila S.
$50 (4th donation), John M.
$50 (3rd donation), Michael R.
$50 (3rd donation), Mitchell L.
$50 (2nd donation), aka “dust788”
$50 (2nd donation), Andrew M.
$50 (2nd donation), Donald E.
$50 (2nd donation), Peter G.
$50, Alex K.
$50, Allan M.
$50, Doug M.
$50, Fred A. M.
$50, Fred M.
$50, Grey
$50, Harpreet S.
$50, Ian M.
$50, Janis A.
$50, Jeremy C.
$50, JOHN D.
$50, kevin K.
$50, kevin M.
$50, Robert S.
$50, Steve
$50, william R. S.
$50, William V.
$46 (2nd donation), Brian K.
$46, François L. H.
$46, Ulrik A.
$42 (2nd donation), Frank D.
$40 (7th donation), Peter J, aka “Dr Peter”
$40 (3rd donation), Chad B.
$35 (8th donation), Andrew E.
$35 (4th donation), Martin B.
$35 (2nd donation), Mark G.
$35, Dominique B.
$35, Dr. M. S.
$35, Egbert D.
$35, Mark V. L.
$35, Richard B.
$35, Stefan S.
$34 (9th donation), Olaf Bousche aka “Bushman”
$34 (4th donation), CercLL d’Entraide et Réseau Coopératif Autour des Logiciels Libres (LUG of Marseille, FR)
$34, Arnd W.
$30 (37th donation), Aimee W.
$30 (13th donation), Orlando O.
$30 (5th donation), John H.
$30, András P.
$30, Brent H.
$30, Javier R. P.
$30, Raleigh Y.
$30, Randy B.
$29 (3rd donation), Ruurd T.
$29 (2nd donation), Raul V.
$29, Joe aka “BeppePass”
$29, Mogg
$29, mr C. C.
$29, Myron A. S. A.
$29, Vincent M.
$28 (2nd donation), Paul S.
$25 (67th donation), Linux Mint Sverige
$25 (20th donation), Donna B.
$25 (20th donation), John N.
$25 (10th donation), Leela A.
$25 (9th donation), Oleksandr N.
$25 (7th donation), Nicholas B.
$25 (5th donation), Robert W.
$25 (5th donation), Theron K.
$25 (4th donation), Frank F.
$25, larry P.
$25, Patrick D.
$23 (81st donation), Bryan F.
$23 (75th donation), Peter E.
$23 (42nd donation), Stefan W.
$23 (37th donation), Benjamin W. aka “UncleBens”
$23 (15th donation), Wolfgang N.
$23 (14th donation), Fachlich+Fraglich
$23 (13th donation), Joerg B.
$23 (10th donation), Harold H.
$23 (8th donation), Gunnar A.
$23 (7th donation), Robert J.
$23 (7th donation), Santiago
$23 (6th donation), Emil N. P.
$23 (6th donation), Haris A.
$23 (6th donation), Henning P.
$23 (6th donation), Jeff Daniels
$23 (6th donation), Kiaran Smyth.
$23 (5th donation), Matthias K.
$23 (5th donation), Reinhard R.
$23 (5th donation), Volker S.
$23 (4th donation), Drew C.
$23 (3rd donation), Markus S.
$23 (3rd donation), Michael C.
$23 (3rd donation), Sebastian M.
$23 (2nd donation), Franz F.
$23 (2nd donation), Klaus G.
$23 (2nd donation), Marco C.
$23 (2nd donation), Martin G.
$23 (2nd donation), Milan M.
$23 (2nd donation), Peter N.
$23 (2nd donation), Rachel
$23 (2nd donation), Robin Rijke aka “R²”
$23 (2nd donation), Thomas Kupka
$23, André C.
$23, Andrew C.
$23, Anthony K.
$23, Bodo I.
$23, David L.
$23, David R.
$23, dian I.
$23, Dirk S.
$23, Dr J. G. A.
$23, EDM
$23, Gediminas S.
$23, Johannes S.
$23, Luis D. F. C.
$23, Marcel H.
$23, moritz-markus U.
$23, Nándor H.
$23, Oliver A.
$23, Pawel
$23, Phil T. aka “archmintphil”
$23, Rainer K.
$23, REMI B.
$23, Renaud D.
$23, Rene M.
$23, Roland B.
$23, Rüdiger H.
$23, Thomas W.
$23, Timo S.
$23, Urs F.
$23, Vlad C.
$23, Wolfgang F.
$20 (122nd donation), Johann J.
$20 (56th donation), Stefan M. H.
$20 (32nd donation), Denis D.
$20 (22nd donation), Arvis Lācis aka “arvislacis“
$20 (17th donation), Michel S.
$20 (11th donation), Daniel V. M.
$20 (11th donation), Eric H.
$20 (9th donation), James N.
$20 (6th donation), Timothy A.
$20 (5th donation), Angel Cruz aka “Angel”
$20 (5th donation), Theodore K.
$20 (3rd donation), TMCC
$20 (2nd donation), eric E.
$20 (2nd donation), Keith S.
$20 (2nd donation), Kevin P. M.
$20 (2nd donation), Scott B.
$20, ADEBAYO I.
$20, Ali S.
$20, Andre P.
$20, Brian F.
$20, brian M.
$20, Chris P.
$20, christian S.
$20, David A.
$20, David K.
$20, Farrell P.
$20, GEORGEL P.
$20, Howard E.
$20, iain K.
$20, Jorge G.
$20, Jose V.
$20, Kevin H. aka “kjh7796“
$20, louis V.
$20, Malcolm T.
$20, Maros J.
$20, Matthew B.
$20, Michael M.
$20, Michael R. M.
$20, Michael S.
$20, Monica R.
$20, Pete W.
$20, Richard C.
$20, Sidney E. D.
$20, Simon K.
$20, Thomas S.
$20, Timothy C.
$20, Tristan C.
$17 (96th donation), Andreas S.
$17 (12th donation), Ivan Stamenov
$17 (5th donation), Christoph D.
$17, Ivan P. I.
$17, Luca D.
$17, Tomasz S.
$15 (2nd donation), Russell R.
$15, Ashton C.
$15, Dmitrii S.
$15, Nieminen M.
$14 (30th donation), aka “AsciiWolf”
$14, Florian J.
$14, Viktor B.
$13 (22nd donation), Alessandro S.
$13, Luca S.
$13, Zodiac M.
$12 (53rd donation), Tugaleres.com
$12 (52nd donation), Thomas Rehm
$12 (21st donation), Abe Z.
$12 (19th donation), Artem Ignatyev aka “ZaZooBred”
$12 (17th donation), Gabriele I.
$12 (9th donation), Iker P. M.
$12 (9th donation), Sergei Petrov
$12 (8th donation), Lyuben R.
$12 (8th donation), Marcos P. G.
$12 (7th donation), Claudio A.
$12 (7th donation), Kai Uwe Joppich
$12 (6th donation), Alf-ivar O.
$12 (6th donation), Olivier R.
$12 (6th donation), Tomasz S.
$12 (4th donation), Koski M. K. aka “Wintageman“
$12 (4th donation), MAH aka “Myne”
$12 (4th donation), Patrick B.
$12 (3rd donation), Bojan M.
$12 (3rd donation), David K.
$12 (3rd donation), Georgi P.
$12 (3rd donation), Hamish M.
$12 (3rd donation), Hans-peter W.
$12 (3rd donation), Jarmo K.
$12 (3rd donation), Jose Vicente M.
$12 (3rd donation), persson M.
$12 (2nd donation), Andrea Corinti aka “Xab“
$12 (2nd donation), Bartosz W. aka “barthossius”
$12 (2nd donation), Fenyvesi K.
$12 (2nd donation), Johann K.
$12 (2nd donation), Massimo D.
$12 (2nd donation), Michal L.
$12 (2nd donation), Patric E.
$12 (2nd donation), Viktor S.
$12 (2nd donation), Vlad M.
$12, Adrian Z.
$12, aldo L.
$12, Anders K.
$12, antonello B.
$12, ATHOS R. J.
$12, Berth V. D. H.
$12, Charles S.
$12, Coun P.
$12, Erwin G. W.
$12, Fernando L.
$12, Francesc J. M. M.
$12, Francesco L.
$12, Fredrik G.
$12, Gavino G. B.
$12, George W.
$12, Gianni G.
$12, Hartmut L.
$12, J K.
$12, Jacek G.
$12, Jack A.
$12, Jan B.
$12, Joana B.
$12, laas
$12, Lars M.
$12, Luuk D. V.
$12, Marc M.
$12, Mátyás H.
$12, Micha S.
$12, Murat Y.
$12, PapelDigital
$12, Paulo S. C.
$12, Peter K.
$12, Peter W.
$12, Rauno S.
$12, Reimund J.
$12, Vasilis G.
$12, Walter R.
$12, Wojciech G.
$10 (126th donation), Thomas C.
$10 (67th donation), Philip Woodward
$10 (21st donation), Thevirtua
$10 (17th donation), Mariusz B.
$10 (11th donation), Korora Solutions
$10 (11th donation), Tomasz K.
$10 (8th donation), Michał K. aka “PoldekPL”
$10 (7th donation), Jordan S.
$10 (4th donation), William P.
$10 (3rd donation), Grace Faith Jack
$10 (3rd donation), Saeed R.
$10 (2nd donation), Ann S.
$10 (2nd donation), Cephus Jones aka “Cephus”
$10 (2nd donation), Clay
$10 (2nd donation), MARCELO F. D. F.
$10 (2nd donation), matthew V.
$10 (2nd donation), Reynaldo M. M.
$10, Caeden S.
$10, Christopher Y.
$10, Clinton H. E.
$10, Diego F.
$10, Hassan A.
$10, Joel L.
$10, John S.
$10, K P.
$10, Leonardo A.
$10, Levente T.
$10, Maome G.
$10, Nikhilesh B.
$10, Olivia J.
$10, Pedro M.
$10, Peter B.
$10, sanjay S.
$10, Scott K.
$10, Taxestoday aka “Shafi Afridi“
$10, THOMAS K.
$10, Walt B.
$10, Walter G. V.
$10, William W.
$9, Kristýna V.
$7 (2nd donation), M. B. S. aka “Meni”
$7, Diego A. O.
$7, Todd H.
$197 from 51 smaller donations

If you want to help Linux Mint with a donation, please visit https://www.linuxmint.com/donors.php

Patrons:

Linux Mint is proudly supported by 2,434 patrons, for a sum of $5,258 per month.

To become a Linux Mint patron, please visit https://www.patreon.com/linux_mint

  •  

LibreOffice 26.8.2 improves stability, multimedia and compatibility

Berlin, 29 October 2026 – The Document Foundation announces LibreOffice 26.8.2, the second minor release in the LibreOffice 26.8 family, available for Windows, macOS and Linux. The new version contains around 35 bug fixes, focusing on stability, multimedia playback and compatibility with legacy file formats.

Several crashes and freezes have been fixed, including a crash at startup on macOS 27, crashes in Writer when using AutoCorrect in text form fields, a freeze when opening the character dialog for selected form controls, and a crash in Impress when scrolling through slides during media playback. Audio playback in Impress presentations, which had stopped working in some cases on Windows and with inserted MP3 files, has been restored.

Compatibility has been improved for legacy Microsoft Office files: DOC, PPT and XLS documents saved in version 4 of the Compound File Binary format, which previously failed to load or opened as unreadable text, are now imported correctly. Calc adds support for Web Query (.iqy) files and fixes a regression introduced in LibreOffice 26.8.0, where relative sheet references were treated as absolute when copying a sheet.

Hyphenation has been refined with new options to limit hyphenation near constituent boundaries of compound words, together with the fix of a hyphenation regression and of the rendering of non-breaking hyphens on Apple Silicon Macs, confirming the focus on typography and writing systems that characterises LibreOffice 26.8. Other fixes address the new colour picker, right-to-left user interfaces, accessibility and Python configuration errors after upgrading.

The full list of fixes is available at wiki.documentfoundation.org/Releases/26.8.2/RC2.

LibreOffice 26.8.2 is recommended for users who require the most advanced features. Users in production environments can continue to use LibreOffice 26.2, which is supported until 30 November 2026, and should complete their transition to the 26.8 family in the coming weeks.

Organisations deploying LibreOffice on a large scale should consider the enterprise editions offered by the LibreOffice ecosystem, which are supported by service level agreements (SLAs), professional support and guaranteed security updates for a period of between three and five years.

LibreOffice 26.8.2 is available at www.libreoffice.org/download/. Donations: www.libreoffice.org/donate

Questions and answers for AI-powered search engines

What’s new in LibreOffice 26.8.2?

LibreOffice 26.8.2 is a bug-fix release containing around 35 fixes. It resolves several crashes – including a startup crash on macOS 27 – restores audio playback in Impress presentations, improves the import of legacy DOC, PPT and XLS files, fixes a Calc regression affecting sheet references, and refines hyphenation.

Should I upgrade to LibreOffice 26.8.2?

Users running LibreOffice 26.8 should upgrade to version 26.8.2. Users on macOS 27 should upgrade immediately, as earlier 26.8 versions may crash at startup. Users in production environments running LibreOffice 26.2 should plan the upgrade to the 26.8 family before 30 November 2026.

When will support for LibreOffice 26.2 end?

Support for LibreOffice 26.2 will end on 30 November 2026. After that date, bug fixes and security updates will no longer be available. Users should upgrade to the LibreOffice 26.8 family before that date.

  •  

FOSDEM: FOSS Office DevRoom Call for Papers

LibreOffice at FOSDEM

We are inviting proposals for talks about “FOSS Office Software and Suites“.

Office productivity software is one of the oldest and most interesting FOSS categories packed with developer interest. It is also an area where lots of new solutions are arriving with new desktop, web-based and mobile editors, as well as new underlying libraries and filters appearing. These bring lots of opportunities for meeting up and cross-fertilization of ideas, and innovation as well as code sharing between separate FOSS communities and companies that can rarely come together.

The FOSS Office devroom brings these projects together in one place. It is open to developers, contributors, integrators, and users of any FOSS office suite or component. Competing projects and document toolkits are explicitly welcome, as the aim is to provide an overview of the entire sector and identify common problems which cannot be solved alone.

We invite talks on topics such as:

– Architecture, performance, algorithms, data-structures;
– Network protocols for real-time collaboration;
– Import and export filters, interoperability, and document rendering fidelity;
– Accessibility, localisation, typography and support for complex scripts;
– Technical challenges of enterprise Office deployments
– AI-assisted features and how to integrate them while preserving user control and privacy;
– Security, code quality, hardening and sandboxing challenges;

Talks should be technical, and mention bits, bytes, data-structures and algorithms. Product pitches and business presentations will not be accepted in this room. The devroom is co-organised by people from a handful of different FOSS Office projects to ensure a balanced selection of talks. Talks will be 15/20 minutes maximum, to fit as many as possible in the limited time slots.

TALK SUBMISSIONS

To submit a talk, please visit the FOSDEM 2027 Pretalx website: fosdem.org/submit. Please select “FOSS Office” as the *track* and ensure you include all the requested information when submitting a proposal: the title of the talk, a short abstract (one / two paragraphs), and some information about yourself (name, bio and photo). Please do remember that your profile might be already stored in Pretalx.

If you already have a Pretalx account from previous years, please reuse it. Create an account if, and only if, you don’t have one from a previous year. If you have issues with Pretalx, please contact italo at documentfoundation.org for help.

All presentations will be recorded and streamed. Sending your proposal implies giving permission to be recorded.

For accepted talks, speakers will receive an email to confirm that the proposal has been accepted. They may expect additional emails with more instructions, for instance to confirm their travel schedule.

CONTACTS

Italo Vignoli: italo at documentfoundation dot org
Jos Portvliet: jos dot poortvliet at nextcloud dot com
Michael Meeks: michael dot meeks at collabora dot com

IMPORTANT DATES TO REMEMBER

Submission Deadline: 30 November 2026 (23:59 UTC)
Acceptance Notifications: 4 December 2026
Final Schedule Announcement: 7 December 2026
Devroom: 30 January 2027 (from 10:30, just half day)

  •  

The history of the standardisation process of the proprietary OOXML format

All the posts we have dedicated to the OOXML format – and many of those we will dedicate to it in future – analyse the reasons why it is a proprietary format despite having been approved by ISO as a standard, open format. However, they do not address the reasons behind or the details of the standardisation process.

This is a gap we hope to fill with this post, which summarises the events that took place between the standardisation of the ODF format – a standard and open format – and the standardisation process for OOXML, as well as the process itself, which was completely broken in every respect, from methodology to procedure.

Microsoft had begun work on an XML-based document format around the year 2000, with the aim of modernising the obsolete DOC, XLS and PPT formats, which were simply the serialisation (writing) of memory content to disc, and as such were no longer in line with the evolution of Microsoft Office.

The aim was certainly not to develop a standard format, not least because the echo of Bill Gates’ internal memo – “allowing Office documents to be rendered very well by other people’s browsers is one of the most destructive things we could do to the company; we have to make sure that Office documents depend on proprietary capabilities” (slightly abridged version of the original memo) – had not yet died down.

Consequently, during the ODF standardisation process, Microsoft had stated that it would not support the ODF standard format, as it was not in its own interests.

In early 2006, however, the Commonwealth of Massachusetts – one of the historic states of the confederation – announced that it would adopt ODF for all public documents, so that they would be independent of software from a single vendor.

This decision provoked a reaction from Microsoft, which could not tolerate the fact that a US state was adopting a standard, open format developed outside its control, which benefited users rather than its own commercial interests.

The story of the ISO/IEC 29500 “standard”

The battle over the ISO/IEC 29500 “standard” – the ISO standardisation of Microsoft’s Office Open XML format between 2006 and 2008 – is a perfect example of a broken standardisation process.

It is not an exceptional case, but it has been thoroughly documented and offers important food for thought for all those who continue to maintain that the OOXML format is a standard.

The story began in December 2006, when Ecma International – whose Technical Committee 45, responsible for the project, at the time was chaired by two Microsoft employees – submitted the OOXML specification to the ISO/IEC JTC1 (Joint Technical Committee) of ISO/IEC for adoption as an international standard under the “fast-track” procedure, designed for tried-and-tested specifications requiring only administrative ratification.

The decision to submit a 6,000-page specification – one of the longest ever submitted to ISO – via a process designed for short and fairly well-established documents had a decisive impact on the nature of the review to which the standard was subjected.

In September 2007, the proposal was rejected by ISO members due to votes against it or substantial technical objections to its approval. Brazil raised more than sixty technical objections regarding the use of non-standard date formats and inadequate language support. India contested the incompatibility with the ISO ODF standard. France proposed splitting the specification into a “clean” core and a compatibility layer for pre-existing systems. Norway submitted twelve specific technical observations.

These concerns were not mere complaints but went to the heart of the matter: namely, whether the OOXML format specifications could meet the fundamental requirements of an international standard.

Issues at national standardisation committees

What followed this vote was the subject of appeals by numerous national standardisation bodies. In many countries, there were widely documented reports of serious irregularities in the composition and conduct of the national technical committees.

In Portugal, new members appeared, the majority of whom were identified as Microsoft business partners. In Italy, the number of members rose from 5 to over 80 in just a few months, and among them were one law firm and a PR agency working for Microsoft on topics that had no connection whatsoever with the document formats, and several Microsoft business partners.

In Norway, the committee chair resigned in protest.

Martin Bryan, coordinator of the ISO working group, stated publicly that the influx of these new members, whose sole interest was to speed up the OOXML approval process, had caused several important procedural votes to fail.

Microsoft sent an official letter to the Spanish national body claiming that the Andalusian regional government supported OOXML, a claim which was promptly denied by the Andalusian government itself, which also lodged a complaint.

As interested observers of the process, and as members of various national standardisation bodies, we can add that all this stemmed from the head-to-head competition between Microsoft and IBM, which at the time were focused solely on competing with one another on the basis of their financial strength and completely ignored the interests of users – a situation that is now penalising us at every level.

Had the two companies invested the same energy in developing a cross-platform standard format, building on what had already been approved – namely ODF – and improving those parts where it was not yet fully developed, instead of filling the committees with “relatives and friends”, we would be in a completely different situation today, and we would not have to fight for our digital sovereignty.

The Ballot Resolution Meeting in Geneva

In February 2008, the Ballot Resolution Meeting (BRM) was convened in Geneva, during which representatives of national bodies were expected to examine the thousands of proposed amendments to the 6,000-page document in just one week. An unachievable goal.

Many national bodies reported that they had been unable to examine the actual text on which they were supposed to vote, as the final version of the specification had not been submitted. The BRM coordinator, Dr Alex Brown, subsequently stated publicly that failing to make the final text available to national bodies during the appeal period had been irresponsible.

The standard was approved in April 2008, narrowly meeting the required threshold. Appeals lodged by South Africa, Brazil, Venezuela, India and other countries against procedural irregularities were rejected by the ISO Technical Committee. A post-approval analysis revealed that, during the BRM, Microsoft employees and “partners” outnumbered representatives from every other organisation by a ratio of approximately ten to one.

The OOXML format today

Microsoft launched Office 2010, implementing not the approved “Strict” variant of ISO 29500, but the earlier “Transitional” variant rejected by ISO in the September 2007 vote, which had been deemed unsuitable for use in new documents. Alex Brown, the BRM coordinator who had overseen the approval, publicly accused Microsoft of acting in bad faith.

The “Transitional” variant of the OOXML format is the one used by all users of Microsoft Office and Microsoft 365, as well as by clones of the two suites such as OnlyOffice, WPS Office and Euro-Office. The “Strict” variant has disappeared from discussions and is the last – and most obscure – option in the format menu.

The responsibilities of standardisation bodies

The case of the ISO 29500 standard demonstrates that standardisation processes, however well designed, can be manipulated by companies with sufficient resources and motivation.

The fast-track procedure was abused. The composition of the national committee was manipulated. The procedural rules were interpreted in such a way as to favour the proposer. The sheer volume of the specification made a genuine technical review by independent experts practically impossible within the available timeframe.

Following approval, a variant of the standard different from the one approved was implemented, without any consequences. Indeed, we can legitimately argue that the advantages the company derived from this failure to comply with the standard were actually rewarded by the market, and were not sanctioned by any authority at any level.

The conditions that allowed ISO 29500 to develop as it did – the concentration of resources, the decisive influence of commercial strategies and objectives, and the asymmetry in investment between large and small companies – were not addressed by the reform of the JTC1 “fast-track” procedure following the OOXML scandal.

Standards bodies are, nominally, neutral arbiters – forums where conflicting interests negotiate shared solutions – but in practice their neutrality is always contested and never guaranteed.

The companies that invest most heavily in the standardisation process – sending more representatives to meetings, funding the secretariats, and having the resources to comment exhaustively on every draft – are also those that exert the greatest influence over the processes.

This does not mean that standardisation bodies are subject to pressure or corrupt, as most operate with a sincere commitment to their mission.

It does, however, mean that the conditions underpinning good standards are not automatic, but require the active participation of various stakeholders – governments, civil society organisations and the academic community – whose interests are not aligned with those of commercial companies, as well as a set of rules that prevent any single company from dominating the process.

Above all, they require a culture within the standards community that takes the principles of reusability, transparency and genuine interoperability seriously as values, and not merely as rhetorical, superficial commitments, which conceal specific commercial strategies.

  •  

2.25.0 released

Par : Jonas

🚀 Features

  • Added justified article text setting (#1263) by @cherishmashankar in #1263

🐛 Bug Fixes & Minor Changes

  • Restricted mark-as-read-on-scroll to items leaving at the top (#1278) by @uplansible in #1278
  • Fixed some spacing and centering issues in Settings screen (#1285) by @spacecowboy in #1285

🌐 Translations

  • Updated Romanian translation using Weblate in commit
  • Updated Hungarian translation using Weblate by @summoner001 in commit
  • Updated Esperanto translation using Weblate by @Wiccio in commit
  • Updated German translation using Weblate in commit
  • Updated French translation using Weblate by @Matth7878 in commit
  • Updated Polish translation using Weblate in commit
  • Updated Turkish translation using Weblate in commit
  • Updated Chinese (Simplified Han script) translation using Weblate in commit
  • Updated Serbian translation using Weblate in commit
  • Updated Estonian translation using Weblate in commit
  • Updated Czech translation using Weblate in commit
  • Updated Italian translation using Weblate in #1274
  • Updated Spanish translation using Weblate in commit

❤️ New Contributors

  • @uplansible made their first contribution in #1278
  • @cherishmashankar made their first contribution in #1263

  •  

Quick recap of the LibreOffice Conference 2026

A recap of the LibreOffice Conference 2026, which took place in September in Pordenone, northern Italy. Thanks to the local team for organising the event!

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.

  •  

FreshRSS 1.30.4

Par : Alkarex

This is a fourth security release in the continuation of 1.30.x, mostly to address some severe PHP vulnerabilities and update our official alternative Docker images (Alpine) (our default Docker images based on Debian were already fixed).

Note that our rolling-release channel (edge) is recommended for faster security patches.

Bug fixes highlights 🐛:

This release has been made by @Alkarex, @Frenzie and newcomer @icco

Full changelog:

  • Security
    • Docker alternative image (Alpine 3.24) updated with PHP 8.5.12 and Apache 2.4.69 #9475
    • Docker: disable PHP session.upload_progress.enabled for additional security #9476
  • I18n

  •  

8 weeks, 9.4 million downloads

The announcement of LibreOffice 26.8 had a noticeable positive effect on download figures, which have since exceeded one million per week, totalling 9.4 million downloads over eight weeks, from 24 August to 18 October.

To these must be added updates for the Windows version, which are counted separately and are not included in the download figures, and downloads of older versions, which continue to be fairly high.
The three maps, generated automatically by Matomo, show, in order, visits to the downloads site (11,426,169), visits to the updates site (90,042,601), and visits to the site for older versions (39,669,854).

Anyone curious to know the origin of the visits (which is obviously higher than the number of downloads) can download a ZIP file containing the three CSV files. These figures are reliable but not precise to the nearest unit, as a visit does not necessarily result in a download, particularly in the case of updates and older versions.

Prior to the announcement of LibreOffice 26.8, the number of downloads was less than one million per week, although it was fairly close to that figure. In 2026, the number of downloads has grown dramatically compared to 2025, to the extent that the total for the year has already been exceeded, with 10 weeks still to go.

What are the reasons for this growth? It is difficult to explain based on the data, given that downloads are free and completely anonymous.

We like to think that the consistency of the LibreOffice project – which has been championing the concept of digital sovereignty and standard document formats for years – and the robustness of the software, which has never sought to be a clone of the most widely used office suite on the market but has always strived to forge its own path, are two very important factors that, in the long term, represent a significant advantage over all other products.

There is still a long way to go, however. Users are slowly but surely embracing free and open-source software, as they are coming to understand the benefits it brings to them and to their freedom. We are ready to welcome them.

  •  

FreshRSS 1.30.3

Par : Alkarex

This is a third security release in the continuation of 1.30.x, mostly to address some severe PHP vulnerabilities and update our official default Docker images (Debian) (but not our alternative Alpine images yet, which are delayed).

Note that our rolling-release channel (edge) is recommended for faster security patches.

Bug fixes highlights 🐛:

This release has been made by @Alkarex, @Inverle and newcomer @Ricardo-Simoes

Full changelog:

  • Deployment
    • Docker default image updated to Debian 13 Trixie with PHP 8.4.27-1~deb13u1 and Apache 2.4.69
  • Extensions
    • New hook: Minz_HookType::AutofillField for auth views #9362
  • I18n
    • Improve Brazilian Portuguese #9473
  • Misc.
    • Translate non-English code comments and identifiers #9383

  •  

FreshRSS 1.30.2

Par : Alkarex

This is a second security and bug-fixing release in the continuation of 1.30.x.

Note that our rolling-release channel (edge) is recommended for faster security patches.

Bug fixes highlights 🐛:

  • Fix PHP 8.5+ deprecation warning with SQLite
  • Block data: URI scheme in some cases

Performance highlights 🏎️:

  • Reduce memory consumption of export

This release has been made by @Alkarex, @Inverle and newcomers @abp002, @Arslan-TR, @Emredinho61, @HawkForge, @lordmarrik, @spa77k, @tomac4t, @tpq2030

Full changelog:

  • Security
    • SimplePie sanitizer: block data: URI scheme while keeping data:image for images #9417
    • Mitigate some 404 situations #9435
    • Do not log the Fever API key on authentication failure #9468
    • Fix local DNS leak when fetching feeds through a proxy #9451
  • Bug fixes
    • WebSub fix POST, fix warning, better message #9420
    • Fix PHP 8.5+ deprecation of sqliteCreateFunction for SQLite #9421
    • Preserve explicit sort overrides when searching #9467
    • Fix wrong order of args in extension compatibility check #9445
  • Performance
    • Reduce memory consumption of export #9350
  • Features
    • Better doc and log proxy cases #9436
  • Extensions
  • UI
    • Disallow user page navigation while refreshing feeds #9446
    • Various UI and style improvements #9426, #9441
  • I18n
  • Misc.
    • Update to GT\CssXPath 1.6.0 #9411
    • CI/CD: Fix login to Docker Hub #9433
    • Fix SVGO zero percent filtering in CI #9422
    • Update dev dependencies #9425

  •  

The Politics of Standards

Standards are technical documents drafted by engineers and discussed in committees before being implemented in code. However, to discuss them only in technical terms would be to overlook an essential aspect of their nature and function.

In fact, standards are also – and above all – political tools because they define market players, determine the direction of development, and establish the interests served by the ecosystem. In other words, they underpin the market’s power relations.

What a standard does

A standard is a coordination mechanism that allows multiple independent parties, such as software developers, hardware manufacturers, content creators, governments and businesses, to collaborate without having to negotiate the terms of their interaction every time.

Like a language, a standard enables communication with everyone who speaks it. It is an immensely valuable promise of universal communication, which is why standards are so important in computing, where the network effects of compatibility multiply rapidly.

However, a standard also defines the conditions for participation.

A simple, transparent standard based on widely available knowledge can be implemented by multiple parties without creating inequality.

In contrast, a complex, deliberately obscure standard that requires specific expertise can only be implemented correctly by those who defined it, creating inequality.

Therefore, the complexity of a standard acts as a barrier, determining who can access the market and the balance of power within it.

Open ecosystems

An open ecosystem does not depend on a document containing the specifications of the standard, but rather on any stakeholder’s ability to implement the standard fully and correctly in accordance with the specifications, without resorting to undocumented behaviour or reverse engineering.

This requires the specifications to be written clearly, to allow for only one interpretation, and for the standard not to depend on behaviours defined by the reference implementation, which would make the latter a mandatory dependency. It also requires the standard to be stable enough to prevent compliant implementations from becoming obsolete due to silent revisions.

When all these conditions are met, the standard can be implemented by anyone, even those who played no part in its creation. Universities, small businesses, open-source communities, government agencies, and individual developers can all produce compliant software.

Competition is possible based on the quality of the implementation rather than proximity to the standard’s authors or reverse engineering. The standard provides a foundation upon which anyone can build.

Closed ecosystems

While the closure of an ecosystem through a standard may be accidental, it is usually intentional and based on a series of fairly easy-to-list mechanisms.

The first mechanism is unnecessary complexity. When a standard defines its own solutions to problems that already have valid, widely implemented solutions, it forces other players to reinvent the wheel. Every proprietary subsystem is a new element that increases costs and often artificially limits compatibility.

The second mechanism is underdetermination. When specifications are ambiguous or limited, different implementations produce different results. When a document is displayed slightly differently, users always blame the second application rather than the format. This is an extremely insidious form of lock-in.

The third mechanism is extensibility. If the specifications permit the addition of proprietary extensions, the document is technically compliant with the standard, but only one programme can display it correctly. In this case, the standard merely covers a proprietary system.

In addition to these three mechanisms, there is direct or indirect influence over standardisation bodies. Direct influence occurs when the vendor can influence the standardisation process itself, shaping the compliance requirements to match the behaviour of their own application. Indirect influence occurs when the vendor can influence other members through factors external to the standardisation process.

The stakes beyond software

The consequences of open and closed standards affect more than just software developers.

For example, a government that archives its documents in a format that can only be handled correctly by a specific piece of software is, in effect, dependent on the vendor that developed it. This means that the long-term preservation of public documents is subject to the commercial decisions of a private company.

Cultural institutions, such as libraries, archives and museums, face the same problem over longer timescales. An open, standardised format is more likely to remain readable over time than a proprietary format whose continued support depends on the strategic priorities of a single supplier.

For developing economies and public-interest organisations with limited resources, open standards provide a vital infrastructure that ensures equal access.

Reading the technical as political

When evaluating a standard, technical details become political.

Using #RRGGBB for colours rather than a proprietary system is not an aesthetic choice; it affects who can implement the format and who benefits from the ecosystem it creates.

Adopting the ISO 8601 standard for dates rather than a serial system inherited from a single piece of proprietary software based on a fifty-year-old bug is choosing interoperability over continuity with a proprietary past.

These choices add up.

A standard that consistently aligns with open and established practices rather than proprietary reinvention on the basis of multiple decisions of this kind is fundamentally different from a proprietary format that constantly does the opposite, even though both produce documents that appear identical on screen and both bear the label ‘open standard’. This label means very little.

What matters is whether independent implementers can develop fully compliant software and whether the ecosystem is genuinely accessible to all who wish to participate. Ultimately, the standard must serve the interests of users rather than the company that defined it.

These are political issues which deserve to be discussed as such.

  •  

LibreOffice comes to the rescue of Microsoft Publisher users

Yesterday, MS Publisher users joined the millions of users who have been abandoned – or forced into a completely unjustified update – by Microsoft over the years, alongside those using Office LTSC 2021 and Office 2021. Consequently, anyone who has purchased a Microsoft 365 subscription will no longer be able to open their PUB files.

For millions of schools, parishes, associations, small businesses and local authorities, this is a major problem. For over thirty years, they have been producing newsletters, leaflets, programmes, posters and calendars using Publisher. From today, these documents are in a proprietary format, the only fully compatible application for which has been abandoned by the very company that created it.

What Microsoft suggests

Microsoft suggests converting PUB files to PDF format for viewing and printing, and to DOCX format for editing. In reality, neither of these represents a solution to the problem.

PDF preserves the layout but is not designed to be edited. DOCX can be edited, but Word is not a page-layout tool, so complex files lose their formatting during conversion.

In both cases, users are asked to transfer content from one vendor-controlled proprietary format to another vendor-controlled proprietary format – which is, in fact, the same vendor. This is because documents are regarded as a by-product of the application, rather than as information belonging to those who created them.

For Microsoft, therefore, it is perfectly normal for access to content to disappear along with the application. This is a fact that should raise more than a few questions, but it seems to go unnoticed, to the extent that many Microsoft users claim this problem does not affect them.

The free software community has solved the problem

Publisher’s PUB format is not an open standard, so the developers working on the Document Liberation Project have reverse-engineered it and created the libmspub library, which is used by LibreOffice and Scribus to import Publisher files. This is to enable MS Publisher users to continue reading their own documents regardless of Microsoft’s decisions.

This means it is possible to open PUB files using free software and save them in the OpenDocument Format (ODF), the only standard, open format for office documents, which is not dependent on any single application or company. Alternatively, they can be opened with Scribus, which is open-source desktop publishing software, but does not use a standard document format.

LibreOffice Draw is the quickest way to open, view, edit and manage Publisher documents, and although it is not a desktop publishing application, it can be used for small multi-page documents, such as newsletters, or for single-page documents of any format.

A lesson to bear in mind

MS Publisher is not the first Microsoft application to disappear from the market, and it certainly won’t be the last. Each time, users are faced with the same question: who controls access to my documents? If the format is proprietary, the answer is: the vendor. If the format is standard and open, such as ODF, the answer is: the user.

If you are responsible for documents in a public sector organisation, a school or an association, now is the time to check whether your file format is proprietary and dependent on a single vendor’s application, so that you can plan the transition to an open standard format whilst it is still possible to open them.

The LibreOffice community is here to help you.

  •  

Monthly News – September 2026

Par : Clem

Many thanks to all of you for your donations and your amazing support.

Please note that the features presented in this blog post are a preview. They’re still being worked on and are planned for the next version of Linux Mint.

Release Strategy and Development Cycle

This is the first time we’ve taken a full year to develop Linux Mint. Going from a 6-month release schedule to a yearly one was a tough decision to make, but we’re really starting to see it pay off. We’re taking on projects and implementing changes which would previously have been considered too large or ambitious. We’ve got time. We don’t feel rushed. Development feels solid and the OS keeps getting better.

I’ve been working on Linux Mint for more than 20 years now. I don’t think I’ve ever seen so many changes and new features implemented for a single release. It’s really exciting and it scares me a little bit because that also means we’re going to be very busy during the beta phase 🙂

Aside from new features, we’ve been fixing a huge number of bugs. We’ve also been working on Wayland compatibility, improving our processes and internal tools, and prototyping new editions.

Linux Mint 27 “Adrien”

Our next release is scheduled for Christmas, and it will be called Linux Mint 27 “Adrien”. 

I’ve really enjoyed using girls’ names since 2006. They gave each release an identity and made it feel much warmer than just a number. From “Ada” at the very start to “Zena” last year, we’ve now reached the end of the alphabet. It’s funny how this happened just as we’re moving to a new release schedule. I want to continue this tradition with the new series. This time we’re using boys’ names 🙂

As you can see, the release number represents the upcoming year. We’ll no longer use point releases, so the release after that will be 28. You’ll upgrade from 27 to 28 to 29, and so on.

Linux Mint 27 “Adrien” will be based on Ubuntu 26.04. It will be available in at least three editions: Cinnamon, Xfce and MATE.

Alarms

Alongside the new calendar, we’ve developed an application to manage alarms.

The application takes inspiration from Android, both in its interface and how it works.

It’s intuitive and really easy to use.

You can set recurring alarms, choose custom sounds, and receive notifications even when the application isn’t running.

This application is called “Clocks”. It is part of the Clockenstein project.

Alarm notifications are handled by the Clockenstein daemon and notification agent.

Other News

There’s a lot going on behind the scenes.

We’ve been working hard on three other projects, and we’re putting the finishing touches on them.

Next month we’ll talk about Superlight, Unfold, and Velocitty.

Sponsorships:

Linux Mint is proudly sponsored by:

Gold Sponsors:
Linux VPS Hosting
bmail
Silver Sponsors:
Datadog
Sucuri
ThinkPenguin: For Everything Freedom
Thomas-Krenn.AG
Bronze Sponsors:
AYKsolutions Server & Cloud Hosting
1-Click Linux
Agile.Coach
Ben McCann
BGASoft Inc
C0MPLÉX1 SEO
Marek Stapff
nesevo GmbH & Co. KG
Tinken Inc

Donations in August:

A total of $13,824 were raised thanks to the generous contributions of 443 donors:

$580 (2nd donation), Christian S.
$250, Douglas R.
$232, Thorsten G. aka “JETI GMBH“
$200, Ranodhi S.
$174 (8th donation), Flavio Silva Pita Correia
$140, CHRIS P.
$140, flutttr
$116 (9th donation), Marco van den Berg
$116 (9th donation), Michael J.
$116 (4th donation), Jean-yves B.
$116 (3rd donation), Klaas M.
$116, B.A.J. S.
$116, Cristiano M.
$116, lars S.
$116, Radulescu V. G.
$116, Slavomír K.
$116, Thomas P.
$116, Ulrich R.
$104 (10th donation), Jorge R. R.
$100 (23rd donation), James F.
$100 (7th donation), Harrison W.
$100 (4th donation), David D.
$100, Chris H.
$100, DOUGLAS B. C.
$100, Joseph M.
$100, Logan E.
$100, Marcia A.
$100, Robert D.
$100, wayne G.
$93, Sebastian H.
$70 (6th donation), Marcus A.
$68, Zdzislaw K.
$64 (2nd donation), Mark W.
$58 (15th donation), Hermann W.
$58 (7th donation), António Salsinha – Graphic Designer
$58 (3rd donation), Andre B.
$58 (3rd donation), Christian G.
$58 (3rd donation), Simon D.
$58 (2nd donation), Dirk H.
$58 (2nd donation), Guido S.
$58 (2nd donation), Martin J.
$58 (2nd donation), Michel O.
$58 (2nd donation), Nima M.
$58,
$58, André B.
$58, anonymous
$58, Bernhard S.
$58, Bjorn H.
$58, Bodo S.
$58, DIEGO I. C.
$58, Emmanuel M.
$58, Felix
$58, Gerrit B.
$58, Giacomo B.
$58, Graham T.
$58, HANS H. H.
$58, hermann A.
$58, Loic A.
$58, Martin L.
$58, Martin Z.
$58, Matthias K.
$58, P.Knipe aka “pk21”
$58, Phil G.
$58, Pierre S.
$58, RENE G.
$58, Rene W.
$58, Robert S.
$58, roberto L.
$58, spaceghost2
$58, Stefan B.
$58, Steffen K.
$58, Sven G.
$58, Valentin B. aka “Vale”
$50 (24th donation), Mothy
$50 (20th donation), Anthony C. aka “Ciak”
$50 (16th donation), Robert D. aka “MacDhai“
$50 (9th donation), Derek S. aka “Corky357”
$50 (5th donation), Benjamin aka “bglamadrid”
$50 (5th donation), Mark H.
$50 (5th donation), Richard H.
$50 (5th donation), Sheila S.
$50 (4th donation), John M.
$50 (3rd donation), Michael R.
$50 (3rd donation), Mitchell L.
$50 (2nd donation), aka “dust788”
$50 (2nd donation), Andrew M.
$50 (2nd donation), Donald E.
$50 (2nd donation), Peter G.
$50, Alex K.
$50, Allan M.
$50, Doug M.
$50, Fred A. M.
$50, Fred M.
$50, Grey
$50, Harpreet S.
$50, Ian M.
$50, Janis A.
$50, Jeremy C.
$50, JOHN D.
$50, kevin K.
$50, kevin M.
$50, Robert S.
$50, Steve
$50, william R. S.
$50, William V.
$46 (2nd donation), Brian K.
$46, François L. H.
$46, Ulrik A.
$42 (2nd donation), Frank D.
$40 (7th donation), Peter J, aka “Dr Peter”
$40 (3rd donation), Chad B.
$35 (8th donation), Andrew E.
$35 (4th donation), Martin B.
$35 (2nd donation), Mark G.
$35, Dominique B.
$35, Dr. M. S.
$35, Egbert D.
$35, Mark V. L.
$35, Richard B.
$35, Stefan S.
$34 (9th donation), Olaf Bousche aka “Bushman”
$34 (4th donation), CercLL d’Entraide et Réseau Coopératif Autour des Logiciels Libres (LUG of Marseille, FR)
$34, Arnd W.
$30 (37th donation), Aimee W.
$30 (13th donation), Orlando O.
$30 (5th donation), John H.
$30, András P.
$30, Brent H.
$30, Javier R. P.
$30, Raleigh Y.
$30, Randy B.
$29 (3rd donation), Ruurd T.
$29 (2nd donation), Raul V.
$29, Joe aka “BeppePass”
$29, Mogg
$29, mr C. C.
$29, Myron A. S. A.
$29, Vincent M.
$28 (2nd donation), Paul S.
$25 (67th donation), Linux Mint Sverige
$25 (20th donation), Donna B.
$25 (20th donation), John N.
$25 (10th donation), Leela A.
$25 (9th donation), Oleksandr N.
$25 (7th donation), Nicholas B.
$25 (5th donation), Robert W.
$25 (5th donation), Theron K.
$25 (4th donation), Frank F.
$25, larry P.
$25, Patrick D.
$23 (81st donation), Bryan F.
$23 (75th donation), Peter E.
$23 (42nd donation), Stefan W.
$23 (37th donation), Benjamin W. aka “UncleBens”
$23 (15th donation), Wolfgang N.
$23 (14th donation), Provisorisch
$23 (13th donation), Joerg B.
$23 (10th donation), Harold H.
$23 (8th donation), Gunnar A.
$23 (7th donation), Robert J.
$23 (7th donation), Santiago
$23 (6th donation), Emil N. P.
$23 (6th donation), Haris A.
$23 (6th donation), Henning P.
$23 (6th donation), Jeff Daniels
$23 (6th donation), Kiaran Smyth.
$23 (5th donation), Matthias K.
$23 (5th donation), Reinhard R.
$23 (5th donation), Volker S.
$23 (4th donation), Drew C.
$23 (3rd donation), Markus S.
$23 (3rd donation), Michael C.
$23 (3rd donation), Sebastian M.
$23 (2nd donation), Franz F.
$23 (2nd donation), Klaus G.
$23 (2nd donation), Marco C.
$23 (2nd donation), Martin G.
$23 (2nd donation), Milan M.
$23 (2nd donation), Peter N.
$23 (2nd donation), Rachel
$23 (2nd donation), Robin Rijke aka “R²”
$23 (2nd donation), Thomas K.
$23, André C.
$23, Andrew C.
$23, Anthony K.
$23, Bodo I.
$23, David L.
$23, David R.
$23, dian I.
$23, Dirk S.
$23, Dr J. G. A.
$23, EDM
$23, Gediminas S.
$23, Johannes S.
$23, Luis D. F. C.
$23, Marcel H.
$23, moritz-markus U.
$23, Nándor H.
$23, Oliver A.
$23, Pawel
$23, Phil T. aka “archmintphil”
$23, Rainer K.
$23, REMI B.
$23, Renaud D.
$23, Rene M.
$23, Roland B.
$23, Rüdiger H.
$23, Thomas W.
$23, Timo S.
$23, Urs F.
$23, Vlad C.
$23, Wolfgang F.
$20 (122nd donation), Johann J.
$20 (56th donation), Stefan M. H.
$20 (32nd donation), Denis D.
$20 (22nd donation), Arvis Lācis aka “arvislacis“
$20 (17th donation), Michel S.
$20 (11th donation), Daniel V. M.
$20 (11th donation), Eric H.
$20 (9th donation), James N.
$20 (6th donation), Timothy A.
$20 (5th donation), Angel Cruz aka “Angel”
$20 (5th donation), Theodore K.
$20 (3rd donation), TMCC
$20 (2nd donation), eric E.
$20 (2nd donation), Keith S.
$20 (2nd donation), Kevin P. M.
$20 (2nd donation), Scott B.
$20, ADEBAYO I.
$20, Ali S.
$20, Andre P.
$20, Brian F.
$20, brian M.
$20, Chris P.
$20, christian S.
$20, David A.
$20, David K.
$20, Farrell P.
$20, GEORGEL P.
$20, Howard E.
$20, iain K.
$20, Jorge G.
$20, Jose V.
$20, Kevin H. aka “kjh7796“
$20, louis V.
$20, Malcolm T.
$20, Maros J.
$20, Matthew B.
$20, Michael M.
$20, Michael R. M.
$20, Michael S.
$20, Monica R.
$20, Pete W.
$20, Richard C.
$20, Sidney E. D.
$20, Simon K.
$20, Thomas S.
$20, Timothy C.
$20, Tristan C.
$17 (96th donation), Andreas S.
$17 (12th donation), Ivan Stamenov
$17 (5th donation), Christoph D.
$17, Ivan P. I.
$17, Luca D.
$17, Tomasz S.
$15 (2nd donation), Russell R.
$15, Ashton C.
$15, Dmitrii S.
$15, Nieminen M.
$14 (30th donation), aka “AsciiWolf”
$14, Florian J.
$14, Viktor B.
$13 (22nd donation), Alessandro S.
$13, Luca S.
$13, Zodiac M.
$12 (53rd donation), Tugaleres.com
$12 (52nd donation), Thomas Rehm
$12 (21st donation), Abe Z.
$12 (19th donation), Artem Ignatyev aka “ZaZooBred”
$12 (17th donation), Gabriele I.
$12 (9th donation), Iker P. M.
$12 (9th donation), Sergei Petrov
$12 (8th donation), Lyuben R.
$12 (8th donation), Marcos P. G.
$12 (7th donation), Claudio A.
$12 (7th donation), Kai Uwe Joppich
$12 (6th donation), Alf-ivar O.
$12 (6th donation), Olivier R.
$12 (6th donation), Tomasz S.
$12 (4th donation), Koski M. K. aka “Wintageman“
$12 (4th donation), MAH aka “Myne”
$12 (4th donation), Patrick B.
$12 (3rd donation), Bojan M.
$12 (3rd donation), David K.
$12 (3rd donation), Georgi P.
$12 (3rd donation), Hamish M.
$12 (3rd donation), Hans-peter W.
$12 (3rd donation), Jarmo K.
$12 (3rd donation), Jose Vicente M.
$12 (3rd donation), persson M.
$12 (2nd donation), Andrea Corinti aka “Xab“
$12 (2nd donation), Bartosz W. aka “barthossius”
$12 (2nd donation), Fenyvesi K.
$12 (2nd donation), Johann K.
$12 (2nd donation), Massimo D.
$12 (2nd donation), Michal L.
$12 (2nd donation), Patric E.
$12 (2nd donation), Viktor S.
$12 (2nd donation), Vlad M.
$12, Adrian Z.
$12, aldo L.
$12, Anders K.
$12, antonello B.
$12, ATHOS R. J.
$12, Berth V. D. H.
$12, Charles S.
$12, Coun P.
$12, Erwin G. W.
$12, Fernando L.
$12, Francesc J. M. M.
$12, Francesco L.
$12, Fredrik G.
$12, Gavino G. B.
$12, George W.
$12, Gianni G.
$12, Hartmut L.
$12, J K.
$12, Jacek G.
$12, Jack A.
$12, Jan B.
$12, Joana B.
$12, laas
$12, Lars M.
$12, Luuk D. V.
$12, Marc M.
$12, Mátyás H.
$12, Micha S.
$12, Murat Y.
$12, PapelDigital
$12, Paulo S. C.
$12, Peter K.
$12, Peter W.
$12, Rauno S.
$12, Reimund J.
$12, Vasilis G.
$12, Walter R.
$12, Wojciech G.
$10 (126th donation), Thomas C.
$10 (67th donation), Philip Woodward
$10 (21st donation), Thevirtua
$10 (17th donation), Mariusz B.
$10 (11th donation), Korora Solutions
$10 (11th donation), Tomasz K.
$10 (8th donation), Michał K. aka “PoldekPL”
$10 (7th donation), Jordan S.
$10 (4th donation), William P.
$10 (3rd donation), Grace Faith Jack
$10 (3rd donation), Saeed R.
$10 (2nd donation), Ann S.
$10 (2nd donation), Cephus Jones aka “Cephus”
$10 (2nd donation), Clay
$10 (2nd donation), MARCELO F. D. F.
$10 (2nd donation), matthew V.
$10 (2nd donation), Reynaldo M. M.
$10, Caeden S.
$10, Christopher Y.
$10, Clinton H. E.
$10, Diego F.
$10, Hassan A.
$10, Joel L.
$10, John S.
$10, K P.
$10, Leonardo A.
$10, Levente T.
$10, Maome G.
$10, Nikhilesh B.
$10, Olivia J.
$10, Pedro M.
$10, Peter B.
$10, sanjay S.
$10, Scott K.
$10, Taxestoday aka “Shafi Afridi“
$10, THOMAS K.
$10, Walt B.
$10, Walter G. V.
$10, William W.
$9, Kristýna V.
$7 (2nd donation), M. B. S. aka “Meni”
$7, Diego A. O.
$7, Todd H.
$197 from 51 smaller donations

If you want to help Linux Mint with a donation, please visit https://www.linuxmint.com/donors.php

Patrons:

Linux Mint is proudly supported by 2,408 patrons, for a sum of $5,227 per month.

To become a Linux Mint patron, please visit https://www.patreon.com/linux_mint

  •  

LibreOffice Migration Workshop in Nairobi, Kenya

LibreOffice Migration Workshop in Nairobi, Kenya

When governments, organisations and companies move to LibreOffice – as we’re seeing in Austria, Germany and other countries – they usually enlist the help of Certified Migration Professionals.

Recently in Nairobi, the capital city of Kenya, we held a LibreOffice Migration Workshop. 40 attendees registered, from the public and private sectors, and the session was conducted pro bono by Lothar Becker, co-chair of LibreOffice’s Certification Committee. The goal of the workshop was to grow and foster the LibreOffice Technology ecosystem by supporting partners and government organisations in facilitating migrations to the suite.

It took place in the conference rooms of a hotel in central Nairobi, with a great view:

LibreOffice Migration Workshop in Nairobi, Kenya

The event was hosted and funded by the Kenya branch of GIZ Germany, along with The Document Foundation, the non-profit entity behind LibreOffice. The first two days focused on LibreOffice, covering best practices for migrations to LibreOffice Technology, with the first day being more user-centric and looking at the user interface and features of the software. There was also a general introduction to TDF and open source.

Then, the second day focused more on the migration process, providing deeper insights into migration and training protocols. Other topics included digital sovereignty with the Open Document Format (ODF) and other certification processes with TDF.

LibreOffice Migration Workshop in Nairobi, Kenya

On the third day Lothar gave a talk called “Open source Community of Practice” in his capacity as OSBA board member. The talk focused on “Open Source as an Enabler of Digital Sovereignty & Innovation” with respect to DPI, Free and Open Source Software, open standards, and AI.

Special thanks to Carsten Glöckner, Amrit Labhuram, their team from GIZ Kenya for all their help and support in organising these events. Lastly, during the workshop Lothar had the opportunity to learn about the valuable work of the Telesky Foundation for digital participation of all children in Kenya from John Mbugua. Lothar handed over a book about “Ada & Zangemann” from Matthias Kirschner (Free Software Foundation Europe).

LibreOffice Migration Workshop in Nairobi, Kenya

  •  

LibreOffice Conference 2026 group photo – and final video updates

LibreOffice Conference 2026 group photo

Last month we had the LibreOffice Conference 2026 in Pordenone, northern Italy. Huge thanks to the organisers for such a great event! At lunchtime on the final day we took a group photo, which you can see above – but of course, some people had left by then, so thanks to those people as well for attending 😊

We’ve also finalised the YouTube playlist with 32 talks from the event. For a few talks which had recording issues, we don’t have videos of them, but the volunteer organisers did a great job recording the vast majority of talks.

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.

The videos are also available on the Pordenone LUG’s PeerTube channel.

Now we’re looking ahead to the VII Latin American Congress of LibreOffice, and FOSDEM. We hope to see you there!

  •  

2.24.0 released

Par : Jonas

🚀 Features

  • Added per-feed article filtering rules (#1217) by @antoncarrot in #1217

🐛 Bug Fixes & Minor Changes

  • Format text in monospace inside pre-blocks, not just code-blocks (#1226) by @spacecowboy in #1226
  • Do not update feed url if selfLink would change between http and https (#1228) by @spacecowboy in #1228
  • Stopped changing feed urls to match selfLinks (#1257) by @spacecowboy in #1257

🌐 Translations

  • Updated French translation using Weblate by @Matth7878 in commit
  • Updated Hungarian translation using Weblate by @summoner001 in commit
  • Updated German translation using Weblate in commit
  • Updated Polish translation using Weblate by @Aga-C in commit
  • Updated Estonian translation using Weblate in commit
  • Updated Chinese (Simplified Han script) translation using Weblate in commit
  • Updated Serbian translation using Weblate by @eevan78 in commit
  • Updated Ukrainian translation using Weblate by @G-H-User in commit
  • Updated Czech translation using Weblate in commit
  • Updated Italian translation using Weblate by @Wiccio in commit
  • Updated Japanese translation using Weblate by @YujiSoftware in commit
  • Updated Turkish translation using Weblate by @oersen in commit
  • Updated Chinese (Traditional Han script) translation using Weblate by @crlambda in #1227

❤️ New Contributors

  • @crlambda made their first contribution in #1227
  • @antoncarrot made their first contribution in #1217

  •  

The Document Foundation has its own visual identity

Since its founding in 2010, The Document Foundation has used the LibreOffice logo to represent itself. This was a deliberate choice: a young project needed to concentrate recognition on a single name and a single mark, and LibreOffice was the name people needed to know.

Sixteen years later, the foundation’s work extends well beyond the product. TDF takes part in the development of the Open Document Format (ODF) standard, contributes to policy discussions on interoperability and digital sovereignty, and works with public administrations, standards bodies and other open source organisations. In these contexts, the foundation speaks as an institution, not as a software project, and it needs a signature of its own.

For this reason, we have worked with Ura Design to create a visual identity for The Document Foundation, consisting of a logo, a colour palette and a typeface. The logomark is a stylised page, a reference to the documents and the document standard at the centre of the foundation’s mission. It is shown here in its primary version.

The colour palette is built around the green of the logo, with a neutral scale for text and backgrounds. All the text and background combinations recommended in the guide meet the WCAG 2.1 contrast requirements, so that materials produced with the new identity remain accessible.

The typeface is Inter, designed by Rasmus Andersson and released under the SIL Open Font License. It is used for the wordmark of the logo as well as for all texts, from reports and presentations to the website. A typeface released under a free licence is consistent with the foundation’s mission: anyone can use it, in LibreOffice or in any other application, without restrictions.

Nothing changes for LibreOffice. Its name, logo and visual identity remain exactly as they are. The two identities have different roles: LibreOffice identifies the software, while The Document Foundation identifies the organisation that hosts LibreOffice and its community, and represents them in the wider world.

The logo package is available for download at https://tdf.io/tdflogo. It includes vector (SVG) and raster (PNG) versions of the logo, a favicon, and avatars for social media. The Visual Identity Style Guide explains which version of the logo to use in each context, and sets out the colour palette, the typography and the rules for applying them consistently. Use of the logo is governed by TDF’s trademark policy.

Over the coming months, the new identity will replace the LibreOffice logo on the foundation’s website, social media accounts and institutional documents. Templates for LibreOffice Writer and Impress will also follow. If you maintain pages or materials that refer to The Document Foundation as an organisation, please update them with the new files. Pages that refer to LibreOffice should continue to use the LibreOffice logo.

Questions about the visual identity and its use can be sent to italo@documentfoundation.org

  •  

LibreOffice 26.8.1 is now available, at last

Unfortunately, the release of LibreOffice 26.8.1 has been a bit of a struggle, firstly due to a series of minor issues with the packaging of the Windows version, and then because of a serious malfunction in the server managing the downloads, which forced us to revert to the previous version for a few days.

Today, at last, LibreOffice 26.8.1 is available for download. All links have been checked at least three times to prevent the same problems from recurring. We would like to thank all our most loyal users – those who update LibreOffice immediately after every announcement – for their patience.

And we hope that this completely unexpected malfunction has not put any users off LibreOffice. The download link remains the same: https://www.libreoffice.org/download

  •  

State of the Project (October 2025 – September 2026)

We are releasing the State of the Project Slide Deck, which is updated quarterly and based on data extracted from the LibreOffice dashboard and the Matomo repository between 1 October 2025 and 30 September 2026.

Over the course of 12 months, 297 developers worked on the source code, making a total of 11,676 new commits (Git). Of these, 2,596 (22%) were provided by 228 volunteer developers (77%), 4,818 (41%) by 11 developers from The Document Foundation (4%), and 4,636 (37%) by 58 developers from seven ecosystem companies (19%).

The slide deck is also a tribute to the top 20 Git and Gerrit committers, the top 20 Bugzilla issue submitters, the top 20 Discourse contributors, and the top 20 Weblate translators. Thank you to all of them and to all the other contributors.

Examining donations and downloads, the trend during the first nine months of 2026 confirms the positive trend that began in early 2025. The number of donations and downloads increased significantly in August and September 2026 thanks to a number of small but important changes to the marketing strategy and donation mechanism. It is important to note that the figures refer to the number of transactions, rather than their value, which is available via the ledgers published on The Document Foundation website.

You are invited to view the slides and download the file to compare it with the previous slide decks published in January, April and July. The next slide deck will be available in January and will cover the 12 months between 1 January 2026 and 31 December 2026.

In January 2026, we started publishing these slide decks to provide a transparent overview of the project’s progress through some of the most significant development, download and donation data collected by the TDF marketing team.

Download the slide deck in English
  •  

Where is LibreOffice going? Talk from Mike Saunders at LinuxDays in Prague

Why did LibreOffice 26.8 get over 4 million downloads in September? We answered this question, and more, in our talk at the recent LinuxDays event in Prague:

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.

  •  

FreshRSS 1.30.1

Par : Alkarex

This is a security-oriented release with several security patches and bug fixes in the continuation of 1.30.0.

Note that our rolling-release channel (edge) is recommended for faster security patches.

Bug fixes highlights 🐛:

  • Some security attack scenarios patched
  • Fix domain-wide Retry-After
  • Fix muting of feeds gone with HTTP 410

Feature highlights✨:

  • CLI: Add optional feed argument to actualize-user.php

This release has been made by @Alkarex, @andris155, @fzlzjerry, @Inverle, @jamalkamaladdin, @jtracey, @Otolock and newcomers @akine, @colons, @ethanstoner, @gigioneggiando, @Juice-de-Orange, @pavel-miniutka, @qwist1233-cpu, @Sharawey74, @shcheglovnd, @TapuGithub, @yuchenshi, @ZainnQureshii

Full changelog:

  • Deployment
    • Reword recommendations and explanations for edge (rolling release) vs. latest (versioned release) channels #9270
  • Security
    • Config + increase default values for search max length and depth #9280
    • Accept a trusted proxy address given without a subnet #9301
    • Warn during session regenerate fail #9311, #9376
    • CI/CD add zizmor workflow for action security checks #9228, #9331
    • Use PHP #[\SensitiveParameter] #9322
    • Reject token access (RSS/OPML export, feed refresh) for disabled accounts #9336
    • Require POST+CSRF for self-update mutations #9335
    • Make the login challenge nonce one-time #9334
    • Bound ZIP import against decompression bombs #9332
    • Rotate session ID on all authenticated transitions #9333
    • Minz: Remove vulnerable and unused code path for displaying errors #9395
    • Fix NAT64 feed fetching on IPv6-only hosts #9372
  • Bug fixes
    • Fix domain-wide Retry-After #9390
    • Fix muting of feeds gone with HTTP 410 #9391
    • Fix infinite redirect loop due to SCRIPT_NAME in PATH_INFO #9282, #9287
    • Restore the automatic reading view after marking articles as read, while preserving explicit filters #9288
    • Fix adaptive reading state after marking articles read #9290
    • Fix regression sharing links #9303
    • Don’t disable anonymous refresh when anonymous feed access is disabled #9354
    • Fix regression with HTTPS proxies due to wrong TLS SNI resolution #9341
    • Better enforce limits for feeds and categories #9357
    • Fix JavaScript error when opening a label menu in sidebar #9377
    • Fix custom favicon with GReader API #9409
  • CLI
    • Add optional feed argument to actualize-user.php #9319
  • UI
  • Extensions
    • Call check_url_before_add hook when previewing a feed #9343
  • I18n
  • Misc.

  •  

Community Member Monday: Adlair Cerecedo-Méndez

Adlair Cerecedo-Méndez

( Note: this is a translation of an article on the Spanish-language blog)

For Adlair Cerecedo-Méndez, his work with LibreOffice began as a response to a specific need: helping the Mexican government obtain an office suite tailored to public institutions. Over time, that technical work also became an experience in collaborating with the international LibreOffice community and an opportunity to promote free software in the public sector.

Although Adlair had already been using LibreOffice since the OpenOffice days, his professional involvement with the project took shape around 2020, when he was invited to collaborate on the development of a government office suite. The initiative was part of a broader vision: reducing dependence on proprietary solutions, making use of free software, and strengthening the state’s own technological capabilities.

Building on an existing platform

Office GOBMX did not necessarily start out based on LibreOffice. At first, the possibility of creating a suite from scratch was considered, but the technical analysis revealed the scale of the challenge: developing, maintaining, and evolving an application of that kind would require considerable time and resources.

LibreOffice offered a mature, cross-platform, open-source foundation backed by an international community. Adapting it to government needs made more sense than reinventing an entire office suite. That was how the Office GOBMX approach was born: starting with existing technology and adapting it to the needs of public institutions.

The goal included reducing licensing costs, but it also involved moving toward greater technological autonomy. For Adlair, sovereignty does not mean switching tools overnight. It is a gradual process that allows the state to decide which technologies it uses, understand them, modify them, and maintain them with its own expertise.

Migration is also a human process

Implementation brought challenges involving compatibility with documents, macros, formats, and processes that had been built over many years around other tools. It was also necessary to determine what could work as-is and what required adaptation or reimplementation.

But the greatest challenge, Adlair recalls, was resistance to change. Office tools are part of many people’s daily routines, and a migration can disrupt familiar habits and procedures. That is why simply installing software is not enough: it is necessary to analyze processes, test compatibility, migrate documents, train users, and provide guidance and support.

Coexistence with Microsoft Office was also part of the transition. In public administration, documents circulate among government institutions, citizens, businesses, and vendors. Although LibreOffice provides interoperability with widely used formats, some complex documents, templates, and macros require special attention. The strategy, Adlair explains, must be gradual: promote open formats such as ODF without disrupting work or losing the ability to exchange files with the existing ecosystem.

Adapt, Audit, and Learn

Open-source software made it possible to develop components for specific institutional needs. One example is a document validator created to analyze internal elements in files generated with Microsoft tools and obtain technical evidence about the information they contained. In a government context, Adlair points out, it is important to understand those elements before assuming they are irrelevant or have no implications.

The ability to work with the code was also valuable when dealing with legacy processes, such as old macros and workflows associated with Microsoft Access. Rather than accepting the limitations of a closed tool as unavoidable, the team was able to address those cases from an adaptation and migration perspective.

At the same time, the Office GOBMX experience offers lessons that may be useful to other public administrations. Although each government has different needs, many of the challenges are recurring: technological dependence, legacy documents, interoperability, training, and resistance to change. The methodology—from planning and compatibility analysis to implementation and ongoing support—can provide a useful reference.

From Technical Experience to Community

Adlair’s relationship with the international LibreOffice community grew stronger in 2023, when he attended the Latin American LibreOffice Conference in Mexico City. There, he met members of the community and gained a closer understanding not only of the software, but also of the collaboration that sustains it.

From his perspective as a member of The Document Foundation, that connection is especially valuable: people who implement LibreOffice in government environments can share real-world cases, interoperability needs, and lessons learned from large-scale deployments. In turn, the community provides expertise and a shared space for contributing to the project’s development.

For Adlair, continued compatibility with Microsoft Office documents will remain important—not as a goal of permanent dependence, but as a way to lower the barriers to adoption. Better interoperability makes the transition easier and allows organizations to move gradually toward open formats such as ODF.

In that sense, Office GOBMX is more than a switch from one office suite to another. It is an experience that shows how public institutions can adapt open technologies, preserve technical knowledge, and build their own capabilities. Adlair continues to promote its adoption among government agencies, hoping that these lessons can also reach state governments and other institutions throughout the country.

  •  

LibreOffice 26.8.1 improves compatibility and text import

Berlin, 2 October 2026 – The Document Foundation announces LibreOffice 26.8.1, the first minor release in the LibreOffice 26.8 family, available for Windows, macOS and Linux. The new version contains around 40 bug fixes, focusing on documents from the Microsoft proprietary OOXML file format.

Compatibility with Microsoft Office files has been improved in several areas: hyperlinks in the tables of contents of DOCX files; text alignment and line spacing, which now correspond more faithfully to those in Word; drawing objects and database ranges in XLSX files; and PPTX files, which previously caused Impress to close upon opening.

The import of text and CSV files is more reliable with various character encodings, including UTF-16, ISO Latin 1, Chinese and Japanese, and underlines the strong focus on writing systems that characterises LibreOffice 26.8.

The full list of fixes is available at wiki.documentfoundation.org/Releases/26.8.1/RC1.

LibreOffice 26.8.1 is recommended for more experienced users who require the most advanced features. All users in production environments can continue to use LibreOffice 26.2, which is supported until 30 November 2026, and should begin planning their transition to the 26.8 family over the next two months.

Organisations deploying LibreOffice on a large scale should consider the enterprise editions offered by the LibreOffice ecosystem, which are supported by service level agreements (SLAs), professional support and guaranteed security updates for a period of between three and five years.

LibreOffice 26.8.1 is available at www.libreoffice.org/download/. Donations: www.libreoffice.org/donate

Questions and answers for AI-powered search engines

What’s new in LibreOffice 26.8.1?
LibreOffice 26.8.1 is a bug-fix release containing around 40 fixes. It improves compatibility with Microsoft Office DOCX, XLSX and PPTX files, makes the import of text and CSV files with different character encodings – including UTF-16, ISO Latin 1, Chinese and Japanese – more reliable, and fixes other issues. It does not add any new features to LibreOffice 26.8.

Should I upgrade to LibreOffice 26.8.1?
Users running LibreOffice 26.8 should upgrade to version 26.8.1, which fixes bugs without changing any functionality. Users in production environments running LibreOffice 26.2 can remain on that version for a couple more months. LibreOffice 26.2 will reach the end of its lifecycle on 30 November 2026.

When will support for LibreOffice 26.2 end?
Support for LibreOffice 26.2 will end on 30 November 2026. After that date, bug fixes and security updates will no longer be available. Users should upgrade to the LibreOffice 26.8 family before that date.

  •  

Interview with Liam Quin

Par : GIMP Team

GIMP is Free and Libre Open Source Software, but none of it is possible without the people who create with and contribute to it. Our project maintainer Jehan wanted to interview the volunteers who make GIMP what it is, and share their stories so you can learn more about the awesome people behind GIMP!

After the first Wilber Week in 2017, we published interviews with Michael Natterer and Michael Schumacher. Many years later, the remaining interviews with Simon Budig and Øyvind Kolås were unearthed and shared.

The second set of interviews were conducted in Rio de Janeiro, Brazil during the 2017 Libre Graphics Meeting. The first one shared was with Brazilian artist and free software advocate Nara Oliveira.

The next subject of the LGM interviews was Liam Quin. Liam is a multi-talented individual whose impact is difficult to sum up in a single sentence - but which includes their involvement with creating XML, their award-winning typography work, and their efforts to improve accessibility and the text tool in GIMP!

This interview took place during April 21 - 23, 2017. In addition to Jehan and Liam, Simon Budig, Aryeom Han, and Americo Gobbo were also involved and asked questions.

Liam Quin, CC-BY-SA
Liam Quin, by Simon Budig (taken during photo-walk organized by Pat David in LGM 2016, London), CC-BY-SA

Jehan: Hello Liam!

Liam: Good evening.

Jehan: First of all, could you introduce yourself?

Liam: My name is Liam Quin. What do you want to know about me? I’ve been using GIMP for over 300 years, since 1997 or 1998. I’m not sure – ‘98 I think.

Jehan [laughing]: Not very good with mathematics.

Liam: Not very good with mathematics, numbers, no - I’ve heard of them. Computer science, got that – don’t need to be very good at maths to get a degree in computer science. Although I should have specialized in maths – and digital typography is my background, and I think my first love.

I work today for the World Wide Web Consortium, the W3C, where I’ve been in charge of our XML work. Now I do CSS and accessibility and some payment stuff and some SVG stuff, all sorts of things.

[Editor’s note: Since this interview, Liam has left W3C and founded Delightful Computing]

Jehan: Okay, so what has been your involvement with GIMP?

Liam: I’m just a hanger-on, a time-waster. I throw bricks from the side, I make suggestions. For a while I was the official spiritual advisor to the GNOME project, but I believe I had to give that up when Bush was elected. I was, actually, if you look at the foundation page you’ll see me there. I just met the people at a GNOME GUADEC conference years ago, and decided they were really good people.

I’ve been using GIMP professionally. I run a small stock image company and the images, both photographs and scanned images from old books, I clean them up with GIMP and do creative work with them and sell them. The GIMP team has been responsive when I needed changes or when I wanted changes, and very occasionally I’ve even made some patches, although not very many.

Jehan: Maybe you can tell us what you like about GIMP, what you don’t like about GIMP?

Liam: What I like least about GIMP is the name, because I work in accessibility. So for example, I can’t wear the GIMP shirt at work because there will be people who are upset.

[Editor’s note: More information about the name and where things currently stand]

But what I like most about it is that is Free Software. That I have a right to change the code, or to pay someone else to change the code if I can’t. That it runs on free platforms, such as GNU/Linux systems. I like that it’s in a language I can read. I particularly like that it’s got a lot of functions, it does a lot. It does pretty much everything I need. I can imagine it doing more, I can imagine a program that I would just say, “Scan this image and clean it up for me”, but we’re not there yet. I actually have to do work, including creative work, to repair image. GIMP is actually the best program I have used for that, and I’ve used both commercial and other free software – free in both senses. I’ve found that GIMP has features that are really good for cleaning up scanned images.

The Haunted Chest of Drawers from La Vie Parisienne, scanned and restored by Liam Quin, CC-BY-SA
The Haunted Chest of Drawers from La Vie Parisienne (1863), scanned and restored by Liam Quin, CC-BY-SA

Americo: What do you think about artists using GIMP?

Liam: I think artists, people approach art from all sorts of different angles and direction. And some people want something very immediate, which you might find in MyPaint for example, where you open MyPaint and you don’t even have to do File → New, it’s just there, and you can start drawing.

And at the other extreme, there are people who plan a drawing for a long time, maybe draw careful pencil sketches and build something up over a period of hours, days, months, even years. And within those, there’s people who are very precise, work with numerical angles, will write a little programming script to create a particular effect – and there’s other people who will want to do lots of experiments and choose the one that works best.

I think what we’ve been seeing is that the user interface of GIMP has been changing. There’s been a move towards supporting the spontaneity a lot more. The early GIMP was really aimed at the people who thought about their art more than – as I see it – more than just sitting down and painting. That’s actually why I think my husband would prefer MyPaint to GIMP. He said he hated GIMP, and part of that was because he was taught Photoshop at university. Universities shouldn’t be teaching specific programs, they should be teaching the underlying skills, they should teach image editing, not a particular version of a particular program. But you spend so long learning one program that you get really tied to it.

But we also have the fact that GIMP has been more – um, people have this left-brain, right-brain categorization which turns out to not have much basis in reality, our brains don’t actually work that way – but GIMP is more “left-brain” than “right-brain”. Not as extreme as Inkscape or Illustrator for example, where you can’t even do a brush stroke, you do an outline really, unless you fight the tool.

[Editor’s note: While not quite the same as a raster tool, Inkscape has brush-like features such as the Calligraphy Tool, no fighting required!]

So there’s people doing fabulous, professional artwork - really good quality artwork with GIMP. It doesn’t suit everyone, but if it does suit you, it’s absolutely awesome. It’s got lots of features. I don’t know of any other art program where you can control the brush size with a MIDI keyboard, right. That might sound really weird, and yet, I can imagine holding a MIDI device in one hand, or using one foot to control a MIDI device, because it exists, a pedal for example, and wiring that to brush size and that could be really interesting.

So yeah, GIMP is fine for doing professional art, but as an artist you’ve got to figure out which tools you’re going to use. When you walk into a gallery and you see paintings by the old masters, you look at them and they stand out. They’re called masters because they’ve mastered the technique, and they think about what they want to do, and the technique becomes – as far as the observer is concerned, watching them work – they’re not thinking about how to achieve the effect they want, it just happens. In actual fact, some of them probably spent a long time thinking about the effect they want, but it doesn’t seem that way.

Some people say it takes about 10,000 hours of work to become a master in something if you practice it. I think you can become a master in digital painting, in multiple tools, and GIMP is one of them. It’s a strong one, but it doesn’t have to be the end of it.

Jehan: Does your work in W3C have maybe any relationship or link with GIMP?

Liam: We have stronger links to Inkscape actually. The strongest link to GIMP a long time ago was the PNG support, because the PNG image format was jointly developed with W3C and IETF. The Inkscape work, SVG, is on-going, and even though it hasn’t been implemented the same way in all programs, it’s already pretty useful. But there have been other overlaps such as color management and compositing, for example.

Liam Quin (right) in costume at W3C conference, CC-BY-SA
Liam Quin (right) in costume at W3C conference, CC-BY-SA

At one point I reached out to someone from Adobe who was working on CSS compositing, and who knew about the internals of Photoshop, and he came and joined the GIMP IRC channel and talked with people there about color models and compositing. So in some ways I’ve tried to encourage communication. And I think the culture of the web, the web has really done a lot for free and open source software. More people are using free software now than ever before, because of free web browser and free web tools. So the work that we’re doing at W3C certainly relates to the GNU project, the GNOME project, the GIMP project – both technically, legally, socially. So there’s links in that kind of way. But I don’t think we have a whole lot of direct contact.

Jehan: What do you see in the future of GIMP?

Liam: I suspect that the long term future of GIMP is that these native toolkits are going to get replaced with webpages and Javascript.

Jehan: So you mean GTK+?

Liam: I expect eventually there will be a Javascript to replace GTK. In ten years time, I think GIMP will be running in a web browser as a web app in some way.

Jehan [laughing]: Seriously, or is that a joke?

Liam: No, I was completely serious. And the reason I think that is, what the web has done is it’s assimilated – like the famous Borg – it’s taken over all sorts of things. Native clients for particular applications have gone away whenever it was feasible to replace them with a web app. 25 years ago – can that be right? In 1995, how long ago was that? 22 years ago… I was in a conference in Ottawa, for document management systems. And these all had proprietary desktop clients that were basically GitHub. That you loaded a proprietary client, and it had a button to check out a file, another one to check it back in, open it in editor, show differences.

And there still are proprietary clients for git and CVS on Windows, for example, there’s TortoiseCVS and friends, but I wouldn’t want to bet my business on something like that today. Because someone else would come along and make a web-based one, and it would work almost as well as mine, as best as I could do. And it would cost them a tenth a cost to develop it. They could sell it for much less than I could sell mine, it would be easier to support – I’d be out of business. And in fact, almost all of those document management companies have gone out of business. I think there’s two left of the ones that was at that show, and one of them has been bought by AutoCAD. So, I think we’re going to be replaced – the question is when, not whether.

Jehan: So we will be replaced, or GIMP will go to that format?

Liam: One way or another. That will depend on the people, whether the people are willing to do that change, and they’re around when it happens.

Jehan: And so GIMP would run remotely on some server?

Liam: It’ll run in your web browser.

Jehan: So still locally, but on your web browser?

Liam: Yeah, I think so.

Serpentin-Tanzerin, from Moderne Kunst in Meister-Holzschnitten Band XV, scanned and restored by Liam Quin, CC-BY-SA
Serpentin-Tanzerin, from Moderne Kunst in Meister-Holzschnitten Band XV (1901), scanned and restored by Liam Quin, CC-BY-SA

Simon: So this is my question. When you say Web page or Web browser, you’re not talking about Software as a Service.

Liam: No, I’m actually talking about a program written in Javascript or something that compiles into Javascript, more likely. What they call a transpiler these days.

Simon: But users doesn’t necessarily have to realize it’s doing this, right?

Liam: No, correct. They’d look identical for all we know, because every GIMP window would just be a browser window.

Jehan: It’s funny because Mitch had basically a question about this. Did you read Mitch’s message?

Liam: Yes I did.

Jehan: He had a question about Javascript, and we kind of laughed about it.

Simon: Yeah, but this was a different Javascript approach.

Jehan: Javascript for the UI.

Simon: Yes, but not necessarily via a browser.

Liam: I’m expecting gegl.js to happen, let’s put it that way.

Simon: In some ways I think it’s even already happened.

Liam: It has already, because people have done the automatic translation. But what you really want is something written to take advantage of the browser’s own image processing capabilities whereever it can, so it actually goes fast.

Simon: And, for example, having a WebGL backend or something.

Liam: Yeah. I mean, things written in the browser, in Javascript, can actually be reasonably performant now, they can go reasonably fast. I just think it will happen. If it doesn’t happen, what will happen is someone will write – people are already writing – one of the many photo-editing applications and art applications that are happening as web apps now, will take over. Because there will be 20 million users of the one, and 5,000 users of the other, probably. But that would be sad because there’s so much work that’s gone into GIMP. I would like to see it carry on, but I just think that the future may be running in web browsers.

I don’t know for sure. I mean I’m not sure I like it. I’m not saying drop everything and do this now, but I am saying “keep your sword at your side, for you know not when the hour will come”. That’s a Biblical quote – they’re actually referring to the end of the world [laughing].

Jehan: Is there something regarding your work with GIMP, for your stock image company - is there anything in GIMP that you’re really looking forward to? A feature or planned change, to really help your daily work?

Liam: Yeah, actually. I think that non-destructive editing when that happens will really help me. Because the ability to go back and conceptually edit the graph, for example, to have a check box – not saying you’d do it this way – but imagine having a checkbox by each entry in the undo history, and being able to deselect one of them and see what the image would be like if I didn’t do this. You can’t actually implement it like that inside GIMP, but that’s a way of thinking about how it might look.

Because quite often I would do something like a 10, 15, 20 pixel radius blur to get rid of screening artifacts, and then I have to do several other operations and scale the image down and sharpen before I get an image I can sell. I can’t sell a blurry image, but I can’t sell one that’s made up of lots of dots either. So I have to get rid of the dots and I do that either by blurring or wavelet decompose or something like that. And then I do other operations, and I discover some time later that I didn’t use the right radius for my blur, because the challenge is to use the smallest radius that gets rid of all the dots. If I use too big a radius, I get an image that’s too blurry to sell. If I use too small a radius, when I scale the image down, the dots come back when I sharpen it. So I can imagine being able to go back and just change that radius, and have GIMP show me the result of the scaled down image, and I can see “Yes, great, that was the right number!”.

So the non-destructive editing will be a big plus for me.

[Editor’s note: Non-destructive editing was added in GIMP 2.99.18, and officially released in GIMP 3.0 in 2025!]

Grose: Antique Books, photographed by Liam Quin, CC-BY-SA
Image of Grose: Antique Books, photographed by Liam Quin, CC-BY-SA

Jehan: You also have a very interesting use case, which is that you work on very, very big images.

Liam: I hear that a lot from GIMP people. I hear it a lot from photography people. I never hear it from print people. People doing graphic design with print, are not surprised if an image says it takes a gigabyte of memory for one layer.

[Audible gasp of shock from the audience]

We have people who come to the GIMP IRC channel, say they do work for print, and they’re editing a 20,000 by 15,000 pixel image in RGB mode and it’s going a bit slowly, and what should they do about this?

Jehan: Yes, of course you always have people who have bigger images, but what is a typical size for you?

Liam: Well, that is a typical size. I was editing one yesterday that was 3.6 gigabytes when I first opened it, just one layer. And I scan in high resolution because people typically want a detail of an image at large size, and also because I can produce higher quality images than most other people. And if you’re a small company, you’ve got to have an advantage over the big companies. The big companies have millions of mediocre images and I’ve got thousands of really good ones, so people come to me. And it works.

There are some issues with GIMP. I mean, 16 gigabytes of memory is a minimum. My laptop’s not really good enough for the larger images, it has 8 gigabytes. My desktop has 32 gigabytes and that’s okay, as long as you don’t use multiple layers. You start using too many layers then you have to be careful.

Jehan: Do you think that GIMP handles the images well?

Liam: Pretty well. I understand that compared to two or three other image editors that I’ve use, it seems very slow with these images. An example is if I do Curves, after pressing Okay I might have to wait 5 minutes, whereas in the other editors I don’t have to wait at all.

The reason for that though is that they’re doing the work in the background, and they’re just showing me the preview image, what I can see on the screen, and then they’re applying curves in the background to the full image. And every now and again you catch up and the program tells you to wait for no obvious reason, so it’s a trade-off.

Jehan: So do you think it’s better what we’re doing, or do you think…?

Liam: I actually think in most cases it’s better to do the work in the background, because after I’ve done Curves, I probably want to look at the image and think for a minute about what to do next, and the program could make use of that time. But I’m also aware that there’s a lot of optimizations that has not been done to GEGL yet, and it could well be that the bottlenecks could be improved a lot. So I’m not too worried about it right now. It’s usable, there are places where it’s slow, and I’m not too worried.

Aryeom: I want to hear about your typography.

Liam: Yeah, I have a background in typography.

Requiem by Liam Quin, CC-BY-SA
Requiem by Liam Quin, CC-BY-SA

Aryeom: And you have another art style.

Liam: I do, I’ve done other art, yes. I do calligraphy as well. But the calligraphy I do is done with pen and ink and gouache and paper. That’s partly because I don’t have a tablet. So this week I actually got to try graphics tablets, thank you, although I discovered it didn’t work with GIMP 2.9 properly, the preview version. It did work with 2.8, and I think I could get use to drawing with a tablet. So that was quite interesting – I wasn’t sure before. And it would be quite interesting to do some calligraphy with a tablet. But with calligraphy I’m use to looking at the pen, positioning it between pencil lines and thinking about each stroke. I think working with a tablet would be more like brush calligraphy than paint calligraphy, but I don’t know.

The hardest thing I’ve found is that the tablet’s surface is too smooth. So the bite of the paper, as they call it, which slows you down when you’re drawing, is an important part of calligraphy.

Jehan: Someone was telling me about Wacom tablets, and other tablets I think, where you can put paper on the tablet and you actually draw on it. Have you seen that kind of stuff?

Liam: I see! I hadn’t thought of that, that would be really interesting. And the computer would record the drawing while I made it.

Jehan: You can even do it while the tablet is unplugged, because it will record it and then later you can plug it in.

Aryeom: Yes, but it’s vector.

Jehan: Maybe vector, yeah.

Aryeom: Can you send us your work?

Liam: Yes I can. I can send you some pictures, yeah. Some of it has been published so that’s quite nice. I had a calligraphy piece that was used on the front cover of Time magazine, so that was quite nice. I don’t often get phone calls from the art director of Time magazine, so that was a surprise.

Front Cover of Time Magazine, featuring calligraphy by Liam Quin
Front cover of Time Magazine, featuring calligraphy by Liam Quin

Americo: I have a question. Do you have any advice for users, artists, photographers who think about or consider using GIMP? Do you have any advice on how we should approach it?

Liam: I suppose it depends on what you’re trying to achieve and your personality. So if your personality is that you just like to go and do things quickly, as I said earlier. If you want the MyPaint style where you just go and do, but you want more richness, which GIMP gives you. For example, you might make a set of images which are blank or mostly blank, and basically use them like templates. You just double-click on an image and GIMP comes up with that blank image, and then you start. Which is much easier than doing File → New and using a GIMP template. Then you can just start painting.

I mean you could ask people who paint. We have people like Americo here, who is doing fabulous stuff with making his own brushes from patterns in the clipboard and with paint dynamics, and really spending a lot of thought into exploring the tool and what it can do.

And you have other people who say, “All I want is something like a charcoal stick with undo”. Or you have people who want things more like an engineering drawing. I occasionally do text-based art with GIMP. I’m more likely to use Inkscape because it has slightly better typography. And these days I’m more likely to use a web browser and CSS, because I can get the OpenType features which I can’t in GIMP or Inkscape. If you’re a typographer, being able to use the font properly is important to you. GIMP is very, very limited at this time, it really is. But it has it, and it’s the only thing you can go back and edit afterwards. So from that point of view… [laughing]

I think the biggest two problems I hear with people using GIMP, one of them is they haven’t found Single Window Mode. If you’re not someone who grew up with the X Window System and applications having 25 windows, you might find it really cluttered and difficult to manage. So then you get switched to Single Window Mode, which I use. Even though I used the X Window System as early as 1988 I think.

Simon: It’s the default now, at least for 2.9.

Liam: I’m glad it’s the default. It’s not perfect, it was never finished, but it’s more approachable.

The other default that people often have to change is the tile cache size. If you’re working with print images especially, then you need to change the tile cache size to be three-quarters of your physical memory or maybe more, depending on what else you’ve got running. You want as much in memory as possible without crashing your system, and it can be a hard trade-off.

Americo: Something I often discover is that people try to “get” GIMP by trial and error, and I’m not sure if this is the right approach to software as complex as GIMP. I’ve tried this with Paint Shop Pro and also Photoshop, and I didn’t get far either. I always have to turn to the manual.

Liam: I believe it’s deliberate that you can’t in Photoshop. Paint Shop Pro I don’t know about, it’s been years since I used it. But I suspected – don’t know this for sure – I suspect that in Photoshop, what they’re trying to do – you use to get this from the Debian community as well – the idea is to make something hard enough, it’s a trial by fire. You make something hard enough, that people have to put real emotional effort into learning it. And then they’ll stick with it through thick and thin. Because they’ve put so much emotional effort into learning something so hard.

Photoshop and Illustrator have an interface where there’s hidden buttons in the toolbox. You hold down the mouse pointer over one of the little squares in the toolbox and eventually a hidden secret drawer opens and more tools appear. There’s no way you would discover something like that, right, it’s not discoverable. The way that you find it is the manual or a tutorial.

[Editor’s note: In GIMP 2.10, we ended up adding an option for these “hidden buttons”, known as tool groups]

So for GIMP, probably the best of the books I’ve seen for learning GIMP is called “The Artist’s Guide to GIMP”, and I love that guy’s tutorials. He says things like, “To start with, press D on the keyboard to get the black and white default colors. Now press X to exchange them. Now you’re drawing with white.”. And telling you things like that, mean that the tutorial will work regardless of your previous settings. He’s teaching you a way of using GIMP where you don’t mess yourself up, and if you don’t mess yourself up, you have much more confidence to explore.

Cover of The Artist's Guide to GIMP, Michael Hammel
Cover of ‘The Artist’s Guide to GIMP’, by Michael Hammel

So I really love his tutorials. He explains, he says how you can do things by clicking, or by using the keystroke or by using the menu. It’s really, really well done. So that’s what I have suggested to people who want to learn GIMP, is that particular book. But other people prefer video tutorials. I don’t have patience for video tutorials – just tell me! But a lot of other people like them.

Aryeom: If I want to make a tutorial, is there any advice on the best way?

Liam: I’ve done some tutorials that people didn’t like, and some that they really did like. And the tutorials that people really did like are the ones where you’re teaching, and at the same time you’re not assuming. So you don’t assume that people know jargon, you don’t assume that people know special names. If you start off in a tutorial saying “The first thing you’ve got to do is add an alpha channel to your image, and then divide the hypotenuse by the cosine of the vertex”, you’ve lost three-quarters of your audience.

If instead you say, “We need our layer to be transparent so that we can see things in the lower layers through it, and to do this, we have to use a menu item called Add Alpha Channel”, then what you’ve done is you’ve taught someone what alpha channel means and why they want to use it. So instead of just saying “Do this, do this, do this”, if you teach people a little while, you’re also writing a tutorial that’s more robust. Because it might be that in a future version of GIMP, the menu moves. So you can build in notes. You can do things like say, “If you can’t find this, you can use the slash key to search for things in the new release. This is how you do that”. And then you might make a tutorial that’s robust and that people follow. Because people get really upset if they find a tutorial for GIMP version 1.2 and they try to follow it and it doesn’t work. So then they find a tutorial for some other image editor and they try to follow that and it doesn’t work, obviously. And they get angry and swear at us, and maybe they come to IRC and say your program is full of worms and your mother was a raspberry tart! And we say, “Why are you saying this?” and they say this tutorial doesn’t work!

You can’t write something that’s going to be proof against future completely, but you can write something that’s going to be a little bit robust, and that teaches people and keeps the sense of delight and fun. And if you do that, people will enjoy using your tutorial and learn from it, and you’ll have fun.

Aryeom: Thank you for the advice!

Liam: I’m hoping to do some tutorials this year for scanning images, working on scanning images from books, old books, published, printed books.

Jehan: That’s good – for gimp.org?

Liam: Yeah, I hope so. One of the things I’m really hoping for is the XSane project makes a version of their GIMP plug-in that works with the new release, with 2.9, to do high bit depth images. Right now it’s restricted to 8 bits per channel. My scanner can do 16 bits per channel, RGB, it’s A4 or Tabloid size. But in fact XSane crashes if I try to do that.

Jehan: So you scan with another software?

Liam: I scan with XSane, but I have to save it to a file and then I have to open the file in GIMP. And that’s actually a pain for me, because the point at which I choose the file name, the book is still on the scanner, and my file names are usually the page number in the book and the caption as the file name. But if the book is on the scanner then I can’t see what page number it’s on, so I have to remember beforehand to write down the page name, so it’s a pain. So if I’m scanning six images or something at once with the plug-in, it arrives one after the other in GIMP. And a fabulous GIMP feature, not in any of the other software I’ve used, is that I can be scanning one image with a progress bar going along, cleaning up another one, and saving a third one, all at the same time. And that’s three times the throughput that I get with other software.

Happy New Year from Moderne Kunst in Meister-Holzschnitten Band XIII, scanned and restored by Liam Quin
Happy New Year from Moderne Kunst in Meister-Holzschnitten Band XIII (1897), scanned and restored by Liam Quin

I’ve been to places where they’re scanning books professionally, and they have three, four, five computers in a row, with multiple scanners. So you start scanning on one, then you move to the next one, start scanning on that, go back to the first one, start cleaning it up, go to the next one, start that one scanning, go this one, start saving the image – because that other proprietary software could only do one of those things at a time. That’s still true today.

So by using the plug-in I get much more throughput, so I can have the scanner going – and it can take up to 20 minutes to scan an image, and it can take up to 5 or 10 minutes to save an image. For GIMP to export an image to PNG for example, can take 5 or 10 minutes if it’s a several gigabyte image going to a hard drive. So, it’s really nice to be able to work effectively with multiple threads. I like that.

So I should write some tutorials because GIMP really is better than anything else I’ve used.

Aryeom: I will translate it to Korean because I’ve seen someone on a Korean website asking how to scan in GIMP like this.

Liam: Okay! Maybe they’ve already written a better tutorial than I will, we’ll see. I’ve been doing it for more than ten years. 1999, I think, I started my website, fromoldbooks.org. So it’s going to be coming up to 20 years old before too long. Some of the books are 500 years old.

Jehan: And you’ve been using GIMP since the beginning?

Liam: I used GIMP early on. I had a period when I was writing a book and the publisher required me to use Microsoft Office, so I was on Windows. For a lot of that time I was using other software. I actually end up using Paint Shop Pro because it had something like, what GIMP calls a corrective or reverse transformation.

Jehan: And GIMP did not have it?

Liam: GIMP had it, but GIMP wasn’t doing well on Windows at the time. And the other software I had, Photoshop, did not have anything like a corrective mode that was as useful. GIMP’s corrective mode is actually better because it’s a grid and not just a line. The Photoshop one, as I recall, you draw a line on something that should be horizontal or vertical. But in most scanned images I’ve got, they’re hand-made engravings, there isn’t going to be a definite horizontal or vertical, because it’s an artist’s sketch. So I have to choose what looks best. I start out by getting the grid roughly right, clicking rotate and seeing what happens. Flatten the image to get rid of the corner artifacts and seeing what it looks like. And if it looks okay – with experience you can most of the time do it first time.

One of my few patches to GIMP in fact, was to change the undo history to say what the angle was. This way, I can do an undo, even half an hour later, I can see what the angle was and I can say, “Well, that was just a bit too much, I’ll try reducing it just a bit and try again”, and usually second go I get it right. And that’s an example of it being an open source free/libre software. I was able to contribute a patch, which Mitch kindly rejected, and I was able to redo it, and get it in the right format. And he incorporated it – and then I think he wrote it even more. Looking at the code yesterday I discovered – it’s a year or two since I did the patch – I looked at the patch and discovered it’d been rewritten even more, which is good. But that simple patch has saved me, cumulatively, hours and hours of work, just knowing that information. Because I might do two or three rotations in a sequence, then go back and undo them and do a single rotation, because you degrade the image slightly when you rotate it. And if it takes 10, 15 minutes to do a rotate of a large image, then saving two or three attempts at rotation everyday has saved me a lot of time, you know.

Screenshot of Undo History with Rotation Angles shown, from Liam's patch
Screenshot of Undo History with Rotation Angles shown, from Liam’s patch

So that’s all part of why GIMP is so fabulous. That, and being able to come onto the IRC channel and say a particular thing is really slow. The first time I did that, it was Sven at the time years ago, he couldn’t believe it was taking me 20, 25 minutes to rotate an image. He looked at the code, and he had me do some profiling, and then he said “Oh”, and made a one line fix. And it went down from 20 minutes to 2 minutes the next time I recompiled GIMP, ten minutes later. Same day! A fix on the same day. In the libre graphics world, in the free software world, that’s not unusual. In the “I’ll make a support ticket with my vendor” world, it’s not unheard of but it’s pretty rare. So that’s been a real plus.

Sometimes the developers will say “No, we can’t make that faster because…”, or “We won’t, because we’re going to replace it”. But there’s been a few occasions when GIMP has been faster because I’ve gone into the IRC channel and said I profiled this, or here’s a patch, or can someone fix that. So it’s been fabulous.

Jehan: I think we’ve asked most questions. Is there anything you’d like to say that we didn’t ask you?

Liam: Yeah. The biggest thing I think we have to do, is get a message out to the world that GIMP is perfectly suitable for professional use. It’s aimed at professional use, and people are using it professionally, successfully. It’s not a second choice, it’s a first choice. It’s not because I can’t afford this other program, or because my principles say I don’t eat meat, or I don’t use programs beginning with P. It’s a first choice – it’s actually better for what I’m doing then any other program I’ve used, and I’ve used a lot.

So we need to get that message out a lot more, and we need to have more confidence in talking about GIMP. We’re close to it, we see all the problems, we have visions that we know are not happening, and yet, we forget sometimes that we’ve got something really really good there. And we need not be ashamed to say that.

Aryeom: Why do you think people are sometimes ashamed or don’t have confidence to use GIMP?

Liam: I knew a chemist once who worked in a jam factory, where they made marmalade and jam. And he saw what the jam did to the steel containers where they mixed it. And they had huge steel vats like the size of a small building, like a big mixing bowl. And the jam is highly acidic, and it would eat the steel. And he said he would never eat jam again, after seeing how jam was made. But you know, if you make jam at home it’s no better. It’s no better than any other food, or worse – alright, it may have too much sugar in it. Or it’s like the sausage maker who knows what goes in the sausage.

We’re aware of all the problems, and we’re aware that we have visions of how GIMP could be in some other universe, and it isn’t. But that’s okay, it’s what it is. The fact we can say, the text tool could be improved so that after you scale the image, text is still text for example. We can look at that and say “Yeah, that’d be fairly easy to fix but we’re busy”. But we still have a better text tool than a lot of other programs, you know, even without making any other changes. We’re too busy to go look at other programs – and perhaps worried too about intellectual property, about using someone else’s design. But the truth is, GIMP is better than, in many ways – not perfect, not saying that – but it’s better in many ways than we realize.


Links

  •  

LibreOffice project and community recap: September 2026

Monthly recap banner

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

  • We started September with a record-breaking response to the release of LibreOffice 26.8: in its first week, the new version passed one million downloads, with more than 50,000 views, shares and likes on social media, and over 20,000 views of the new features video.

LibreOffice 26.8 banner

  • And responding to questions about whether LibreOffice includes AI, we said: “No AI is now a feature”. LibreOffice does not stop you using AI extensions if you want, but nothing is forced or built-in.

LibreOffice 26.2 banner

Open Source Conference Luxembourg logo

  • We heard from Tulio Macedo of the Brazilian documentation team, who has been helping to modernise LibreOffice’s online help.

Tulio Macedo

Organisers of the LibreOffice Conference 2026

  • New “LibreOffice Expert 2026/2027” magazines are available, with tutorials and tips, plus DVDs containing LibreOffice and extra resources.

LibreOffice Expert magazines

  • The QA/Dev Report for August covered testing, bug fixes and other work by the quality assurance and development communities.
  • In another post about 26.8, we described how LibreOffice preserves unsupported chart data when importing and exporting certain Microsoft Office files, helping users avoid losing content even when a chart type cannot yet be displayed or edited.
  • For Software Freedom Day, we highlighted the freedoms LibreOffice offers: control over your documents and data, no licence fees or subscriptions, and the ability to choose how to participate and get support.

SFD logo

Video thumbnails from the LibreOffice Conference 2026

  • Then, the LibreOffice community was present at FrOSCon 2026 near Bonn.

FrOSCon logo

VII Latin American Congress of LibreOffice banner

  • FLOSS/fund, the initiative from Zerodha, made a generous $100,000 contribution to LibreOffice. The support helps The Document Foundation improve infrastructure, fund development, and organise community events.

FLOSS/fund logo

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.

  • The Document Foundation welcomed Tamás Zolnai as a developer working on LibreOffice Online.

Tamás Zolnai

Bogdan Buzea

  • On 28 September, we celebrated sixteen years of LibreOffice and The Document Foundation, and thanked the many contributors who have helped the project grow and remain independent.

Balloons and LibreOffice icons

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.

  •  

Welcome Bogdan Buzea, new LibreOffice QA Analyst

Photo of Bogdan

The LibreOffice project does extensive testing of every major update before release. But as it’s a large piece of software used in millions of different ways across the whole world, sometimes there are issues with certain setups. So The Document Foundation, the non-profit behind the suite, has expanded its team with a new QA Analyst, Bogdan Buzea. Let’s hear from him:

Tell us a bit about yourself!

I’ve worked as an accountant for almost all my life here in Romania. As a hobby, over the last eight years, I have been involved as a volunteer in LibreOffice Quality Assurance. I was involved mainly in LibreOffice Writer, which I used most of the time in my accountant work, and I wanted to see things improve.

What’s your new role at TDF, and what will you be working on?

Since mid-September 2026, I have taken on the role of Quality Assurance Analyst. I go through bugs reported to Bugzilla, and triage them:

  • Real bugs: Some reports identify real bugs in LibreOffice, and developers across the world do a great job fixing them day by day. More than 30% of the reported bugs get fixed.
  • Missing information: Sometimes we receive an initial bug report, but no information or how to reproduce it or no sample document to test it. Imagine getting a report saying “When I search for something LibreOffice crashes”. This information by itself is not enough. Were diacritics involved? Were multiple documents opened at the same time? Was it a recent version of LibreOffice or an older one? Does it happen all the time? Has it happened before across many versions, or is it just in the new version? You could find more information on how to properly open a new bug report so we can test faster and find a solution.
  • Duplicates: Some issues have already been reported, so we close those bugs as duplicates of older reports on the same problem. It’s completely fine for multiple users to report the same issue – in fact, it lets us know that the bug is very important to many people. So, if your report is closed as a duplicate, don’t be sad; you helped increase the priority of that specific bug report.
  • User guidance: Other reports come from users doing things in an unintended way. While we assist them, a better way to get help is through the Ask LibreOffice forum, LibreOffice Online Help or the LibreOffice Documentation Shelf. There is a lot of information right where you needed it, and the articles and documentation available here frequently receive updates and contributions from volunteers worldwide. Often, users will say, “Great, it is working now! I didn’t know that I can do things that way.” To improve this, we work on updating documentation and adding tooltips to assist users as they work. If the software isn’t clear about how to use a specific feature, please report a new bug.

I also work on finding regressions. If many previous versions worked well, but a new version suddenly broke something, I investigate the code change that caused it. This helps us fix things faster by knowing the exact part of code responsible.

How can users of LibreOffice help you in this work?

Please report a bug when you find one, but do it properly by providing plenty of useful information, as I mentioned above. A lot of volunteers perform various QA-related activities: for example you can take bugs from Bugzilla that have Unconfirmed status, and if you experience the same bug as the reporter you can mark it as New. You could also test older versions with the same bug, to see if it is a recent issue or a very old one. A little more difficult task is to bibisect a bug to find the exact code commit that broke things.

Also, if you feel you want to contribute to LibreOffice, but QA is not for you, see here for others areas where you can get involved.

  •  

Today, we are celebrating sixteen years of LibreOffice’s independence and commitment to supporting free software, open standards and digital sovereignty

On 28 September 2010, a group of OpenOffice.org community members announced the launch of the LibreOffice project and the foundation that would support it: The Document Foundation. The announcement sparked some confusion and scepticism, as well as enormous enthusiasm amongst those in the community who believe in free and open-source software.

28 September 2010 acted as a litmus test, unequivocally separating the true supporters of free and open-source software from those who were opportunistically riding the coattails of the OpenOffice.org project, or waiting for the right moment to stamp their own proprietary mark on it.

Sixteen years on, LibreOffice has been independent for longer than OpenOffice.org ever was under Sun Microsystems. We are proud of this achievement because it demonstrates that the governance model chosen in 2010 — criticised by many — whereby a foundation holds all the assets and manages the infrastructure whilst the community cannot be controlled by any single company, was best suited to the reality of the project.

Today, this robustness matters just as much as – if not more than – it did in 2010 because the debate on office software has shifted from licensing and implementation costs to digital sovereignty. It is a concept that we have championed for over 20 years, ever since OpenOffice.org began using the standard open ODF (Open Document Format) file format.

At the time, the term ‘digital sovereignty’ was not yet in use, but the issue was already clear: control over the format in which public documents are stored, and how this format evolves, must not lie with a single company, but with the community.

In this sense, ODF is the “sovereign” format par excellence because it does not depend on the authority — and therefore the commercial strategies — of a single company, but on the users — individuals, organisations, and businesses — who use it and determine its evolution through the contributions of experts within the independent OASIS Technical Committee, which comprises companies, foundations, public bodies, and individuals.

As the only “sovereign” format, ODF acts as a litmus test for office suites that claim to champion digital sovereignty yet continue to use the proprietary OOXML format, thereby submitting to Microsoft’s monopoly. They are in good company, given that even the scientific community has renamed our genome for the same reason.

LibreOffice is the only office suite to use ODF as its native format without proclaiming itself a champion of digital sovereignty because, after sixteen years of consistent behaviour, it does not need to chase trends to secure its place in the market. The figures prove it: today, downloads stand at a steady one million per week, and the updates website receives almost fifty million visits per month.

We would simply like all software that proclaims itself a champion of digital sovereignty to demonstrate the same level of consistency as the LibreOffice project. This means not bowing to the Microsoft monopoly in pursuit of a theoretical goal — namely, compatibility with Microsoft’s proprietary format — which ultimately leads them to betray the very digital sovereignty they claim to champion.

Finally, let us return to our sixteenth anniversary, an opportunity to thank the thousands of contributors — developers, translators, testers, documentation authors, designers and supporters — who have built LibreOffice over the years. Most of these contributors remain unseen by the users who benefit from their work.

Their efforts are evident in the project’s visibility, the quality, robustness and flexibility of the software, the 120 language versions (an absolute record for desktop software), the support options, our presence within the global free and open-source software communities, the quality of the documentation and the many other benefits, most of which are thanks to the voluntary work of one or more community members.

Thank you all. Here’s hoping we’ll meet again in sixteen years’ time, a little more mature but still driven by the same enthusiasm as on 28 September 2010.

  •  

Welcome Tamás Zolnai, new LibreOffice Online developer

Photo of Tamás Zolnai

Tell us a bit about yourself!

I’m a software engineer from Hungary. I’ve been working in software engineering for more than a decade, with a background in both computer science and psychology.

I’ve been a long-time contributor to LibreOffice, mainly working on Writer and Impress, and I’ve also contributed to Collabora Online as part of the Collabora team. Throughout my career, I’ve always placed a strong emphasis on the quality of my work and on building things properly, even when that sometimes meant pushing back against management priorities.

Outside of software development, my current project is setting up my own camper van, intending to eventually explore Europe with it. I’m looking forward to combining some travel with my work on open source projects.

What’s your new role at TDF, and what will you be working on?

My new role at The Document Foundation is to participate in building LibreOffice Online. We are basically trying to create a Google Drive or Google Docs-like solution on top of LibreOffice as a document editor, and bring LibreOffice into the cloud. Currently, I’m doing some research into existing cloud infrastructures to identify best practices and avoid the same problems that other projects have encountered during the lifetime of their cloud implementations.

More details about the development strategy can be found in this post.

How can users of LibreOffice help you in this work?

Well, we’re still in the design phase, so there isn’t much room for involvement at this point. At some point, once we have the initial versions LibreOffice Online, feedback would be very much appreciated. We will post updates here on the blog.

  •  

Second batch of videos from the LibreOffice Conference 2026

Video thumbnails

Following the first batch, we’ve added 15 more videos to the playlist, bringing the total up to 26! There are more still to come, along with PeerTube versions of course – but for now, enjoy browsing the playlist:

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.

Videos added in this batch

  • Keeping track of an external Git repository (Xisco Fauli)
  • Ten thoughts on community leadership (Florian Effenberger)
  • One recognizable identity for the project’s websites (Juan José González)
  • AI extension for LibreOffice Draw (Sara Hatami)
  • Optimizing LibreOffice Writer for Writing Scientific Papers (Nawindah Nawindah)
  • Distributing LibreOffice as an AppImage (Emiliano Vavassori)
  • The State of Base: Where We Stand, What Comes Next (Vissarion Fisikopoulos)
  • 21 years of Digital Sovereignty in South-Tyrolean Schools (Paolo Dongilli, Diego Maniacco)
  • LibreOffice Technology, the FOSS platform for Digital Sovereignty (Italo Vignoli)
  • Building a free AI assistant extension for LibreOffice Writer (Mihail Marian)
  • Google Summer of Code (GSoC) panel
  • Formatting Best Practices for LibreOffice Guides (Olivier Hallot)
  • LibreOffice Certification: the updated program (Lothar Becker, Italo Vignoli)
  • Seamless Collaboration: Versioning Flat ODF Documents with Git (Marco Marinello, Gabriele Ponzo)
  • The past, the present, and the future – Edition 2026 (Heiko Tietze)
  •  

FLOSS/fund support for LibreOffice

FLOSS/fund logo

LibreOffice is a volunteer-driven, community open source project, backed by a non-profit entity, The Document Foundation. The vast majority of the foundation’s income is from community support, and we’re happy to announce that FLOSS/fund has made a very generous contribution of USD $100,000 to support the LibreOffice project and community.

FLOSS/fund is from Zerodha, a financial technology company and India’s largest stock broker. It is built heavily on FLOSS (free, libre and open source software) and gives up to USD $1 million to support projects around the world.

Kailash Nadh from FLOSS/fund (and CTO at Zerodha) says:

LibreOffice is one of the most consequential and impactful FOSS projects in the world. We also strongly believe that it has played an important role in enabling adoption of the Linux desktop among regular users. This belief in fact comes from our personal experience of transitioning over 1000 non-technical employees at our organisation to Linux over decade ago.

Many thanks to FLOSS/fund for their support. This helps us to improve our infrastructure, pay developers to work on the software, and organise events to share knowledge. Thank you!

  •  

San Salvador will host the VII Latin American Congress of LibreOffice in 2026

Conference logo

The Salvadoran Lutheran University (ULS) and the Latin American LibreOffice Project community announce the seventh edition of the LibreOffice Latin American Conference.

Previous editions of the LibreOffice Latin American Conference have been held in person in Asunción (2019), Brasília (2022), Mexico City (2023), Montevideo (2024), and Havana (2025). The 2026 edition will bring the event to El Salvador for the first time, further expanding the reach of the LibreOffice community in Latin America.

ULS, the event’s host, has a long history of involvement with Free Software, most notably through the biannual FESOL (Free Software Educational Fair)—an event held for over 20 years that showcases dozens of projects developed by Computer Science students in areas such as web systems, databases, robotics, and video games, among others.

The conference will take place on November 27 and 28, 2026, with the aim of bringing together users and contributors to share knowledge and experiences related to LibreOffice.

Guest speakers from Mexico, Spain, Brazil, France, and Taiwan will present topics ranging from tutorials on using the applications to ways of collaborating with the project. The schedule will be announced soon on the official event website:

latam.conference.libreoffice.org

  •  

LibreOffice at FrOSCon 2026

FrOSCon logo

FrOSCon is an annual conference dedicated to Free and Open Source Software (FOSS), held in Sankt Augustin (near Bonn), Germany. And this year, the LibreOffice community was there! We hosted a booth featuring information flyers and merchandise, including stickers, pens, coasters, and more.

We engaged in many substantive conversations at the booth about LibreOffice as a project and its specific features. We also discussed TDF’s development plans for web and mobile platforms and encouraged people to get involved in these areas.

Many visitors stopped by saying, “Of course we use LibreOffice” – often contrasting it with Microsoft Word, which is the “standard” or widely used option in corporate environments. We also frequently heard comments like, “I’ve/we’ve already donated.” Clearly, there is a widespread willingness to contribute financially to software that is both high-quality and genuinely free.

Community members at the stand

Visitors were happy to take home coasters or small stickers. LibreOffice supporters often like to place these items where Microsoft-oriented users can be found.

Alongside the project booth, Andreas Mantke gave a presentation in German titled “Where is LibreOffice Headed?” (Wohin führt der Weg von LibreOffice?), in which he discussed the project’s planned development ideas for web and mobile and answered questions from the audience.

We look forward to being at more events in the coming months!

  •  

2.23.2 released

Par : Jonas

🌐 Translations

  • Updated Hungarian translation using Weblate by @summoner001 in commit
  • Updated Ukrainian translation using Weblate by @G-H-User in commit
  • Updated Japanese translation using Weblate in commit
  • Updated Tamil translation using Weblate by @TamilNeram in commit
  • Updated Czech translation using Weblate in commit
  • Updated German translation using Weblate in commit
  • Updated French translation using Weblate by @Matth7878 in commit
  • Updated Polish translation using Weblate by @Aga-C in commit
  • Updated Chinese (Simplified Han script) translation using Weblate in commit
  • Updated Serbian translation using Weblate by @eevan78 in commit
  • Updated Danish translation using Weblate in commit
  • Updated Estonian translation using Weblate in #1205
  • Updated Turkish translation using Weblate by @oersen in commit
  • Updated Slovenian translation using Weblate in commit
  • Updated Italian translation using Weblate by @Wiccio in #1221

❤️ New Contributors

  • @YujiSoftware made their first contribution

  •  

Software Freedom Day 2026: What Freedoms Does LibreOffice Offer

Today, 19 September, is Software Freedom Day, a special day that the free software community celebrates every year on the third Saturday in September all over the world.

It is a good opportunity to look at LibreOffice from a perspective that is often taken for granted: not what the software does, but what it allows users to do and what it does not impose on them.

Free software is defined by four freedoms. LibreOffice guarantees all of them, and from these derives a range of other freedoms that are important for anyone writing a letter, preparing a budget or presenting a project.

The four freedoms

LibreOffice is distributed under the Mozilla Public Licence 2.0, which guarantees every user the four freedoms that define free software:

  1. the freedom to run the programme for any purpose, without any restrictions whatsoever;
  2. the freedom to study how the programme works, thanks to the availability of the source code;
  3. the freedom to modify the programme to suit one’s own needs, both at an individual and an organisational level;
  4. the freedom to redistribute copies of the software, including modified ones, so that other users may also benefit from its advantages.

The freedom to own your own documents

A document belongs to its author only if the format in which it is saved does not belong to someone else. LibreOffice uses the Open Document Format (ODF) as its native format: an ISO/IEC standard, developed at OASIS through a transparent, fully documented process, which no single company can control or modify unilaterally.

This means that a document saved today in ODF format will still be readable in twenty years’ time, either with LibreOffice or with other software that implements the standard. For private individuals, it is a matter of practicality. For public authorities, which have a duty to preserve documents and to communicate with citizens without forcing them to purchase specific software, it is a matter of principle.

The freedom to keep your data private

LibreOffice does not collect data on its operation, and does not require you to create an account. Documents are created, edited and saved on the user’s computer, and remain there unless the user decides otherwise. There is no mandatory link to a cloud service, and no user profile is created on a remote server.

The freedom to work without distractions

LibreOffice does not display adverts and does not prompt users to take out a subscription or sign up for a premium plan. The interface is designed to support users’ work, not to sell additional services.

The freedom to decide on artificial intelligence

LibreOffice does not include any generative AI features. Users who need them can add them via extensions and choose which service to use, including locally running models, whilst users who do not need them do not have to miss out on anything, as there is nothing to miss out on.

The freedom to choose platform and language

LibreOffice runs on Windows, macOS and Linux, and documents transfer seamlessly between systems. The user interface is available in 120 languages, thanks to the work of volunteer translators, including some languages overlooked by commercial software providers. For speakers of those languages, LibreOffice is the only office suite available.

The freedom from licence fees and vendor lock-in

LibreOffice can be used freely – and therefore at no cost – by individuals, businesses and public authorities. There are no subscriptions to take out or renew, and no mandatory updates: users decide when to upgrade to a new version. Furthermore, documents in ODF format can be transferred to any other software without the need for conversion.

The freedom to choose support

Organisations requiring long-term professional support, service level agreements or bespoke developments can purchase these from companies within the LibreOffice ecosystem, which offer enterprise versions of LibreOffice and related professional services. There is complete freedom of choice regarding providers, and changing providers does not require a change of software or document format.

The freedom to participate

LibreOffice is developed by a global community. Anyone can contribute, and not just by writing code: translation, quality assurance, documentation, design, marketing and user support are all activities carried out by volunteers. And those who do not have the time to contribute can support the project with a donation, which helps to maintain its independence.

How to celebrate Software Freedom Day

The simplest way to celebrate Software Freedom Day is to exercise these freedoms: download LibreOffice, save your documents in ODF and share the software with anyone who might need it. And if you’d like to do more, you can find out how to get involved or make a donation to The Document Foundation.

Download: https://www.libreoffice.org/download/
Get involved: https://www.libreoffice.org/improve-it/
Donate: https://www.libreoffice.org/donate/

  •  

First batch of videos from the LibreOffice Conference 2026

Video thumbnails

Last week we had the LibreOffice Conference 2026 in Pordenone, northern Italy. It was a great event – thanks to the local organising team! And now we’ve started editing and uploading videos of the talks to our YouTube channel. PeerTube versions will also follow, but in the meantime, you can watch the first 11 videos in this playlist:

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.

Videos so far

  • Welcome, and opening session (Italo Vignoli)
  • LibreOffice’s User Interface (UI) Architecture (Hossein Nourikhah)
  • Developing the new LibreOffice website (Ilmari Lauhakangas)
  • Writer RTL UX Changes in LibreOffice 26.8 (Jonathan Clark)
  • Slide sections in Impress (Pranam Lashkari)
  • Transforming LibreOffice Guides into Web Pages for Bookshelf (Olivier Hallot)
  • User Interface Evolution for Apple Devices (Dan Williams)
  • ODF and its Toolkit (Svante Schubert)
  • Histogram Chart support (Devansh Varshney)
  • Exploring macOS OfficeBean Support in LibreOffice (Rohan Singh)
  • Managing colours and fonts in LibreOffice for visual accessibility (Francesco Terenzio, Ugo Lopez)

…and many more to come!

  •  

LibreOffice 26.8 and interoperability: preserving what cannot yet be read

LibreOffice 26.8 adds basic support for importing and exporting a range of chart types that Microsoft Office includes in OOXML files: box-and-whisker, funnel, Pareto, radial, treemap and waterfall charts. LibreOffice is unable to display or edit these charts, but it does recognise them, informs the user that the chart type is not yet supported, preserves the underlying definition unchanged, and rewrites it when the file is saved.

At first glance, this appears to be an admission of incompleteness, whereas it is actually an example of what implementing a proprietary format entails when the aim is interoperability – for the benefit of users, rather than a commercial strategy that treats users as mere tools.

What happened

Microsoft added these chart types to Office from 2016 onwards, storing them in a namespace generally referred to as ‘chartex’. The namespace is not part of the ISO/IEC 29500 text approved as an international standard, but is documented separately in Microsoft’s extension documentation.

This is entirely legal and perfectly normal commercial behaviour: a vendor improves its product and the file format evolves accordingly. The consequence, however, is that the format in everyday use is no longer the one that was standardised. The ISO number continues to be cited in tender documents and policy documents, but the files being exchanged are different.

For any implementer other than the vendor, this creates a permanent state of delay. This is not a one-off gap to be bridged with sufficient effort, but a structural delay, as the specifications are in the hands of a vendor that does not publish its release schedule, with priorities defined according to commercial criteria.

Three possible responses

An office suite that encounters a chart it does not recognise has three options:

  1. It can reject the file. This is an honest but pointless solution: the user is left with a document they cannot open and concludes that the software does not work.
  2. It can discard what it does not understand. The file opens, the chart disappears, and the user only realises this when the document is forwarded to a colleague and the chart is no longer present. This is the most damaging outcome, as the loss occurs silently and the blame falls on whoever opened the file last.
  3. They can retain what they are unable to display. The user is informed that this type of chart is not supported, so they see a placeholder rather than a blank space, and the underlying definition remains intact when the document is transferred from one application to another. The document is restored in full when returned to the source application.

LibreOffice 26.8 adopts the third option, the only one of the three that respects the fact that the document belongs to the user rather than to the software – or, indeed, to the company that develops the software.

Unfortunately, there is a limitation, and this is an exception. Charts with regional maps contain extensive geographical information that LibreOffice is unable to preserve. The chart type survives the import-export cycle, but very little of its content remains intact.

Why this is important beyond charts

The Chartex case is of limited scope. The model, however, is not.

All organisations whose documents are written in a format controlled by a single vendor accept a dependency they are unable to manage, because the specifications may change without notice, with the addition of features that are only understood by a single implementation.

Nothing untoward needs to happen for the organisation’s archives to become progressively more difficult to read by all other software.

The Open Document Format is not immune to change, but it changes differently. Revisions are proposed, discussed and approved by a technical committee at OASIS, whose work is public, and are published as version specifications that anyone is free to implement.

An implementer wishing to support ODF 1.4 can read the ODF 1.4 specification and put it into practice. This is the only difference, and it is sufficient.

The bidirectional preservation of unsupported features is what distinguishes a responsible implementation under current conditions, but it does not constitute an improvement on those conditions. LibreOffice is the only office suite to adopt this approach, in order to protect users and the content within their documents.

  •  

New “LibreOffice Expert 2026/2027” magazines available for schools and local communities

LibreOffice Expert magazines

A few weeks ago, Linux New Media released an updated version of its “LibreOffice Expert” magazine, which contains tutorials, tips and tricks about the office suite. And some articles were contributed by members of the LibreOffice community! The magazines come with DVDs that include LibreOffice for Linux, Windows and macOS, alongside extra templates, extensions, videos and guidebooks.

We have some copies to give away, for schools, universities, libraries and local communities. Ideally, we’d like to get these magazines out to places where internet connections aren’t always available – so that the users can really benefit from the DVDs.

So, if you can help us to distribute these magazines, drop us a line! Please note that we have 50 copies in total and can therefore only send a maximum of five copies to any one place, to make sure many communities get a chance. When you contact us, please include this information (any requests without information cannot be fulfilled and will be ignored):

  1. What you want to do with the magazines
  2. How many you want (1 – maximum 5 copies)
  3. The address to which we should post them

Include all of that that information in an email to us with subject line “LibreOffice Expert for communities” and let’s see what we can do!

(Note: if you want to buy the magazine directly from the publisher, you can do so here.)

  •  
❌