Recent Posts

Meet the LibreOffice community at FOSDEM 2026!

State of the Project – Calendar Year 2025

Version 1 of TDF Community Bylaws

Why open standards are extremely beneficial to end users

LibreOffice Podcast, Episode #6 – Language support

The Future of Open Standards and the Importance of ODF

LibreOffice community focus: Design

LibreOffice’s design community works on the software’s user interface (UI), improving its usability and accessibility. With LibreOffice 6.0 due to be released at the end of the month, we talked to members of the community to get their perspectives on the new version…

What have you been working on in preparation for LibreOffice 6.0?

Various things, including:

  • New table styles and new gradients (click for bigger):

  • The LibreOffice 6.0 motif/splash screen:

  • And menu and toolbar improvements

What are your favourite new features in this release?

Both GSoC (Google Summer of Code) projects are really nice: the revamped customization dialog, and the special character dialog with quick access from the toolbar. In addition, there’s the ability to rotate images to arbitrary degrees, and many other small improvements.

What tools and services do you use in the design community?

At the moment we use Balsamiq Mockups, but next we switch to Pencil. In addition, we use LibreOffice Draw (eg for the new motif) and Inkscape. For communication, we are active on IRC in the #libreoffice-design channel and Telegram.

Finally, how can people get involved with the design community?

A big thanks to the design team for their input and improvements in LibreOffice 6.0. For our final Community Focus, we’ll talk to the development community – more on that soon!

The Document Liberation project announces five new or improved libraries to export EPUB3 files and import AbiWord, MS Publisher, PageMaker and QuarkXPress documents

Berlin, January 22, 2018 – The Document Liberation Project announces five new or improved libraries to export EPUB3 and import AbiWord, MS Publisher, PageMaker and QuarkXPress files. The libraries have been originally developed for the LibreOffice 6.0 major release, but can be used by any other software thanks to the OSI (Open Source Initiative) compliant license.

libe-book exports LibreOffice ODT files to EPUB3. At the moment it offers just basic features, but development is still undergoing and new features will be added before the next major release. The library can be downloaded from https://sourceforge.net/projects/libebook/. A description of the architecture and the features is available here: https://vmiklos.hu/blog/basic-epub3-export.html.

libabw imports AbiWord documents, and can be downloaded from http://dev-www.libreoffice.org/src/libabw/. The library home page is at https://wiki.documentfoundation.org/DLP/Libraries/libabw.

libmspub imports MS Publisher documents, and can be downloaded from http://dev-www.libreoffice.org/src/libmspub/. The library home page is at https://wiki.documentfoundation.org/DLP/Libraries/libmspub.

libpagemaker imports PageMaker 6/7 documents, and can be downloaded from http://dev-www.libreoffice.org/src/libpagemaker. The library home page is at https://wiki.documentfoundation.org/DLP/Libraries/libpagemaker.

libqxp imports QuarkXPress 3.1/4.1 documents and templates and can be downloaded from http://dev-www.libreoffice.org/src/libqxp/. The library home page is at https://wiki.documentfoundation.org/DLP/Libraries/libqxp.

The Document Liberation Project was created to empower individuals, organizations and governments to recover their data – hidden inside obfuscated proprietary file formats – and migrate them into perennially accessible standard file formats.

To return effective control over content to the real authors, the Document Liberation Project develops software libraries that can be used by applications to read data in proprietary formats. The libraries are currently used by Calligra, Inkscape and Scribus.

Sunday Marketing #3

Google Trends is a service which compares end user searches for specific terms, and as such is a useful marketing tool to get some insight on the awareness of LibreOffice in comparison with other applications. I have compared the five alternatives to the leading office suite during the last 12 months: LibreOffice is leading, followed – as expected – by OpenOffice and WPS Office. LibreOffice is also leading in term of geographical coverage.

Wednesday Community #2

The sun never sets on the LibreOffice community, as there are always active members in some countries. Unfortunately, only a minimal part of this global effort is reflected on this blog, which should feature all activities and achievements. In order to get to this objective, we warmly invite all native language communities around the world to send us a short synopsis and a couple of pictures – if available – every time they do something significant for LibreOffice: a talk at a conference, a booth at an exhibition, a meeting, a conference, a localization sprint, or any other event. The same for achievements such as LibreOffice adoptions by government bodies, central or local public administrations, or large enterprises. Just send an email to media@documentfoundation.org, and we will take care of writing the blog post (if necessary, we will translate the local language to English).

LibreOffice community focus: QA (quality assurance)

With LibreOffice 6.0 due to be released at the end of the month, we’ve been talking to various communities involved in the project. In the last couple of weeks, we’ve chatted with the localisation and documentation teams, and today it’s the turn of QA (quality assurance), which is coordinated by Xisco Fauli…

What has the QA community been working on in preparation for LibreOffice 6.0?

During the development of LibreOffice 6.0, three Bug Hunting Sessions were held (6.0 Alpha1, 6.0 Beta1 and RC1), the last one just two weeks ago. There was also a parallel event organized by Muhammet Kara in Ankara, where volunteers gathered to test LibreOffice 6.0 RC1. Besides that, the QA team is constantly testing the latest daily builds, testing new features, and triaging the bugs reported on Bugzilla.

What are your favourite new features in this release?

