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.


Friday
12 December, 2025


face

I decided to start the current campaign, with one blog post per week focusing on the different aspects of Open Document Format, to celebrate the 20th anniversary of the standardisation by OASIS, which happened in May 2005.

My hope was to raise the interest around ODF, which is the document format that every conscious user of office suites should adopt in order to maintain full control on his intellectual property (even if we are not professional writers or researchers, the content of our documents is our intellectual property, and we have the right to decide when, how and with whom we want to share it).

My articles were targeting LibreOffice users, as they have the privilege – over other office suite users – of creating documents (and I am not referring only to text, but also to spreadsheets and presentations or drawings) with the only program adopting ODF as native document format.

I wanted to strengthen their understanding of ODF, and explain in detail the enormous value of the open and standard document format they are using in comparison with the closed and proprietary Microsoft office document format, which is unfortunately the most used worldwide to maintain Microsoft lock in and reinforce Microsoft monopoly.

Software supporting OOXML – the technical name of the closed and proprietary Microsoft office document format – as their native document format are in fact strengthening Microsoft lock in just because in their paramount ignorance of the real situation – today, OOXML is the only lock in tool available to Microsoft – they protect Microsoft rather than protecting their users. In reality, they are enemies of their own users, as they use Microsoft handcuffs to prevent them to own and control their intellectual property.

Unfortunately, the absolute majority of office suite users are not aware of the issues – for their intellectual property – related to the closed and proprietary Microsoft office document format, and are just victim of the irresponsible choice about the native document format made by developers of OnlyOffice and WPS Office, and the likes.

Of course, given Microsoft monopoly on office suites, programs must support OOXML to their best, as LibreOffice does, to “steal” Microsoft stronghold on intellectual property, and give it back to legitimate owners, i.e. users of Microsoft office series suites, whatever the name, and of their accomplishes.

While I was trying to explain all this with my blog posts about ODF, something unexpected happened: several journalists picked up the contents of the articles and relaunched them on their media, showing that there is still hope for a sane attitude about document formats, rather than the current “comfortable” behaviour of choosing the most frequently used document format without even thinking to the consequences of the evil strategy associated to it.

