Welcome to The Document Foundation Planet

This is a feed aggregator that collects what LibreOffice and Document Foundation contributors are writing in their respective blogs.

To have your blog added to this aggregator, please mail the website@global.libreoffice.org mailinglist or file a ticket in Redmine.


Saturday
21 November, 2026


face

Let me publish here a text from Michael Weghorn's letter to our dev mailing list about current Qt6 plugin for Windows build status (because I like when more people can see such important information):

Earlier this year, initial support for the qt6 vcl plugin on Windows (and macOS) was implemented on master.

Below is a summary of the current status and potential next steps from my perspective.

I haven't used/tested it much myself beyond the point of "It starts and looks plausible at first" when contributing to it in the past and it is not my own main focus now. The below is meant as a basis for further discussion and coordinating efforts between those who are interested in getting involved to further improve it.

If you have any thoughts or are interested in getting involve, feedback is very welcome!
I think in particularly steps described in "Identify and address what else is missing" could be a good starting point for both, developers (already now, requires building from source), and non-developers (in 
particular once tests builds for Windows including the qt6 vcl plugin are provided).

LibreOffice: qt6 vcl plugin on Windows

Background/Motivation

So-called "vcl plugins" are used in LibreOffice to implement the user interface and platform-specific aspects. They can either make use of third-party GUI toolkits or implement the low-level logic themselves.

The Qt-based vcl plugins that use the Qt UI toolkit were originally only used on Linux and similar Unix-based systems. qt5/qt6 was later also selected as the basis for the newly introduced WebAssembly port.