That’s a difficult question, especially taking into account all the improvements done in this release to LibreOffice Android Viewer, to LibreOffice Online or the work done by the Google Summer of Code students among others. But if I had to choose one, I think I’d go for the characters dialog refactoring done by Akshay Deep and the UX (user experience) team, as this is probably the feature I will use the most in the near future. Here’s how it looks:

What tools and services do you use in the QA community?

A very handy tool recently completed by Markus Mohrhard is the automated updater for Windows and Linux, which allows the QA team to test daily builds without having to manually download the latest build every time.

This is very practical as testers no longer need to worry about constantly updating to the latest build, and can focus more on testing the program instead, assured that they are testing changes done to the code just the day before.

This tool was presented at the beginning of the LibreOffice 6.0 development cycle, and I believe it will have a very positive impact on the quality of 6.0 as it shortens the time between a problem being introduced in the code, and the time it’s found.

Another tool we’ve been using for some time now is the bibisect repositories, which allow us to find the exact code commit where a bug was introduced, increasing the chances that the bug gets fixed and reducing the time until it gets fixed.

Another tool which is fulling working now is a set of scripts called office-interoperability-tools that we use to automatically find document layout regressions in the master code branch compared to other office suites (in our case we use MS Office). Right now we use it with 8,450 files, and I believe it will also have a positive impact on the quality of LibreOffice 6.0.

Finally, it’s important to mention the main tool used in QA, Bugzilla, the place where all bugs are reported and triaged. Then there’s the wiki page where the QA documentation can be found, and testlink, the application to manage manual tests.

Finally, how can people get involved with the QA community?

The’re many ways one can help LibreOffice QA. Probably the simplest one would be: download the latest pre-release build (LibreOffice 6.0 RC2 as of today), install it and use it as you would use LibreOffice in your daily basis (but take into account it’s still a pre-release, so it’s not recommended to use it with important documents). If you find anything working incorrectly, please report it to Bugzilla.

On the other hand, if you prefer to follow a set of manual tests, you can use testlink (see the documentation for that. We also need help to triage bugs that are not-yet-confirmed, or retest old bugs to see if they might have been fixed.

Lastly, if you’re looking for something especially exciting things to do, you can help us to test daily builds, bisect bugs or write UI-tests. Don’t hesitate to join the #libreoffice-qa channel and say hello. We’ll be grateful to help you with any question or problem you have!

Much gratitude to Xisco and the diligent QA community for helping to make LibreOffice 6.0 a solid release. Their efforts are appreciated by users across the world. Next up, we talk to the design and development communities – more on this blog very soon…

Tender for consultancy on LibreOffice feature implementation incl. on-site development training (#201801-01)

The Document Foundation (TDF), the charitable entity behind the world’s leading free office suite LibreOffice, seeks for companies or individuals to

provide consultancy on implementing features in LibreOffice

to start work as soon as possible. TDF is looking for an individual or company to give technical consultancy on the implementation of one or more of the following:

As part of the tender, TDF is explicitly looking into on-site development training on these topics for the community to share knowledge and enable contributors to get involved. This training is to be delivered during the next LibreOffice Hackfest in Hamburg (April 7-8, 2018)

  • both in groups not larger than four people, ideally via pair programming
  • as well as a public presentation during the event
  • the latter one will also be published by TDF as recording for reference

More details on this approach can be found at https://listarchives.documentfoundation.org/www/board-discuss/msg03988.html

Required skills

  • Extensive knowledge of C++
  • Experience working on the LibreOffice source code
  • Available for a two day in-person meeting at the next Hackfest in Hamburg (April 7-8, 2018)
  • Available for preparation and aftermath coordinating with a community member over email and/or video conference software (approx. 1-2 additional man days).

We exclusively use free, libre and open source (FLOSS) software for development wherever possible, and the resulting work must be licensed under the the Mozilla Public License v2.0.

Other skills

  • English (Conversationally fluent in order to coordinate and plan with members of TDF)

Applications should

  • contain a maximum of 300 words on the developer you intend to send to the Hackfest as consultant
  • contain a maximum of 300 words on the issue the developer intends to help implementing

TDF welcomes applications from all suitably qualified persons regardless of their race, sex, disability, religion/belief, sexual orientation or age.

As always, TDF will give some preference to individuals who have previously shown a commitment to TDF, including but not limited to certified developers and/or members of TDF. Not being a member, or never having contributed before, does not exclude any applicants from consideration.

The task offered is a project-based one-off, with no immediate plans to a mid- or long-term contractual relationship. It is offered on a freelance, project basis. Individuals and companies applying can be located anywhere in the world.

TDF is looking forward to receiving your applications, your financial expectations and the earliest date of your availability, via e-mail to Florian Effenberger at floeff@documentfoundation.org no later than February 5, 2018. You can encrypt your message via PGP/GnuPG.

Applicants who have not received feedback by February 18, 2018 should consider that their application, after careful review, was not accepted.

Press Releases

Announcement of LibreOffice 25.8.4

Berlin, 18 December 2025 – LibreOffice 25.8.4, the fourth minor update to the free office suite developed by volunteers for…

Open Document Format

Why open standards are extremely beneficial to end users

Whenever I talk to other technology users — including CTOs, CSOs and ICT managers, who in theory should have a…