Based on this unexpected – and extremely positive – outcome, I have decided to revive the ODF Advocacy project (which was killed twice in the past) by launching ODF News (https://www.odf.news), where I will write about ODF and publish ODF supporting documents.

ODF News will go


Thursday
11 December, 2025


[en] Michael Meeks: 2025-12-11 Thursday

21:00 UTC

face
  • Up early, packed & lugged more luggage to the venue, bags inside bags.
  • Published the next strip on the difficulty of getting audience sensitive content: conferences & communication
    The Open Road to Freedom - strip#47 - conferences and communication
  • Wandered the show talking to people and handing out stickers and documentation; gave a talk on migrating ministries with Guy-Christian.
  • Bid 'bye to friendly partners. Train to the Eurostar with Meven, managed to bump to the earlier train and stated on the E-mail and admin backlog on the move.

face

LibreOffice 26.2 will be released as final at the beginning of February, 2026 ( Check the Release Plan ). LibreOffice 26.2 Beta1 is the second pre-release since development of version 26.2 started at the beginning of June, 2025. Since the previous release, LibreOffice 26.2 Alpha1, 419 commits have been submitted to the code repository and 114 issues got fixed. Check the release notes to find the new features included in this version of LibreOffice.

LibreOffice 26.2 Beta1 can be downloaded for Linux, macOS and Windows, and it can be installed alongside the standard version.

In case you find any problem in this pre-release, please report it in Bugzilla ( You just need a legit email account in order to create a new account ).

For help, you can contact the QA Team directly in the QA IRC channel or via Matrix.

LibreOffice is a volunteer-driven community project, so please help us to test – we appreciate it!

Happy testing!!

Download it now!


Wednesday
10 December, 2025


[en] Michael Meeks: 2025-12-10 Wednesday

21:00 UTC

face
  • Breakfast with the lads; off to the City of Science and Technology (or something) for Open Source Experience.
  • Great to talk to lots of partners, customers, share a booth with Arawa & atol CD, and to catch up with friends old & new.
  • Drinks in the evening with many, learned about some combination of photonic AI, and business updates. Out for a fine dinner with Arawa & atolCD folk.

Tuesday
09 December, 2025


[en] Michael Meeks: 2025-12-09 Tuesday

21:00 UTC

face
  • Up too early, breakfast with Eloy, Chris & Meven. Very long taxi ride to the Nextcloud Enterprise Day - arrived late.
  • Enjoyed some great talks & conversation with lots of people, distributed hard-working-beaver mascots left and right, quick-start guides, French handouts etc.
  • Enjoyed some drinks & snacks, and off to the XWIKI party - again meeting all sorts of fun people.

Monday
08 December, 2025


[en] Michael Meeks: 2025-12-08 Monday

21:00 UTC

face
  • Up early, fond 'bye to girls. Tried to squeeze lots of 1:1's in, taxi to Cambridge with lots of luggage. Worked in the car & waiting room.
  • Moved up the Eurostar times, did a bit of bug-fix hacking on the train - so fun. Lugged luggage across town.

face

Month of LibreOffice stickers

As November started, we kicked off a new Month of LibreOffice campaign, celebrating community contributions all across the project. We do these every six months – so how many people got sticker packs this time? Check it out…

Excellent work! Hundreds of people, all across the globe, have helped out in our projects. And those are just community contributions, not including the hundreds more from our ecosystem and certified developers!

We’re hugely thankful for the work – and, of course, everyone who contributed in November and is listed on the wiki page can get a sticker pack, with the stickers shown above.

How to claim

If you see your name (or username) on this page, get in touch! Email mike.saunders@documentfoundation.org with:

  • your name (or username) from that wiki page – you must include this
  • and your postal address

…and we’ll send you a bunch of stickers for your PC, laptop and other kit. (Note: your address will only be used to post the stickers, and will be deleted immediately afterwards.) If you contributed to the LibreOffice project in November but you’re not on the wiki page, please let us know what you did, so that we can add you!

There is one more thing…

And we have an extra bonus: ten contributors have also been selected at random to get an extra piece of merchandise – a LibreOffice hoodie, T-shirt, rucksack or snazzy glass mug. Here are the winners (names or usernames) – we’ll get in touch personally with the details:

  • Sarah Lim
  • lodf2023
  • @TerryBTwo@ohai.social
  • jcline
  • Aindriú Mac Giolla Eoin
  • CRDF
  • Xəyyam Qocayev
  • @fluidlogic@oldbytes.space
  • Zayed
  • rram

Congratulations to all the winners, and a big thanks once again to everyone who took part – your contributions keep the LibreOffice project strong. We plan to have another Month of LibreOffice in May 2026, but everyone is welcome to see what they can do for LibreOffice at any time!


face

por Gustavo Pacheco

El Festival Latinoamericano de Instalación de Software Libre (FLISoL) 2025 se llevó a cabo los días 25 y 26 de abril en Montevideo. El FLISoL es el evento descentralizado de Software Libre más importante de América Latina.…


Sunday
07 December, 2025


[en] Michael Meeks: 2025-12-07 Sunday

21:00 UTC

face
  • All Saints in the morning, played bass. Home for roast lamb lunch, prepped for crib service.
  • Ed & David over to share it with us. Played games variously.
  • Prepped music for evening service, ran that - Florence spoke. Home to relax.

Saturday
06 December, 2025


[en] Michael Meeks: 2025-12-06 Saturday

21:00 UTC

face
  • Up earlyish, out to All Saints to play Guitar for a fun Local Houses of Prayer (LHOP) kick-off meeting. Home early.
  • Plugged away at E-mail, lunch with H. and E., slugged a bit. Back to the mail & admin backlog.
  • J. returned home, hair-cut, prepared music for evening service tomorrow.

face

La Conferencia Global de LibreOffice 2026 se llevará a cabo en Pordenone, Italia, organizada por el PNlug (Grupo de Usuarios de Linux de Pordenone) y la Universidad de Pordenone, dentro del campus universitario.

El evento comenzará el jueves …


face

A modern C++ wrapper for the Firebird database API.Documentation | Repositoryfb-cpp provides a clean, modern C++ interface to the Firebird database engine. It wraps the Firebird C++ API with RAII principles, smart pointers, and modern C++ features.Features Modern C++: Uses C++20 features for type safety and performanceRAII: Automatic resource management with smart pointersType Safety:


Friday
05 December, 2025


[en] Michael Meeks: 2025-12-05 Friday

21:00 UTC

face
  • Mail chew, worked through a growing admin backlog. Great TTT from Kendy on Collabora Office on Mac.
  • Published the next strip on trying to please everyone:
    The Open Road to Freedom - strip#46 - trying to please everyone
  • Couple of partner calls, sync with Miklos, worked late.

face

LibreOffice Conference 2026 in Pordenone, Italy, and LibreOffice Conference 2027 in Gothenburg, Sweden

LibreOffice Conference 2026 will be organised by PNlug (Pordenone Linux User Group) and the University of Pordenone in the city of Pordenone, on the university campus.

The conference will begin on Thursday, 10 September and will end on the morning of Saturday, 12 September with the usual closing session.

In the days leading up to the conference, there will be a series of internal meetings and the usual community meeting on the afternoon of Wednesday 9 September.

Of course, all the details of the conference, the call for papers, and the final programme with all the side events will be announced during 2026 on this blog and on the conference website.

LibreOffice Conference 2027 will be organised in Gothenburg, Sweden, by the local community led by Leif-Jöran Olsson, who will be involved in the organisation of the 2026 conference to familiarise himself with the process.

Again, all details will be announced on this blog and on the conference website starting in the last quarter of 2026.


Thursday
04 December, 2025


face

After submitting a patch to LibreOffice Gerrit, one has to wait for the continuous integration (CI) to build and test the changed source code to make sure that the build is OK and the tests pass successfully. Here we discuss the situation when one or more CI builds fail, and how to handle that.

Why Build and Test on CI?

After you submit code to LibreOffice Gerrit, reviewers have to make sure that it builds, and the tests pass with the new source code. But, it is not possible for the reviewers to test the code on each and every platform that LibreOffice supports. Therefore, Jenkins CI does that job of building and testing LibreOffice on various platforms.

This can take a while, usually 1 hour or so, but sometimes can take longer than that. If everything is OK, then your submission will get     Verified +1    .

CI Platforms for LibreOffice

Currently, these are the platforms used in CI:

  • Linux / GCC:  gerrit_linux_gcc_release
  • Linux / Clang: gerrit_linux_clang_dbgutil
  • Android Viewer: gerrit_android_x86_64 and gerrit_android_arm
  • Windows: gerrit_windows_wsl
  • macOS: gerrit_mac

Some of the tests are more extensive, for example Linux / Clang also performs additional code quality checks with clang compiler plugins. Also, UITests are not run on each and every platform.

Jenkins LibreOffice CI

LibreOffice CI uses Jenkins

Why Failures Happen and How to Fix?

There can be multiple reasons for why a CI build fails, and give your submission    Verified -1   . These are some of the reasons, and depending on the reason, solution can be different.

1. Your code’s syntax is wrong and compile fails

In this case, you should fix your code, and then submit a new patch set. You have to wait again for a new CI build.

2. The code’s syntax is OK, but it is not properly formatted

You should refer to the below TDF Wiki article and use clang-format tool to format your code properly.

3. Your code’s syntax is OK, but it logically not OK and fails some tests.

In this case, you should try fixing your code logic, and run the tests that fail and make sure they pass. After that, you may send a new patch set and wait for a new CI build.

4. Your code’s syntax and logic is OK, but some machine fails for other reasons like their disk being full or other software/hardware failures or hiccups

In this case, usually resuming the build can be a good option. You may ask on #libreoffice-dev or #tdf-infra IRC rooms for such a resume, or request access, if you submit many patches.

Resume CI build

Resume build in LibreOffice CI

5. Your code’s syntax and logic is OK, but there are issues from other patches.

In this case, intervention from other LibreOffice developers is needed. Informing people on #libreoffice-dev can help, and then you have to re-base your submission in case new patches fix the build issue.

Final Notes

The best way to know the reason of the build failure is to look into


[en] Michael Meeks: 2025-12-04 Thursday

21:00 UTC

face
  • Mail chew, tech. planning call, new Collabora Office launch retrospective call. Lunch.
  • Sync with Lily, Laser, partner slide sync, drove to Cambridge, good to catch-up with people, finance team call. Christmas dinner with lots of the wider Collabora team, good to meet Tina.

face

The Document Foundation (TDF), la organización sin fines de lucro detrás de LibreOffice, continúa fortaleciendo su equipo de desarrollo con nuevos roles orientados a mejorar el diseño y la experiencia de usuario del proyecto. Hoy, nos complace presentar a Dan …


face

I fetched the release notes for FirebirdSQL/php-firebird and made a concise summary of the user-visible changes and upgrade impact for versions from PHP Firebird 5.0.2 up through 6.1.1-RC.2.I retrieved the release entries for 5.0.2, 6.1.1-RC.0, 6.1.1-RC.1 and 6.1.1-RC.2 and distilled the highlights and upgrade impact into a short, actionable summary below.Summary of changes (5.0.2 → 6.1.1-RC.2)-


face

Photo of Dan Williams

The Document Foundation is the small non-profit entity behind LibreOffice. It oversees the project and community, and is now expanding with new developer roles. So let’s say hello to Dan Williams, who joins the team to work on design and user interface (UI) improvements, with an initial focus on macOS:

Tell us a bit about yourself!

I’m from the USA, have lived on both US coasts at various times, and now live back in the “midwest” where I grew up.

I was previously a software engineer, team lead, and manager at Red Hat for more than 20 years. In that time I’ve worked on a large variety of projects, from local networking to cloud networking to desktop software. I spent two years helping build the One Laptop Per Child software stack which was an eye-opening experience from a UI and design perspective. I believe passionately in free and open-source software; all the code I’ve written so far in my career is open-source.

Oddly enough, I’m not new to the LibreOffice community; I was an OpenOffice contributor and co-founded the NeoOffice port to Mac OS X (now called macOS). That led to being hired by Red Hat to package and improve OpenOffice for Fedora and Red Hat Enterprise Linux, where I helped start the 64-bit port and realize the Native Widget Framework that’s still used in LibreOffice today. I eventually handed my Red Hat OpenOffice duties over to Caolán McNamara (now at Collabora) and moved on to networking. I still recognize quite a few of our community members who I worked with before!

Outside of office software I’m the maintainer of the ModemManager WWAN software stack and I seem to have developed a hobby of collecting LTE and 5G base stations. I enjoy playing with hardware (especially if it runs Linux), baking and cooking, building large structures out of wood, and occasionally brewing beer in my basement.

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

A significant part of my new role will echo my early OpenOffice contributions: Mac! I’ll convert the last bits of Carbon API into modern Cocoa ones. This old code involves some pretty core functionality like popup menus and key modifier detection so it’s going to be tricky but we need to do it. Nobody knows how much longer Apple’s going to support HIToolbox but I’d like to be prepared. I’m also going to improve general Mac usability and experience; I’ve been using LibreOffice on macOS since the beginning so I’m familiar with its rough edges.

LibreOffice screenshot, running on macOPS

But the Mac isn’t the only platform so I’ll be driving user interface improvements and fixing annoying bugs everywhere else too, regardless of platform or visual backend. I also look forward to working with the LibreOffice Design community to try out new ideas and see what sticks.

I enjoy the challenge of working throughout the entire codebase, from


face

The Firebird Book, Second Edition is made publicly available via the IBPhoenix digital store. Everyone can download the complete edition free of charge — no strings attached.If you'd like to support Helen’s legacy and the Firebird community, there is an optional pay‑what‑you‑like contribution. Funds will support the organization of the Helen Borrie Memorial Award, recognizing individuals with


Wednesday
03 December, 2025


[en] Michael Meeks: 2025-12-03 Wednesday

21:00 UTC

face
  • Early partner call, sync with Dave, then Ben, then Patrick & Kevin.
  • E's maths progress review call. Interview, weekly sales call, sync with Philippe.
  • All Saints band practice in the evening.

face

LibreOffice 26.2 se lanzará como versión final a principios de febrero de 2026 (consulte el Plan de lanzamiento), siendo LibreOffice 26.2 Alpha1 la primera versión preliminar desde que comenzó el desarrollo de la versión 26.2 a principios de junio …


face

Esta nueva versión del estándar de formato de documento nativo de LibreOffice marca el vigésimo aniversario del único formato de documento abierto para aplicaciones de oficina

Berlín, 3 de diciembre de 2025. The Document Foundation anuncia que OASIS Open (…


face

ODF 1.4 Approved as Oasis Open StandardThis new version of the native LibreOffice document format standard marks the 20th anniversary of the only open document format for office applications

Berlin, December 3, 2025 – The Document Foundation announces that OASIS Open (www.oasis-open.org), the global open-source and standards organisation, has approved the Open Document Format (ODF) for office applications v1.4 as an OASIS standard, which is the organisation’s highest level of ratification.

The release of ODF v1.4 coincides with the 20th anniversary of ODF’s adoption as an OASIS Standard. Since 2005, ODF has served users as a vendor-neutral, royalty-free format for office documents, ensuring that files remain readable, editable and interoperable across platforms.

Several governments and international organisations, including NATO, the European Commission and countries across multiple continents, have mandated ODF for their operations worldwide.

ODF v1.4 maintains full backward compatibility and improves developer documentation, adds better support for assistive technologies for accessibility, improves professional document formatting and visual design capabilities, and expands features for data analysis and technical documentation. These updates reinforce the Open Document Format’s position as a comprehensive solution for office productivity and document creation.

“ODF provides a vendor-neutral foundation for office productivity and collaboration. With v1.4, the standard continues to evolve, supporting cloud collaboration, richer multimedia, and standardised security,” said Svante Schubert, Open Document Format’s TC Co-Chair. “Looking ahead, ODF is moving beyond document exchange towards standardised, semantic, change-based collaboration, enabling the meaningful sharing of interoperable changes across platforms.”

ODF v1.4 safeguards digital sovereignty by removing a single vendor’s control over documents and returning it to the community, to allows individuals and enterprises to independently decide how and with whom to share content, preventing it from being analysed for commercial purposes or potentially shared without the legitimate owner’s knowledge.
Like all other versions of the standard format, ODF 1.4 is based on an XML schema that complies with simplicity and readability guidelines, making files much more robust and secure than those commonly found on the market.

Overall, this is another significant step towards transparency, openness and digital sovereignty, thanks to the collaborative efforts of open-source software developers, advocates and users.
The finalized four-part specification of ODF v1.4 can be found in the OASIS library by clicking here: docs.oasis-open.org/office/OpenDocument/v1.4/os/.

The announcement mentions OASIS sponsors who have not contributed to the development of ODF 1.4, whereas The Document Foundation, which funded the development of the standard alongside companies such as Microsoft and has always advocated for it, is not mentioned at all. Unfortunately, business is business, even when it comes to open standards.

ODF 1.4 New Features

General

  • The writing direction specification has been expanded and clarified.
  • Complex backgrounds, such as colour gradients or hatching, can now be applied to a wider range of objects.
  • Objects can be marked as “decorative” to support accessibility technologies.
  • Shapes can now contain not only simple text and lists, but also tables.
  • The method for specifying

face

LibreOffice 26.2 will be released as final at the beginning of February, 2026 ( Check the Release Plan ) being LibreOffice 26.2 Alpha1 the first pre-release since the development of version 26.2 started at the beginning of June, 2025. Since then, 4651 commits have been submitted to the code repository and 676 bugs were set to FIXED in Bugzilla. Check the release notes to find the new features included in this version of LibreOffice.

LibreOffice 26.2 Alpha1 can be downloaded for Linux, macOS and Windows, and it can be installed alongside the standard version.

In case you find any problem in this pre-release, please report it in Bugzilla ( You just need a legit email account in order to create a new account ).

For help, you can contact the QA Team directly in the QA IRC channel or via Matrix.

LibreOffice is a volunteer-driven community project, so please help us to test – we appreciate it!

Happy testing!!

Download it now!


face

Writer recently got a new markdown import option to take styles from a template, leading to much prettier output when converting markdown to PDF, DOCX or ODT.

This work is primarily for Collabora Online, but the templating feature is available in desktop Writer as well.

Motivation

A previous post mentioned recent improvements to the markdown import/export in Writer.

But if you convert some markdown to e.g. PDF, all the headings just have the default look, wouldn't it be nice to take your organization template and add colors and other formatting there, automatically?

Also, wouldn't it be nice if you could paste as markdown in COOL or copy the current selection as markdown? Which would enable all sorts of interesting use-cases, like using an external API to turn the selection into a summary or translating it to a different language.

Results so far

Here is a sample input markdown:

# heading 1

body text

Here is how it looks like if you template it using the core.git sw/qa/filter/md/data/template.docx sample:

PDF result: templated

curl invocation for this:

curl -k -F "data=@/path/to/test.md" -F "template=@/path/to/template.docx" -F "format=pdf" -o out.pdf https://localhost:9980/cool/convert-to

Or example desktop command-line:

soffice --infilter='Markdown:{"TemplateURL":{"type":"string","value":"./template.ott"}}' test.md

While it would look like this by default:

PDF result: default

The other part is the PostMessage API of COOL, if you want to copy and paste as markdown. What's newly possible:

  • Copy the current selection: set MessageId to Action_Copy and the value to {"Mimetype": "text/markdown;charset=utf-8"}
  • Paste at the current cursor position: set MessageId to Action_Paste and the value to something like {"Mimetype": "text/markdown;charset=utf-8", "Data": "foo _bar_ baz"}

You can read more about the PostMessage API in the COOL SDK.

How is this implemented?

If you would like to know a bit more about how this works, continue reading... :-)

As usual, the high-level problem was addressed by a series of small changes. Core side:

Online side:

Want to start using this?

You can get a development edition of Collabora Online 25.04 and try it out yourself right now: try the development edition. Collabora intends to continue supporting and contributing to LibreOffice, the code is merged so we expect the core of this


Tuesday
02 December, 2025


[en] Michael Meeks: 2025-12-02 Tuesday

21:00 UTC

face
  • Up early, new Collabora Office team call - nice. Planning call, sync with Laser, lunch.
  • Call with Jim, sync with Anna, chart team call, sync with Laser.

face

 

The Document Foundation (TDF) es la entidad sin fines de lucro que respalda el proyecto LibreOffice. Recauda donaciones de los usuarios y cuenta con un pequeño equipo que da soporte y coordina a la comunidad mundial que desarrolla el software. …


Monday
01 December, 2025


[en] Michael Meeks: 2025-12-01 Monday

21:00 UTC

face
  • Still feeling groggy; early meeting on a11y testing. Sync with Miklos, Thorsten, lunch, signed documents, marketing content call.
  • Sync with Naomi, Pedro & Eloy.
  • Dinner, games with E&H&J, music with H. bed.

face

TDF logo and words Code of Ethics

The Document Foundation (TDF) is the non-profit entity behind the LibreOffice project. It collects donations from users, and employs a small team to support and coordinate the worldwide community that makes the software. In TDF there are various bodies including the Board of Directors, Membership Committee, and the Board of Trustees:

Diagram of structure of TDF bodies

These foundation bodies are guided by a set of policies, and now the Board of Directors has voted on a Code of Ethics and Fiduciary Duties. The code ensures that members of the Board of Directors “strive to speak and act with the mission and effectiveness and the best interest, and only the interest, of the foundation in mind.” See here for the results of the vote.

Click here for the full Code of Ethics and Fiduciary Duties

Older blog entries ->