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.
On August 26 we released LibreOffice 26.8. Here’s a video highlighting some of the user-facing new features and improvements, with subtitle translations in over 25 languages, thanks to our worldwide community! (Note: the video is also available on PeerTube.)
Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party.
If you accept this notice, your choice will be saved and the page will refresh.
LibreOffice 26.8 is the first version to display a donation banner in the Launch Centre. This document explains the reasons behind this decision and provides information on The Document Foundation’s sustainability model.
All figures are taken from the financial statements of The Document Foundation Stiftung, based in Berlin, and have been published on the website for every year of the foundation’s existence since its registration.
TDF revenue in 2025
Total revenue amounted to approximately 2.2 million euros.
Of this, over 90 per cent comes from donations, and the remainder almost entirely from the sale of LibreOffice via Microsoft and Apple’s online stores, where the price is set to cover the costs of maintaining the applications on those platforms.
It is worth noting that the same versions available on Microsoft’s and Apple’s online stores can be downloaded freely – and therefore free of charge – from the LibreOffice website.
Over 90 per cent of donations come from private individuals, and less than 10 per cent from public bodies and companies. Therefore, although the suite is widely used by companies and public bodies, it is funded almost entirely by private individuals who contribute small sums according to their means.
How much did TDF spend in 2025
Total expenditure amounted to approximately 1.5 million euros.
Seventy-five per cent of this expenditure was allocated to staff salaries and social security contributions, as well as consultancy contracts. Today, the foundation employs 18 people, 11 of whom have contributed to software development or other related activities, such as quality control.
It is worth emphasising this proportion clearly. Three-quarters of the TDF’s expenditure goes on staff, and the largest share is accounted for by development work, community building and education on the themes of software freedom, open standards and digital sovereignty.
Donations are channelled into constructive activities, rather than administrative costs.
In the past, a significant proportion of development work was awarded to companies that submitted the best bid in response to a tender, but this strategy has changed, and it was decided to bring development expertise in-house so as to steer the software’s evolution and share knowledge with the community.
The surplus in 2025
The surplus is not left unused but is reinvested in the growth already underway: three developers were hired during 2026 and two more will be hired shortly. In addition, various marketing and community development projects are funded from the same source.
The foundation’s expenditure does not follow a uniform pattern relative to its income. The recruitment process takes months, and if income is received before new staff are hired, a surplus will arise that represents planned work rather than unspent money.
TDF also maintains reserves, with the aim of covering at least one year’s operating costs. This figure, of course, increases year on year.
For an organisation with a single predominant source of income, this represents a minimum target. Indeed, a foundation that employs 18 people and supports a community of thousands …
Digital sovereignty is usually discussed in terms of where servers are located and which company holds the contract. Both matter less than the format in which documents are written.
A document is not a piece of paper
The habit of thinking of a digital document as a sheet of paper is understandable and wrong. A sheet of paper carries its own content. Anyone who can read the language can read the page, with no equipment, no permission and no intermediary. A digital document carries no content at all until software interprets it. The file is a set of instructions, and what appears on screen is the result of a program executing those instructions. Change the program and the result may change with it.
This is why documents produced in one application so often look wrong in another: bullet points shift, tables lose their proportions, headings render differently. The content is present. The document, strictly speaking, is not.
The format is the specification that tells software how to perform that interpretation. Whoever controls the format therefore controls what the document means, how faithfully it can be reproduced, and for how long.
What makes a format open
Openness is not a marketing description. It has established criteria, set out in instruments such as the Open Definition and the European Interoperability Framework, and used by public administrations to assess formats for procurement. Four conditions matter most.
The specification must be published in full and freely available. Nobody should need a licence, a fee or a patent settlement to implement it. The format must be usable by anyone for any purpose, without discrimination between users, applications or business models. And it must be governed by a body independent of any single vendor, so that future versions are decided in public rather than in a company’s product roadmap.
These conditions exist for a practical reason. They are what guarantees that a document written today can still be opened in thirty years by software nobody has yet written.
ODF meets these conditions
The Open Document Format was developed in the open under OASIS, the international standards consortium, and became an OASIS standard in 2005. It cleared its Draft International Standard ballot at ISO/IEC JTC 1/SC 34 in May 2006 with unanimous approval and was published as ISO/IEC 26300 that November. The specification is public, royalty-free, versioned, and maintained by a technical committee whose work is a matter of record. Version 1.4 was approved by OASIS in December 2025.
ODF is not the LibreOffice format. It is implemented by a range of applications from different suppliers, and any developer may implement it without asking anyone. LibreOffice uses it natively, which is a consequence of the format’s openness rather than a claim of ownership over it.
OOXML does not
OOXML, the format underlying DOCX, XLSX and PPTX files, carries an ISO number. It was granted one in 2008 through a fast-track procedure whose conduct is now part of the documented history of …
Berlin, 26 August 2026 – The Document Foundation today announced the availability of LibreOffice 26.8, the new major release of the free and open source office suite, for Windows, macOS and Linux. Development began in December 2025, and the release consolidates the work of 206 contributors, of whom 155 are volunteers.
LibreOffice 26.8 concentrates on three areas: the typographic quality of what the suite produces, the range of writing systems it handles correctly, and the fidelity with which documents survive exchange with other office suites.
Writing systems
The largest single body of work in this release addresses bidirectional and complex text. Writer now detects paragraph direction automatically when documents or plain text are opened or pasted. Line wrapping places end-of-line spaces according to the direction of the paragraph rather than that of the adjacent characters. Object resize handles behave correctly in right-to-left and vertical CJK documents. Bidirectional control characters are now visible alongside other formatting marks. In Calc, typing right-to-left text into an empty cell sets the direction of that cell automatically.
Alignment semantics have been revised accordingly: new documents default to start alignment rather than left, and changing paragraph direction no longer mirrors explicitly left- or right-aligned paragraphs.
Math has gained named functions and operators for the N’Ko and Adlam scripts, used for the Manding languages of West Africa and for Fulani, together with left-pointing vectors and harpoons for right-to-left formulas. The CJK text grid option has been renamed to reflect what it actually does, namely enable the genkō yōshi manuscript grid. Font names recorded in languages other than the interface language are now resolved, so documents authored elsewhere display in the typefaces their authors chose.
None of this work has a commercial market. It was done anyway, because a foundation does not have to ask whether a language pays for itself before deciding to support it.
Typography
Writer introduces the Paragraph Composer, a text layout algorithm that balances word spacing across consecutive lines instead of optimising each line in isolation. The single-line, greedy approach used by word processors has been standard since the technology existed, and produces justified text that alternates between crowded and sparse lines wherever long words fall near a break.
OpenType font variations are now natively supported, allowing variable fonts to be used as designed, including axes that adjust letterform contrast and proportion to the size at which text is set.
Baseline grid alignment now works correctly for text inside frames, and the grid itself can be displayed while editing, with a configurable colour.
Document exchange
LibreOffice Chart provides basic round-trip support for the newer chart types that Microsoft Office writes into OOXML files: box-and-whisker, funnel, Pareto, sunburst, treemap and waterfall. These charts cannot yet be rendered or edited. LibreOffice displays a message identifying the unsupported type and preserves the underlying definition, so that a file opened and saved in LibreOffice returns to its originating application intact. Region map charts carry extensive geographic data that is not preserved; the chart type survives …
My name is Rohan. I am currently in Berlin, Germany, and my background is in mechanical engineering and I have a master’s degree in sustainable mobility and robotics. I recently worked on my master’s thesis, where I used LibreOffice closely on macOS. That experience actually played a big role in bringing me closer to the project.
Outside of my academic and technical work, I am interested in open source software, mobility, robotics, and learning how large software projects are built and maintained. Contributing to LibreOffice has been a very new and rewarding experience for me, because I did not come from a traditional software engineering background.
At the moment, I am exploring macOS-related development work, especially around OfficeBean and native window handling. One of the issues I have been looking into is adding macOS support for OfficeBean, which involves understanding how Java AWT, native macOS views, and LibreOffice’s VCL layer interact.
So far, my merged contributions have mostly been in the LibreOffice core repository, around C++ cleanup, refactoring, and modernisation. These include:
Some of my other patches have not been merged, but they still helped me learn a lot about the codebase, Gerrit, code review, and how to communicate with reviewers.
I also contributed to the developer documentation by adding macOS-related LCOV information to the Development/LCOV wiki page. I wanted to document what I learned so that other macOS contributors could have a clearer path when using coverage tools.
I chose to become a TDF member because LibreOffice has personally helped me a lot, especially during my master’s thesis. While using it closely, I noticed bugs and small rough edges, and that made me curious about how such issues are reported and fixed.
After attending the LibreOffice Conference in Budapest, I became much more interested in the community behind the project. I saw how welcoming and serious the community is about open standards, user freedom, and long-term software sustainability.
For me, becoming a TDF member is a way to give back to a project that supported my own academic work. It is also a way to stay connected with the community and keep learning from people who have much more experience in open-source development.
In the future, I would like to continue improving my understanding of LibreOffice’s core codebase, especially in areas related to C++, macOS, VCL, and developer tooling. I am still learning, so I want to take on tasks step by step and contribute in a way that is useful and maintainable.
I think LibreOffice really benefits from better onboarding paths for new contributors, especially people who …
It has become a commonplace to describe the Microsoft 365 Ribbon as the finest office interface available — the most polished to look at and the most ergonomic to use. The claim is repeated so often that it tends to pass unexamined. It deserves examining, because hidden inside it is an assumption that quietly does most of the work: the idea that there exists a single best interface at all.
A competent design — for one kind of user
Let us begin by granting what is true. The Ribbon is a capable piece of design. It was built to help an occasional or intermediate user discover features by browsing rather than by memorising, and for that user it does its job well. Saying so is not a concession wrung out reluctantly; it is simply accurate, and any honest discussion should start there.
But “well-designed for a particular user” is not the same thing as “best interface,” and treating the two as equivalent is where the reasoning slips. An interface optimised for one persona is, by construction, less suited to the others: the power user who works from the keyboard and resents losing vertical screen space, the migrating user carrying twenty years of muscle memory, the user who depends on assistive technology, the user on a small or low-resolution display. A single fixed layout cannot be best for all of them at once. It can only be best for some, at the expense of the rest.
Ergonomics is a trade-off, not a verdict
The same applies to the ergonomic claim, only more sharply, because ergonomics is something one measures rather than asserts. The research on interface efficiency is consistent on one point: how well an interface performs depends on the task, its frequency, and the expertise of the person doing it. Discoverability and raw throughput pull in opposite directions. An interface that makes features easy to find for a newcomer is rarely the one that lets an expert move fastest, and the reverse is equally true.
So the Ribbon makes a trade. It spends vertical screen space and a measure of expert speed to buy browsability for the less frequent user. That is a perfectly reasonable bargain — for the people it was struck on behalf of. Calling it “the best ergonomics,” though, simply declines to name what was given up to get there. There is no free lunch in interface design; there is only a choice about who pays.
The real question: who decides?
This brings us to the point that actually matters. When a product ships a single interface, it has made the ergonomic decision on the user’s behalf and removed it from their hands. The trade-off still exists — it has merely been settled by someone else, once, for everyone.
LibreOffice takes the opposite path. It offers the traditional menu-and-toolbar layout, the Tabbed interface, Tabbed Compact, the Groupedbar, a Sidebar, and a Single Toolbar mode, and it lets each user choose the one that fits their work, their hardware, and their …
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
LibreOffice is a worldwide project made up of hundreds of people: volunteers, developers at ecosystem companies, and the 18-person team at The Document Foundation (the non-profit entity that coordinates the project and community). So, what has the team been working on recently? Here’s a quick summary:
CppunitTest_sc_swarmsolvertestARRAYTOTEXT function tests as FunctionsTestThemeExport::writeOutMarkdown_SwTableNodeWhen governments and organisations talk about “digital sovereignty,” they usually mean one thing in practice: the ability to choose, control, and if necessary replace the software they depend on — without asking permission from a vendor.
It sounds simple. It rarely is.
Document software sits at the centre of almost every organisation’s operations. Contracts, reports, budgets, policy documents, public communications: they all live in files. And for decades, the format of those files — and therefore the tools required to open, edit, and share them — has been controlled by a single commercial entity. That is not sovereignty. That is dependency with a friendly interface.
LibreOffice Technology exists to make genuine sovereignty possible. Not as a promise, and not as a political statement — but as a technical architecture that removes the dependency by design.
This post explains what LibreOffice Technology actually is, why it is categorically different from a “free alternative to Microsoft Office,” and why it is the only open platform capable of supporting software that is fully compatible with the demands of digital sovereignty. It also reviews what several months of deployments, policy decisions, and one very public debate over what “sovereign” actually means have confirmed about that architecture since we first started making this argument.
Beyond the Application: LibreOffice Technology as a Platform
Most people who encounter LibreOffice encounter it as an application — a word processor, a spreadsheet editor, a presentation tool. That is a reasonable introduction, but it misses what makes LibreOffice Technology significant.
LibreOffice Technology is the underlying platform on which LibreOffice — and a growing number of other products — is built. It is a modular, open-source software framework for creating document applications. It includes rendering engines, import/export filters for dozens of file formats, scripting infrastructure, accessibility layers, and interfaces for integration with operating systems, cloud environments, and enterprise software stacks.
Think of it the way you might think of a general-purpose operating system kernel: the kernel itself is not what users interact with directly, but it is what makes everything else possible — and it is what determines whether the system is genuinely open or merely open-looking.
LibreOffice Technology is governed by The Document Foundation (TDF), a non-profit foundation incorporated under German law. Its source code is publicly available, its governance is transparent, and its development is carried out by a global community of contributors from dozens of countries and organisations — including Collabora, allotropia, Red Hat, and many others.
No single company controls it. No acquisition can change its licence. No pricing decision by a distant board can determine whether your organisation can keep using it next year.
That is what a platform for digital sovereignty looks like.
Open Standards Are Not Optional: The Role of ODF
Sovereignty over software is meaningless if the data is not equally free.
A document format is not just a technical specification. It is a commitment about who can read your files in ten years, which tools can process them today, and whether you are locked into a particular vendor’s …
I’m Aleksi, and I live in Oulu, northern Finland. I graduated this spring with a bachelor’s degree in business information technology, and before that I did a vocational degree in software development. Work-wise, my background is in software engineering: I worked on a secure Android smartphone, mostly fixing operating system bugs.
Outside of that, I’m into retro computing: old machines, old phones, and the software that ran on them. There is a lot to learn from software written back when it could only be shipped on physical media. Every time I sit down with a piece of old software, I notice a detail I want to try building myself: an interesting design decision that makes the UI stand out, or a feature that makes me wonder how on earth it was done.
I also like to hang out at my local hacklab and volunteer at gaming festivals. And of course, I like to work on LibreOffice too. What makes LibreOffice interesting to me is that its codebase has a long history. Reading the code and going through the commits allows me to look back in time and see how the software has evolved over the years.
I’m currently working on smaller code fixes. I pick up bugs from Bugzilla, try to reproduce them, and ultimately submit a patch that fixes the issue. In a codebase the size of LibreOffice one can’t just aimlessly duct tape a solution and hope it works. One has to understand the root cause to be able to look in the right place and understand the effect that the change has on the bigger picture.
Coming from a background of debugging Android, I quite enjoy that part of the work. Also, everyone in the community is genuinely great to work with. Code reviews in particular taught me a lot, when a more experienced developer pointed out something that I’d never have spotted myself.
Becoming a member felt like a way of saying that I’m in this for the long term rather than just passing through. Before I started contributing, I was a bit scared of putting code out under my own name. I felt like my code wouldn’t be good enough, and that I could only contribute to open source after decades of development experience.
Boy, was I wrong. Going through the issues thoroughly (the community likes to leave hints in Bugzilla comments), understanding the problem, and submitting the best patch I could manage turned out to be enough. Having a mentor and the community’s support on IRC, where I could ask questions whenever I needed to, helped a lot too.
I’m planning to move from smaller fixes towards more interesting bugs (our Bugzilla doesn’t contain any …
The LibreOffice Conference 2026 will take place in Pordenone, Italy, from September 10 – 12. And now the schedule is online, with:
FBSimCity, the explorable isometric city of Firebird internals, is at v0.9.0 — 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
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
Correction (added 9 August 2026): the section below headed “A synchronous replica that dies hangs commits” 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
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
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 → v2.14.0), completing its entire roadmap and closing all 47 open issues — 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
We are excited to announce the release of cl-firebird v1.0.0 — 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),
In the past we run several surveys to better understand the use cases for Calc, Impress, Draw, and Writer templates. And since TDF hired a developer for Base it’s time to investigate this module.
We collected a couple of questions that address not only actual users of LibreOffice Base but also people who use other tools or no database at all.
So please participate at https://survey.documentfoundation.org/493555 (expired August/18th).
If you are afraid of the English language either use a translator or let us do it. The more participants we get the better we can steer the development. As usual, we will present the results in this blog.
FBSimCity — the explorable isometric city of Firebird internals — is at v0.4.0, and this release adds a whole backup yard, built around what gbak and nbackup actually do. gbak: the backup that pins your OIT gbak takes a logical backup online: it attaches like any other client and reads every table through a snapshot transaction. That snapshot is the interesting part — it pins
I've published FBSimCity, an interactive visualization of Firebird internals: an explorable isometric city where every building is a subsystem from the classic Conceptual Architecture for Firebird paper (Chan & Yashkir), and queries commute through the pipeline as glowing particles — REMOTE harbor → Y-valve → DSQL → JRD, with the lock manager tower watching over it. The
LibreOffice 26.8 will be released as final at the end of August, 2026 ( Check the Release Plan ). LibreOffice 26.8 RC1 is the third pre-release since development of version 26.8 started at the beginning of December, 2025. Since the previous release, LibreOffice 26.8 Beta1, 133 commits have been submitted
General Activities LibreOffice 26.2.4 was announced on June 5 Olivier Hallot (TDF) added a help article for presentation sections, added support for MathML markup in help pages, improved help for Writer’s break submenu and for some Calc functions and updated help after UI changes Adolfo Jayme Barrientos improved strings in
We are thrilled to share the journey of our last 7 releases (from v2.3.3 to v2.6.0), which mark one of the most transformative periods in the history of the node-firebird driver. With this series of releases, we’ve migrated the driver to native TypeScript 7, implemented native Promise & async/await APIs, added support for Firebird 5.0 and 6.0 features,
Not bad for a few days of work , There are still lot's of bugs and UI inconsistencies ps: It's a fork of existing extension but using updated node drivers and updated roadmap (Firebird 6 support / Typescript 6.x)pps: I need to recover my MFA Azure Developer account to publish it soon
Going Native-Free: Introducing the Pure Node.js Wire Driver for Firebird Published in Engineering • Pull Request #168 Summary If you have ever built Node.js applications that communicate with a Firebird database, you are likely familiar with the standard setup routine. Traditionally, high-level drivers depended heavily on the native client library (
LibreOffice 26.8 will be released as final at the end of August, 2026 ( Check the Release Plan ). LibreOffice 26.8 Beta1 is the second pre-release since development of version 26.8 started at the beginning of December, 2025. Since the previous release, LibreOffice 26.8 Alpha1, 445 commits have been submitted
IBPhoenix is pleased to announce the release of a new free ebook:Practical Firebird Performance Diagnostics: A Structured ApproachUnlike traditional performance tuning guides, this ebook focuses on the reasoning behind successful diagnostics. It introduces a structured framework that helps Firebird professionals move from observed symptoms to defensible explanations by classifying problems,
General Activities LibreOffice 25.8.7 was announced on May 12 Olivier Hallot (TDF) improved the explanation for DATE function in Calc’s Function Wizard, continued documenting in help how LibreOffice treats non-integer values for function parameters expecting integer values, added a help page for Draft View in Writer, added help for Calculated
Firebird is gaining support for Unix Domain Sockets (UDS) through PR #9034, a feature aimed at improving local inter-process connectivity, especially in constrained environments like Android and iOS. The change introduces a new unix:// connection string format and a RemoteServiceUnixSocket configuration option, allowing Firebird clients and services to communicate over filesystem-based sockets
General Activities LibreOffice 26.2.3 was announced on April 30 Olivier Hallot (TDF) updated Writer’s Compatibility options help, improved documentation for wrapped images in headers, worked on documenting in help how LibreOffice treats non-integer values for function parameters expecting integer values, improved help for Declare statement in BASIC, added help for
| Imprint Privacy Policy | |
|
The Document Foundation is not responsible for the content on planet.documentfoundation.org. However - if you have any concerns about content please contact act Mike Saunders for moderation. Copyright information: Unless otherwise specified in the author's blog, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the "Mozilla Public License v2.0". "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy. |
 |
| this site runs a modified version of planet.opensuse (https://github.com/openSUSE/planet.opensuse.org) © 2010 Pascal Bleser and the openSUSE Community. | |