Reusing/Suppporting the qt6 vcl plugin on more platforms could be a potential approach to

  • let an existing cross-platform UI toolkit take care of more platform-specific logic instead of "reinventing the wheel"
  • unify and share more code across different platforms, also to reduce the maintenance effort
  • reduce (but not eliminate) the need for Windows-specific code/knowledge
  • ensure reliability and continued development/progress of the user interface (and more) on Windows despite most developers (currently) not working on Windows or Windows-specific code
  • allow to make use of capabilities that Qt provides to allow theming/styling of the application
  • get support for the newer UIA (User Interface Automation) accessibility protocol on Windows via Qt's internal accessibility bridge
  • gain support for "native widgets" if combined with the "Qt welding" task (https://bugs.documentfoundation.org/show_bug.cgi?id=130857)

Since there is no real "standard native UI toolkit" on Windows (see e.g. also the discussion in 
https://bugs.documentfoundation.org/show_bug.cgi?id=164656), no clear alternative candidate seems to be available to implement support for "native widgets" on Windows.

Current status

The qt6 vcl plugin code and related code was refactored to also allow building the qt6 vcl plugin on Windows and macOS.

Commit enabling build support on Windows: 
https://git.libreoffice.org/core/commit/4d3a291b5d2d8a2dbdae5aca0d5fd506b5d5b0b9
Commit enabling build support on macOS: 
https://git.libreoffice.org/core/commit/ddfc4058cfff09454621fe68f8804bbf289558b5

This work was inspired by/based on an earlier WIP branch …


Thursday
19 November, 2026


face

Developing LibreOffice requires debugging. But, with the default settings, it takes a long time to load GDB and use it. Here I discuss GDB index cache to improve the debugging experience with a faster startup.

GDB Debugging

Whether you want to fix a bug or add a feature to LibreOffice, debugging is an essential part of the task. Running LibreOffice in debug mode, going step by step and checking the value of a variable and checking the stack trace and threads is among the thing that developers do in a debug session.

But, if you have ever tried to debug LibreOffice using GDB, you may have noticed the big delay before you can use LibreOffice in a debug session.

To start a debug session, you need to have a working build environment for LibreOffice. Then, invoke:

$ make debugrun

You will see a few things written on the screen, and then gdb prompt. Enter run to run LibreOffice, after setting the VCL plugin to gen, which starts faster:

(gdb) set env SAL_USE_VCLPLUGIN=gen
(gdb) run

It may even take something like 30 seconds or more before you see LibreOffice running. But, there are ways to improve the situation, and GDB index caching is one of them.

To benchmark the required time for startup and shutdown of Writer, you may set OOO_EXIT_POST_STARTUP environment variable to 1:

(gdb) set env SAL_USE_VCLPLUGIN=gen
(gdb) set OOO_EXIT_POST_STARTUP=1
(gdb) run --writer

In this way, LibreOffice exits immediately after startup. Further environment variables are listed in TDF Wiki:

GDB Index Caching

GDB needs to read symbol files to create its internal symbols, and provide symbols while you debug instead of simple memory addresses. That requires scanning of many files, and increases startup time. In order to improve that, GDB can automatically cache symbol indexes for a faster next startups.

Using this feature requires at least GDB 8.3, which is usually true in recent Linux distributions.

Suggested Configuration

This is a suggested configuration file for GDB, which you may store in ~/.config/gdb/gdbinit:

add-auto-load-safe-path ~/core/instdir
add-auto-load-safe-path ~/core/workdir
set print pretty on
set debuginfod enabled off
set index-cache enabled on

It enables index caching, alongside pretty printing, and some related scripts in instdir/ and workdir/, and it disables fetching debug symbols from internet through debuginfod.

Checking the GDB Index Cache Status

To check the status of caching, first start a debug session:

$ make debugrun

Then, invoke this command in the GDB prompt:

show index-cache directory

show index-cache stats

This will show you the cache directory, and the statistics, which will be useful only after a debug session, to asses the number of cache hits and misses.

gdb index cache statusgdb index cache status

You may check the size of the cache:

$ du -hs ~/.cache/gdb/

Please be aware that there is no limit for the size of GDB cache, therefore it may grow over time. You may remove the cache, and it will be re-created after first use, which is a cold …


Wednesday
18 November, 2026


face

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!


Tuesday
17 November, 2026


face

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.


Monday
16 November, 2026


face

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.


face

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!


Friday
13 November, 2026


face

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.


Thursday
12 November, 2026


face

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 …


Monday
09 November, 2026


face

General Activities LibreOffice 26.8.1 and LibreOffice 26.8.2 were announced on October 2 on October 29 respectively Olivier Hallot (TDF) added extended tips to crop image dialog, added initial wiki pages for new Calc functions, added help pages for dynamic arrays in Calc, Like Operator in BASIC, Shuffle command in Calc,


Friday
06 November, 2026


face

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 …


Thursday
05 November, 2026


face

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!


Wednesday
04 November, 2026


face

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.


Tuesday
03 November, 2026


face

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 …


Friday
30 October, 2026


face

Adriano Fernandes announced the 1.0.0 release of fb-cpp, a modern C++ wrapper for the Firebird database API.This release marks an important milestone: fb-cpp is now feature-complete in the scope of its public database client API. The project has grown from a collection of wrappers around the Firebird interfaces into a complete, consistent library for building Firebird applications in modern C++.


Tuesday
27 October, 2026


face

Two open source projects for running and managing Firebird have grown up side by side: fbadmin, a pgAdmin-style web administration tool for Firebird, and cloudnative-firebird, a Kubernetes operator for Firebird modelled on CloudNativePG. They also work together: fbadmin can list and manage the Firebird clusters the operator runs. fbadmin: a web admin tool for Firebird fbadmin gives Firebird a


face

Electric Firebird runs the Firebird database engine compiled to WebAssembly, in the browser and in Node, similar to what PGlite does for PostgreSQL. It ships on npm as firebird-wasm, and the repo and the package share version numbers. Six releases came out between October 24 and October 27, 2026. Here is what each one brought. npm install firebird-wasm@0.14.0 v0.14.0 – Zero-copy results and


Wednesday
21 October, 2026


face

Pull request #9111 "Build FirebirdSQL CMake+CLang" by Sergey Khalyutin was merged into the Firebird master branch on October 21, 2026. It makes it possible to build the whole Firebird project with CMake + Clang on Windows, Linux and macOS, for both amd64 and arm64. What changed One build system for all platforms – Firebird can now be built with CMake and Clang everywhere. The only exception is


Thursday
15 October, 2026


face

While LibreOffice is (mostly) in C++ and uses native GUI toolkit on different platforms, it is still possible to use web technologies with LibreOffice. Here I discuss how.

Webview

Webview is a small web browser widget that is inside an application. There are many ways to use web technologies with LibreOffice. But, using a webview widget like pywebview is probably the easiest way to link a webview with LibreOffice. The idea is to display a web page in a webview widget that Python provides, and link that to LibreOffice via the connection of Python to LibreOffice and the connection of JavaScript in webview to Python, and send UNO commands to interact with LibreOffice via network.

Minimal Example

This is a minimal example to show a minimal web page that contains a text box to write the UNO commands like .uno:Bold, and see it working in LibreOffice:

import uno
import webview


class UnoBridge:
    def __init__(self):
        self.ctx = self.desktop = None

    def connect(self):
        if self.ctx is not None:
            return
        component_ctx = uno.getComponentContext()
        resolver = component_ctx.ServiceManager.createInstanceWithContext("com.sun.star.bridge.UnoUrlResolver", component_ctx)
        self.ctx = resolver.resolve("uno:socket,host=127.0.0.1,port=2083;urp;StarOffice.ComponentContext")
        self.desktop = self.ctx.ServiceManager.createInstanceWithContext("com.sun.star.frame.Desktop", self.ctx)

    def dispatch(self, command):
        self.connect()
        frame = self.desktop.getCurrentFrame()
        dispatch_helper = self.ctx.ServiceManager.createInstanceWithContext("com.sun.star.frame.DispatchHelper", self.ctx)
        dispatch_helper.executeDispatch(frame, command.strip(), "", 0, ())


HTML = r'''<input id=c value=".uno:Bold"><button onclick="pywebview.api.dispatch(c.value)">OK</button>'''

webview.create_window("LibreOffice UNO", html=HTML, js_api=UnoBridge())
webview.start()

To use this example, first you should start LibreOffice and make it listen on the port that is written in the code, 2083:

$ libreoffice26.8 "--accept=socket,host=localhost,port=2083;urp;StarOffice.ServiceManager"

You may open Writer, and write a small text and select it. Then, you can run the Python code. You may use LibreOffice internal Python or external Python with uno package. But, you have to install pywebview package anyway: (the command might be different according to your operating system, etc.)

$ pip install pywebview

Then, by running the Python code you should be able to see a window similar to the below screenshot:

$ python3 webuno.py

You can edit the command and after clicking on “OK”, you should be able to see the result in LibreOffice.

WebUNOWebUNO: connecting webview to LibreOffice

How the Python Code Works?

The Python code essentially consist of two important functions: connect and dispatch. The connect function uses uno.getComponentContext() to get the component context, and then finds service manager to execute executeDispatch() with the give UNO dispatch command.

You may read more about service manager in LibreOffice DevGuide chapter 1. This is an illustration from the same chapter of DevGuide:

Service ManagerService Manager

Final Words

A comprehensive list of UNO dispatch commands are available in the Wiki link below:

Please note that some UNO commands work in every LibreOffice application, but …


Tuesday
06 October, 2026


face

General Activities LibreOffice 26.2.6 was announced on September 4 Olivier Hallot (TDF) improved help for many Calc functions, alignment and number formats in Calc and the Data Range button in Calc’s Navigator. He also added meta data for cross referencing translated online help pages to improve web search results Alain


Wednesday
16 September, 2026


face

General Activities LibreOffice 26.8.0 was announced on August 26 Olivier Hallot (TDF) added help pages for Calc’s ARRAYTOTEXT function, the easy conditional formatting feature, saving database queries, the VBA Like operator, added new gutter options to the help page for Page Style dialog, added a mention of autodetection of ISO


Wednesday
09 September, 2026


face

If you don't know what is dynamic arrays, then just read this article https://exceljet.net/articles/dynamic-array-formulas-in-excel.

Note, dynamic array's functions like UNIQUE, FILTER, SORT, etc. were already implemented early. But other new general dynamic array features were added to LibreOffice Calc only now into current master that will be 27.2 release in next year.

Let's say big thanks to Collabora's developers for it, because all work was made for Collabora Office and then Xisco Fauli copied all patches to LibreOffice project (The source code license allows it, because it's the same MPL 2.0 on both sides).

You can try the new features using master daily builds for your OS by the link.


Thursday
03 September, 2026


face

Earlier this year we ran a survey about LibreOffice Base. Similar to the questionnaires about LibreOffice Draw (see first and second blog post) and LibreOffice Calc, we asked about use cases, the most important features, the pain points – and what users expect in the future to support development and to gather ideas how the user interface and workflow can be improved. In total, 455 participants completed the questions. Thanks a lot to everyone who took the time!

Demographics

As usual, the survey is heavily biased. The attendees self-estimate their expertise above the average, run the application more frequently, and show a different distribution in operating system usage compared to regular users.

Applications

To start off, we asked what tools they use. We included Spreadsheet Tools to also cover users who do not actually use a database, but think of a spreadsheet as kind of data storage. Participants responding None, obviously not managing any database, got a different follow-up question.

What tools do you use to manage databases?

Features

To trigger the idea of the following open questions, we asked about the importance of different features. Unlike the large number of functions in other modules, Base offers queries, reports, forms, tables, etc. which are all essential for the work with databases. Therefore we collected some features that may or may not be relevant for a sub-group or have room for improvements.

How important are these features for you?

What is your use case for the database management system?

People understand the question differently, and reply very short or rather verbosely. The answers may point to a professional environment if “payroll information for up to 10000 people” is mentioned, over SME’s processing order management, production count, and shipment status, to obviously private usage. The following attempt to categorize the answers cannot do justice to the variety of all replies:

  • Catalogs/Inventory: In-house Bakery, Receipts, Music/Books, CD/DVD, Musical scores. Plant samples, Publications/Scientific research, Health data
  • Web/Software: Backend storage, Software development, Websites, Managing SQL
  • ERP/Finance: Order management/Production count/Shipment status, Invoicing, User data, Cost management, Expenses,
  • Storing addresses and mail merge processing

For example:

“I use it mostly as place to store sensitive customers data. But since I have small quantities of information, I switched to LibreOffice Calc, which files can be also locked with the password.”

“Smaller business applications in the freight forwarding and logistics sectors, such as fleet management, warehouse management, category management, and invoicing.”

“Managing geospatial information with PostgreSQL/PostGIS and creating reports with the information from the attribute table using LibreOffice Base/Writer.”

“Storing data when it gets too big/slow for a CSV file for personal or internal work (engineering) projects.”

In your opinion, which LibreOffice Base features (if any) need improvement the most, and why?

The majority asks for improvements to the user interface with less clutter and a more attractive design. The workflow and user experience should become either simplified or more powerful, depending on the expertise and the scenario …


Monday
31 August, 2026


face

The NotebookBar (NBB) or tabbed interface is an alternative user interface for LibreOffice. In the second part of this series, I explain the way the NotebookBar takes icons and text to create the final output that you see on the screen.

Creating NotebookBar is LibreOffice Code

Currently, the NotebookBar is not exactly like the other UI files that in LibreOffice with weld mechanism. In the first part of the series of blog posts on this topic, I discussed the custom widgets in notebookbars and how to edit them using Glade.

The custom widgets rely on C++ code, especially for sizing and other characteristics. For example, Priority Merged Horizontal Box (sfxlo-PriorityMergedHBox) is a “horizontal box hiding children depending on its priorities”. It needs C++ code to implement the priority display of the children. If you search for it in C++ files, you will reach builder.cxx:

$ git grep -l sfxlo-PriorityMergedHBox "*.cxx"
vcl/source/window/builder.cxx

The above file is a huge > 100 KB C++ source code  that handles NotebookBar custom widgets, but also handles every other VCL widget.

The other parts of the relevant code for the NotebookBar resides in below files. Search for both “Notebookbar” and “notebookbar” in C++ files:

$ git ls-files "*otebook*cxx"
sfx2/source/notebookbar/NotebookbarTabControl.cxx
sfx2/source/notebookbar/SfxNotebookBar.cxx
vcl/qt5/QtInstanceNotebook.cxx
vcl/qt6/QtInstanceNotebook.cxx
vcl/source/control/NotebookbarPopup.cxx
vcl/source/control/notebookbar.cxx
vcl/source/window/NotebookBarAddonsMerger.cxx

Icons in Notebookbar

If you open the NotebookBar UI for LibreOffice Writer or other components like Calc, etc., what you see lacks two important things: icons and text.

Notebookbar widgetsNotebookbar widgets

First, let’s look into icons. The icon files come from the set of icon themes that are available with LibreOffice. The icon theme of LibreOffice is configurable, therefore you do not see some specific LibreOffice icon in the design. That makes the work of UI designers harder, but lets LibreOffice choose among different icon themes.

You may find more information in the icon-themes/ module README.md file, which describes how to create new icon themes, and how to link the icons to specific icons via .xcu files. For example, in officecfg/registry/data/org/openoffice/Office/UI/CalcCommands.xcu you see:

<node oor:name=".uno:OpenFromCalc" oor:op="replace">
    <prop oor:name="Label" oor:type="xs:string">
        <value xml:lang="en-US">~Open...</value>
    </prop>
    <prop oor:name="Properties" oor:type="xs:int">
        <value>1</value>
    </prop>
</node>

This is defined for the UNO dispatch command, .uno:OpenFromCalc, which opens a file for Calc. The complete list of UNO dispatch commands is available here:

For each command, two icon sizes are created, one small and one big icon. lc_<command name>.png and sc_<command name>.png, if not in SVG format. At first, one should add the icons for a new command to the colibre theme, in order to be usable also with other themes.

Here, the filenames will be lc_openfromcalc.png and sc_openfromcalc.png, which are available …


Thursday
20 August, 2026


face

General Activities LibreOffice 26.2.5 was announced on July 23 Olivier Hallot (TDF) added help pages for many new Calc functions and for matrix input dialog in Math and improved help for regular expressions Alain Romedenne added help for the Python modules scriptforge, msgbox and officehelper Miklós Vajna (Collabora) fixed an


Saturday
15 August, 2026


face

FBSimCity, the explorable isometric city of Firebird internals, is at v0.9.0 &mdash; and this one adds the thing the project has been circling since it started. The city has always carried the same caveat: it is a model, it parses no SQL, and no Firebird code runs in your browser. The new machine room is the other thing.The machine roomThe machine room runs the actual Firebird engine: version


Friday
14 August, 2026


face

Electric Firebird (mariuz/electric-firebird on GitHub) compiles the Firebird database engine to WebAssembly, following the same approach PGlite took for PostgreSQL. The goal is to let Firebird run both server-side (Node.js) and fully client-side in the browser, with no server round-trip required for queries.Highlights:Two backends: a native Node.js implementation (via the Firebird Embedded Server


Sunday
09 August, 2026


face

Correction (added 9 August 2026): the section below headed &ldquo;A synchronous replica that dies hangs commits&rdquo; is wrong. Dmitry Sibiryakov pointed this out on firebird-general, and the source confirms it. In src/jrd/replication/Publisher.cpp, checkStatus() is called with canThrow = false on the commit path, so it cannot throw; disable_on_error (default true) instead clears the replicating


Tuesday
04 August, 2026


face

Firebird's client library, libfbclient / fbclient.dll, has always been distributed exclusively as a shared library. PR #9104 by Adriano dos Santos Fernandes, merged into the Firebird source tree on July 24, 2026, changes that: it introduces an optional, non-default static archive (libfbclient.a on POSIX, fbclient_static.lib on Windows) for applications that need to link the client library


Friday
31 July, 2026


face

Big news for anyone using Firebird from Node.js: the pure-JavaScript node-firebird driver shipped eight releases in under a week (v2.6.0 &rarr; v2.14.0), completing its entire roadmap and closing all 47 open issues &mdash; some dating back to 2015. The driver now stands at feature parity with the best Node.js drivers for Postgres and MySQL, while staying pure JavaScript with zero native


face

We are excited to announce the release of cl-firebird v1.0.0 &mdash; a pure Common Lisp database driver for Firebird 3.0, 4.0, 5.0, and 6.0+. Featuring full 1:1 feature parity with node-firebird, this release brings 12-factor connection URIs, thread-safe connection pooling, named placeholder parameter binding, custom type parsers (type-cast), streaming cursors, database events (POST_EVENT),

Older blog entries ->