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.

22 October, 2021


Have you ever edited a document in LibreOffice in more than one window? Right, neither have I. Who'd think about LibreOffice and more than one user at the same time, right? Except ... somebody did and that's how collaborative editing based on LibreOffice works. For whatever strange reason, somewhen in the past somebody thought that implementing multiple views for one document in OpenOffice (StarOffice?) was a good idea. Just select Window->New Window in the menu and you can edit your favourite document in 50 views that each show a different part of the document and update in real time. And that, in fact, is how collaborative editing such as with Collabora Online works - open a document, create a new view for every user, and there you go.

But, given that this has never really been used that much, how well did the original relevant code perform and scale for more users? Well, not much, it turns out. Not a big surprise, considering that presumably back when that code was written nobody thought the same document could be edited by numerous users at the same time. But I've been looking exactly into this recently as part of optimizing Collabora Online performance, and boy, are there were gems in there. You thought that showing the same document in more views would just mean more painting also in those views? Nah, think again, this is OpenOffice code, the land of programming wonders.

Profiling the code

When running Online's perf-test, which simulates several users typing in the same document, most of the time is actually spent in SwEditShell::EndAllAction(). It's called whenever Writer finishes an action such as adding another typed characters, and one of the things it does is telling other views about the change. So here LO spends a little time adding the character and then the rest of the time is spent in various code parts "talking" about it. A good part of that is that whenever an action is finished, that view tells the others about it happening, and then all those views tell all other views about how they reacted to it, making every change O(n^2) with the number of views. That normally does not matter, since on the desktop n generally tends to be 1, but hey, add few more views, and it can be a magnitude slower or more.

Redrawing, for example, is rather peculiar. When a part of the document changes, relevant areas of the view need redrawing. So all views get told about the rectangles that need repainting. In the desktop case those can be cropped by the window area, but for tiled rendering used by Online the entire document is the "window" area, so every view gets told about every change. And each view collects such rectangles, and later on it processes them and tells all other views about the changes. Yes, again. And it seems that in rare cases each view really needs its own repaint


Impress is now able to correctly render shadows for table shapes, even if the shadow itself or the fill of the table cells have transparency. The result is now compatible with PowerPoint.

First, thanks to our partner SUSE for working with Collabora to make this possible.


We got a PPTX document, which has a table shape with pink background and a blurry shadow. Impress rendered a red background, making the text hard to read.

The request was to improve the shadow rendering to be PowerPoint-compatible and in general correctly support transparency when it comes to table cell fills and table shadows.

Results so far

The table shadow now looks like this:

Figure 1. New render result in Impress

Matching the reference rendering:

Figure 2. Reference render result

While background was red previously:

Figure 3. Old render result in Impress

You can see that not only the background in the top center cell is pink now, but the blurry table shadow is still correct.

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 fixes:

With these, it’s now possible to add transparency to both table cell fills and to table shadows, and the rendering will take both into account, correctly.

Want to start using this?

You can get a snapshot / demo of Collabora Office and try it out yourself right now: try unstable snapshot. Collabora intends to continue supporting and contributing to LibreOffice, the code is merged so we expect all of this work will be available in TDF’s next release too (7.3).

21 October, 2021


Rafael Lima from the Brazilian LibreOffice community is working on an extension to remove blank cells in LibreOffice Calc. It has four modes (single column, single row, blank rows and blank columns). Here’s a quick animation of it in action:

So far, the main functionality is there, but Rafael would like to improve it. We asked him for some more info…

What does the extension do?

The main purpose of this extension is to remove blank cells to easily compact data. For instance, suppose you have a table with data and then you delete the contents of some rows. The next thing you might want to do is remove these blank rows to compact your table. By using the Remove Blank Cells extension this can be done with a single click.

Currently the extension supports four modes to remove blank cells. The simplest one is when you select a single row or column, then the extension will detect the selection and compact the data removing all blank cells. However, if a matrix is selected, then a message will be displayed and you can choose if blank rows or blank columns are to be removed.

When did you start making it?

I started writing the extension in February this year and finished the first version in less than one month. Then I kept testing it and working on improvements and the final version was finished in July.

At first the extension focused on my use case, because in my work with data analysis I often have to remove blank rows and columns. However, after seeing many people asking about how to remove blank cells in LibreOffice, I decided to pack it and make it available for everyone since it might be useful for other people.

What are the current limitations of it?

The main limitation of the extension is when the user wants to process very large tables (with tens of thousands of rows), which might take some time to finish. In these cases a progress bar is shown so the user can keep track of the data processing.

Moreover, the extension still does not support translations, so the user interface is only available in English. I plan to support translations in the next release.

How can people help to improve it?

Because this is the first released version of the extension, I would appreciate having more people testing it and reporting issues on the extension’s GitHub page.

I would also like to invite the community to create a better icon for the extension, so that it would be more in line with the default icon theme in LibreOffice.

In the future I will also need some assistance with translating the extension’s strings.

So, everyone is welcome to try out the extension – and if you have some technical knowledge, jump in and help Rafael and the community to improve it! Check out the wiki for more information on extension development.

20 October, 2021


Here are some more videos from the LibreOffice Conference 2021! Check out the playlist, using the button in the top-right – or scroll down for links to individual videos:

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.

Individual links

Note: many of these are also available on PeerTube, and more will be added…

Stay tuned for more videos from rooms 2 and 3 of the conference!

19 October, 2021


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 student developers into free and open source software development. Seven projects were finished successfully. Students and mentors enjoyed the time, and here we present some of the achievements, which should make their way into LibreOffice 7.3 in early February 2022!

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

100 Paper Cuts by Bayram Çiçek

Mentors: Muhammet Kara (Collabora), Heiko Tietze (TDF)

100 Paper Cuts aims to improve user interface, implementing enhancement requests and solving the most annoying issues on the user experience (UX) side of LibreOffice.

Bayram fixed six bugs from different topics. Most notable are border preview not showing the diagonal border option, a bug where cropping flipped images occurred at the wrong side, and mouse-over effect for different palettes in the area tab.

Learn more about 100 Paper Cuts in the final report.

Screenshot of diagonal borders

Integrate .ui dialogs with translation tooling/string search webservice to help translators by Sary Nasser

Mentors: Christian Lohmaier, Olivier Hallot (TDF)

Sary automated the adding of screenshots to our translation platform, Weblate, while associating them with translatable words. This will greatly help translators by providing context for their work.

Learn more about the translation tooling in the final report.

Tests for the VCL graphic backends by Akshit Kushwaha

Mentors: Tomaž Vajngerl, Luboš Luňák (Collabora)

LibreOffice adapts its user interface to different operating systems with the help of its graphics toolkit Visual Class Library (VCL). Thanks to Akshit’s work, we have a working suite of automated graphics rendering tests. There is now also the ability for users to run the tests manually, inspect the results and attach them to our bug tracker in case there is a problem.

Learn more about the tests in the final report.

Screenshot of VCL tests

Improving table styles by Balázs Sántha

Mentors: László Németh (independent), Michael Stahl (allotropia)

This project resulted in fixes for the most annoying Writer table style issues. Further work is needed to provide full DOCX compatibility.

Learn more about DOCX tables styles in the final report.

Make SVM (StarView Metafile) format independent of the VCL Metafile + tests of the format by Panos Korovesis

Mentors: Tomaž Vajngerl, Miklos Vajna (Collabora)

Thanks to the work of Panos, the SVM file format is handled independently of internal VCL constructs, which will make important reorganisation of the VCL code possible. Panos also created automated tests for the SVM format.

Learn more about the SVM project in the final report.

Show text styles together in the sidebar by Anshu Khare

Mentors: Mike Kaganski, Tomaž Vajngerl (Collabora), Heiko Tietze (TDF)

Both paragraph as well as character styles are essential means to format text. Many users struggle with this concept and use direct formatting. Also, we don’t show both at once, and the two style families are not obvious to spot for casual users


Marina Latini, on behalf of the Membership Committee, writes:

On October 18, we officially announced the upcoming election for the next Board of Directors of The Document Foundation, the non-profit entity behind LibreOffice.

As per § 7 II of our statutes (binding German version and non-binding English translartion) the Board’s term lasts two years. The current Board started its duty on February 18, 2020. Therefore, the old Board remains in charge until the end of February 17, 2022, so the new Board will be in charge the day after that, which is February 18, 2022.

That upcoming term will then (regularly) end on February 17, 2024, so the next election of the Board of Directors will take place before.

As per § 6 III, only members of the Board of Trustees of The Document Foundation, as well as current members of any of its bodies, are eligible to be elected into the Board of Directors, and the election is prepared and supervised by the Membership Committee (§ 7 II).

The active electoral right is reserved to those who have been members of the Board of Trustees before this announcement (§ 7 II).

§ 6 III also states that members of the Board of Directors or their deputies may not be members of the Membership Committee and vice versa. This means that current members of the Membership Committee are eligible to be elected, but with the acceptance of their new role they lose their current role in the MC. For clarification, they have to step down from the Membership Committee, with effect no later than to the beginning of the new term of the Board of Directors, the minute before accepting to become a member of the Board of Directors.

There is one more notable limitation: Per § 8 IV of the statutes, a maximum of 1/3 members of the Board of Directors is allowed to work on an employment basis for the same company, organisation, entity or one of its affiliate organisations.

Nomination of candidates fulfilling the above requirements, as well as self nomination is welcome. In total, at least seven Board of Directors members are required, and given there are enough candidates, up to three deputies can be elected (§ 7 II). As deputies are on duty quite often, we encourage many candidates to participate.

Re-election of current members of the Board of Directors is permitted (§ 7 II).

Please send nominations and self-nominations via e-mail to elections@documentfoundation.org (which reaches the Membership Committee in private) and at the same time to board-discuss@documentfoundation.org (which is a public mailing list).

We kindly ask nominees who would like to stand for election to provide a statement of up to 75 words – longer statements will be cut off at the maximum – on their candidacy as continuous text (so no bullet lists or multiple paragraphs). In addition, you have to provide and keep up to date your full name, e-mail address and your corporate affiliation, if any, or state the lack of an affiliation, and please

18 October, 2021


Today we’re talking to Hlompho Mota, who’s working on the Sesotho LibreOffice translation project in Lesotho…

Tell us a bit about yourself!

I am a native of Lesotho, and a dreamer and a person who aspires to make changes. Currently I’m working in a business that serves other businesses in Lesotho to get recognition in the market, and generally grow to become more self-reliant. Other than my business, I do try and dabble in technology and try to understand how it works – and get a sense on how it can be relevant in the area of life that I live in at this moment.

But besides that, I consider myself as lifelong learner and I hope that the learning will continue for the rest of my life. Currently, I’m a self-taught developer trying to participate in as many open-source projects as possible, with the hope of bringing much-needed development to my part of the world.

How did the Sesotho LibreOffice translation project get started?

I’ll refer to a few individuals who I came across, who grew the seeds to contribute to this project.

  • Mamako Mota: My wife, who was somehow able to believe in some of my vision, and hopes that the vision will become reality someday. She was willing to help me get the word out to people.
  • Edwin R Brown: One of the most intelligent people that I had the honour of meeting. He lived by his philosophy of trying to make the world a better place. During the times that he came to Lesotho, we were able to talk about some of the many ways that we looked at the world. However, given that there are some serious changes that need to be brought about with developing the country, I feel that we need some changes in the outlook in my part of the world, and only then will we be able to understand this man’s vision.
  • Vincent D. Warmerdam: A machine learning practitioner and another person I was humbled enough to meet. From how he hold his talks on in the Python community, right down to how he does his work – it all radiates a purpose that has inspired me to have an outlook on what can happen when people have enthusiasm for the work that they do. Besides that, he has shown me some of the ways that vision can be used to develop language, and has shared the tools and resources that he personally developed.
  • Maele Neko: One person who I originally spent time with, where we had hoped to make significant developments in Lesotho and Sesotho. But we were originally came across the challenges that came along with translating, due to the differences in Lesotho and South African dialect. The challenges in life and the discussions I’ve had with him have inspired me to continue. However, he was able to contribute to Sesotho knowledge and language on Twitter.
  • Lastly, Red Hat, the company: I see it



Earlier this year we run a survey on LibreOffice Calc. It was inspired by a similar questionnaire for LibreOffice Draw (see first and second blog post). The Calc survey was used to learn about how Calc is being used, what features are most important to users and where they expect to see the improvements to the software.…

15 October, 2021

  • Mail chew; admin, patch review here & there - encouraging to see more fixes & performance improvements for Online as well as good progress to our next major release.
  • After Italo's keynote announcement of the new LibreOffice Technology marketing plan at the LibreOffice conference, we lost no time integrating this great way to fairly present the goodness of LibreOffice that we depend on to build Collabora Online & Collabora Office mobile into the product. With new links that can take you to our LibreOffice Technology page where we can celebrate the community & credit all the hard work done under the hood here, and of course the logo. Still a work-in-progress, and will start to appear in our products over the next weeks as/when we refresh them, but so far it looks like this for desktop & mobile:
    up-coming COOL About dialog up-coming COOL About dialog
    Thanks to Italo & Mike at TDF for developing the concept, and also to Pedro & Elisa, for their work on the code & logos - we'll be iterating it with them over the next days & weeks.


Here are some more videos from the LibreOffice Conference 2021! Check out the playlist, using the button in the top-right – or scroll down for links to individual videos:

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.

Individual links

Note: many of these are also available on PeerTube, and more will be added…

Stay tuned for more videos from rooms 2 and 3 of the conference!


Want to organise a local (or online) LibreOffice event? Need some merchandise to boost your project or community? Then we can help you! The Document Foundation, the non-profit behind LibreOffice, is backed by contributions from ecosystem members and volunteers, as well as donations from end-users. This helps us to maintain TDF, but we can do a lot more too. And next year, we want to do a lot of projects again!

Each year, we set a budget that LibreOffice projects and communities can use for financial support. Some examples:

  • Booking a location, and travel refunds for a local event (eg a translation sprint)
  • Merchandise for community members, to use at events and conferences
  • Infrastructure to start a new project (or help an existing one)

So if you have some ideas for a meetup, project or activity that could benefit from financial help, let us know! We can also assist you in other ways: our team members are there to help you, and enable you to do exciting and interesting things.

You don’t need to work out all the technical details right now – the main thing is that we have an overview. To help us with planning, we kindly ask you to send your ideas by the end of November, as we try to prepare the 2022 annual budget during December.

You can send your proposal (with estimated costs) to budgets@documentfoundation.org and we’ll take a look. Of course, can’t guarantee that everything will be approved, but we’d love to hear your ideas!

Further reading

14 October, 2021

  • Mail chew; catch up with Miklos, Andras & a great COOL community call - lovely to see some of the hacktober participants showing up and contributing.


In programming, we usually face bugs that we should fix to maintain or improve our software. In order to fix a bug, first we should find the source of the problem, and there are tools like “Automated bibisect” are available to help, specially when the bug is a regression. You probably know what a regression is:

Regression bugs are special kinds of bugs. They describe a feature that was previously working well, but at some point a change in the code has caused it to stop working. They are source of disappointment for the user, but they are easier to fix for the developers compared to other bugs! Why? Because every single change to the LibreOffice code is kept in the source code management system (Git), it is possible to find that which change actually introduced the bug.

From: https://blog.documentfoundation.org/blog/2021/07/29/fixing-an-interoperability-bug-in-libreoffice-missing-lines-from-docx-part-1-3/

But, how to find where (in which commit) the bug has actually introduced? The answer is provided by the Git; the source code management system that most of us use, and is used in LibreOffice development. Git provides a command named bisect.

Using git bisect, you can find the exact commit where the bug was introduced with the minimum number of tries possible using binary search. After invoking git bisect start, you should mark the last bad commit you know using git bisect good, and then the first bad commit you know using git bisect bad. Then you are told what is the number of estimated steps you need to go. You should compile each commit that is checked out, and then test to see if the problem is there.

Binary bibisect

But wait! Isn’t it true that compiling LibreOffice takes a while? Is git bisect for LibreOffice is something usable, in a short period time? The answer is no, but there is a solution called binary bisect or bibisect. Binary builds of all commits within certain periods of time are available as git repositories, and you can do git bisect on these repositories.

You can read more about bibisect here:


First, you have to find a suitable repository. If the bug is reproducible on every platform, you can choose among the repositories according to your OS:

For example, consider tdf#141049. It is about bad rendering of an EMF figure, which is wrongly displayed as blank. It was OK in LibreOffice 6.2, but in newer versions of LibreOffice 6.2, the problem appeared. So, if you are working on Linux, bibisect-linux-64-6.3 would be the right choice, because it provides “libreoffice-6-2-branch-point to libreoffice-6-3-branch-point and then libreoffice-6-3”.

good output in binary bibisect


bad output in binary bibisect


Figure 1: The good, and the bad!

We start by downloading the repository bundle from TDF repo: (Warning: The bundle is ~8GB, and you need more space to extract and work with it)

$ wget --continue https://bibisect.libreoffice.org/linux-64-6.3.git-bundle
$ git clone -o bundle 


Berlin, October 14, 2021 – The Document Foundation announces LibreOffice 7.2.2 Community, the second minor release of the LibreOffice 7.2 family targeted at technology enthusiasts and power users, which is available for download from https://www.libreoffice.org/download/. This version includes 68 bug fixes and improvements to document compatibility.

LibreOffice 7.2.2 Community is also available for Apple Silicon from this link: https://download.documentfoundation.org/libreoffice/stable/7.2.2/mac/aarch64/.

For enterprise-class deployments, TDF strongly recommends the LibreOffice Enterprise family of applications from ecosystem partners, with long-term support options, professional assistance, custom features and Service Level Agreements: https://www.libreoffice.org/download/libreoffice-in-business/.

LibreOffice Community and the LibreOffice Enterprise family of products are based on the LibreOffice Technology platform, the result of years of development efforts with the objective of providing a state of the art office suite not only for the desktop but also for mobile and the cloud.

Availability of LibreOffice 7.2.2 Community

LibreOffice 7.2.2 Community represents the bleeding edge in term of features for open source office suites. For users whose main objective is personal productivity and therefore prefer a release that has undergone more testing and bug fixing over the new features, The Document Foundation provides LibreOffice 7.1.6.

LibreOffice 7.2.2 change log pages are available on TDF’s wiki: https://wiki.documentfoundation.org/Releases/7.2.2/RC1 (changed in RC1) and https://wiki.documentfoundation.org/Releases/7.2.2/RC2 (changed in RC2).

LibreOffice Technology based products for Android and iOS are listed here: https://www.libreoffice.org/download/android-and-ios/, while for App Stores and ChromeOS are listed here: https://www.libreoffice.org/download/libreoffice-from-microsoft-and-mac-app-stores/

LibreOffice individual users are assisted by a global community of volunteers: https://www.libreoffice.org/get-help/community-support/. On the website and the wiki there are guides, manuals, tutorials and HowTos. Donations help us to make all of these resources available.

LibreOffice users are invited to join the community at https://ask.libreoffice.org, where they can get and provide user-to-user support. People willing to contribute their time and professional skills to the project can visit the dedicated website at https://whatcanidoforlibreoffice.org.

LibreOffice users, free software advocates and community members can provide financial support to The Document Foundation with a donation via PayPal, credit card or other tools at https://www.libreoffice.org/donate.

LibreOffice 7.2.2 is built with document conversion libraries from the Document Liberation Project: https://www.documentliberation.org.

13 October, 2021

  • Slept badly, took babes to school in such a hurry I left my wallet & phone at home: discovered this having filled up the car; eventually released to get them from home; ho hum.
  • A day of gut-wrenching TDF administrative angst; draining.


The Document Foundation (TDF) is the charitable entity behind the world’s leading free/libre open source (FLOSS) office suite LibreOffice.

We are looking for an individual or company to implement C++ accessibility tests.

The work has to be developed on LibreOffice master, so that it will be released in the next major version.

The current accessibility tests are rather incomplete and hard to maintain. Additionally, they are written in Java.

The scope of this tender is to convert them into in-process cppunit-based tests and create a solid foundation in both code as well as documentation to facilitate extending the coverage both as part of this tender as well as for follow-up contributions. TDF aims to prepare a good infrastructure and documentation, so that adding further tests is much simpler in the future, even for new kinds of widgets, up to a point where they could be implemented as part of our EasyHacks. The implementation therefore has to be solid and thorough to support future test cases easily.

We recommend the following steps to approach the tender deliverable:

  • assessing the technical requirements (both using the existing tests to convert, plus the various requirements of a11y in general)
  • assessing the current status
  • designing and creating the new required interfaces, or adapting or augmenting existing ones
  • creating helpers to ease writing tests
  • writing some tests to both serve as examples and proof of concept (at least a couple for each key aspect of testing, but exercising the infrastructure to validate it is key to having something that has a chance of withstanding the test of time)
  • extensive documentation on all those, plus how to write tests and such
  • peer review

Therefore, this tender should provide the infrastructure to:

  • Test the interfaces (AT-SPI, UIA, MSAA, etc.) allowing accessibility tools (ATs) such as e.g. screen readers, magnifier glasses, etc. to access the information required to perform their tasks. This requires testing the LibreOffice implementation of the AT interfaces themselves to catch issues at the outer edge. It is crucial because even if all is well working inside LibreOffice itself, but the information is not properly sent to the platform, it still won’t work for users. Also, it probably has to be done for each platform separately (Desktop Linux (AT-SPI2), Windows (UIA, MSAA), macOS etc.) as their APIs are different, even if often similar, and have separate modules in LibreOffice.
  • Test that there is enough information sent through those interfaces and that it is accurate and usable. This could rely on internal unified interfaces to fetch information and interact with the UI, but there still is a fair bit of diversity on what needs to be tested.
  • Test that functionalities are usable with different type of input (e.g. work with the keyboard, as it’s the most common offender). Also this could rely on internal unified interfaces to fetch information and interact with the UI, but there still is a fair bit of diversity on what needs to be tested.

A key

12 October, 2021

  • Caught up with Kendy; more admin, calls. Out for a run with J.

11 October, 2021

  • Mail chew, planning call, worked on projections, and an admin backlog - lots to be done.


If you use Windows 7 and LibreOffice 7.1 doesn't start there, then possibly you have Windows 7 without update. For fixing that issue please install Windows 7 update as it wrote in LibreOffice 7.1 Release Note:

Because of updated Python's change bpo-36085, LibreOffice now requires KB2533623 on Windows 7. The mentioned update is not directly available from Microsoft anymore, but KB3063858 (32-bit / 64-bit) may be used, that superseded the older one (details in tdf#144902).

10 October, 2021

  • All Saints in the morning; Snashells over for lunch. Took N. and M. to StAG in the evening for a fine sermon & youth group afterwards. Out for a drink with J. while waiting for them; home.

09 October, 2021

  • J. out all day, plugged away at tidying the garage; worked on new loft hatch with E. - had fun together playing outside. Bit of work, helped N. with some homework. David over for Ham, Eggs & Chip dinner with J. watched the first of The Hobbit - got PCC minutes into some sort of shape.

08 October, 2021

  • Mail chew, board calls, lots of mail & admin. Dinner. Relaxed by removing some obsolete Poco synchronous socket code and moving LOOLWebSocket into tools/ and out of the way.


(Graphic by Lisa Schmidt, CC-BY-SA 4.0 or later)

The Free Software Foundation Europe is starting a new competition:

Are you up to hacking on a software project of your choice? Do you want to meet like-minded people of your age from around Europe? What about getting the chance to receive one of our cash awards and to travel to Brussels to meet the other winners and great people from the Free Software movement? Then join the YH4F competition! The only conditions for you to join are that you are 14-18 years old and you live in Europe. Start by registering before Sunday, 31 October 2021.

There’ll be an online event on Sunday, 10 October at 17:00 CET – see the Youth Hacking 4 Freedom page for more info, and details on registering.

And there’s more: Thorsten Behrens from The Document Foundation’s Board of Directors is on the jury. So, if you fill the requirements listed above and want to get hacking on a project, join in!

07 October, 2021

  • Sync with Miklos, long legal call, lunch; ESC, catch up with a friend; admin.


General Activities

  1. LibreOffice 7.2.1 was released on September 16
  2. LibreOffice 7.1.6 was released on September 9
  3. Allotropia published a couple of blogposts about their recent work on master documents and ODF 1.3 transition
  4. Alain Romedenne improved the Help content for the ScriptForge library
  5. Adolfo Jayme Barrientos improved the accuracy of some Help texts and made some smaller fixes
  6. Rafael Lima created a guide about Calc macros for formatting cell borders, improved the Help pages for Slide master, Calc AutoCorrect and document encryption.
  7. Steve Fanning improved the help for EUROCONVERT and CONVERT_OOO Calc functions
  8. Olivier Hallot (TDF) added Help pages for Accessibility Check Tool, ProtectFields and ProtectBookmarks, improved the pages for GPG signing and Database Advanced Settings, added examples for using Calc functions in macros and updated many menu item references.
  9. Ilmari Lauhakangas (TDF) replaced Help’s index filtering JS library with a more performant one
  10. Jean-Pierre Ledure worked on the ScriptForge library
  11. Ross Johnson improved paragraph keyboard navigation in Writer and fixed a problem with the grouping of Help index filter results
  12. Juan C. Sanz implemented connecting to a Firebird server (still missing UI)
  13. Natalia Gavrilova made Calc’s focus rectangle use the highlight colour rather than the default font colour
  14. Aleksei Nikiforov (basealt) fixed a Linux crash related to SVG icon themes
  15. Pierre Marty (Linagora) fixed an Impress autolayout issue
  16. Tor Lillqvist (Collabora) worked on the iOS version
  17. Daniel Arato (NISZ) fixed issues with footers in XLSX export and custom shapes in DOCX export
  18. Jim Raykowski completed the work on Navigator focus tracking for all content types while greatly improving its performance and improved the Outline folding feature
  19. Tibor Nagy (NISZ) added support for hyperlinks in images in PPTX import
  20. Vasily Melenchuk (CIB) added line thickness presets for borders and fixed a couple of DOCX import hyperlink issues
  21. Gábor Kelemen (NISZ) fixed a regression in Mail Merge email output ranges
  22. Michael Stahl (allotropia) fixed an issue of spelling dialog in Impress messing up text formatting in shapes and made several crash fixes
  23. Regina Henschel fixed an issue with line object rotation in XLSX export
  24. Samuel Mehrbrodt (allotropia) improved the Calc colour filter feature
  25. Áron Budea (Collabora) fixed a crash caused by a performance improvement
  26. Julien Nabet made emoji toolbar button work on Windows, fixed a regression in Calc’s standard filter with gtk3 UI, improved the behaviour of Base’s Direct SQL dialog and fixed the percentage display in the Check for Updates dialog
  27. Jan-Marek Glogowski (allotropia) made internal directory handling and Windows-specific printing related code more robust
  28. Rizal Muttaqin updated Sukapura and Colibre icon themes
  29. Ilhan Yesil made internal hyperlinks in spreadsheets work in the Android app
  30. Tomaž Vajngerl (Collabora) continued working on the new searching and indexing feature
  31. Hossein Nourikhah (TDF) fixed a font size problem in WMF graphics and added preliminary support for Visual Studio 2022 for building on Windows
  32. László Németh (NISZ) improved the coverage of change tracking, adding paragraph style tracking and making table tracking more

06 October, 2021

  • Mail chew, sales call, admin, partner call.

05 October, 2021

  • Mail chew, met with Kendy, Andras; admin, catch-up with Lubos, patch review; improved trace generation slightly.

04 October, 2021

  • Took babes to school, planning call, churned through admin; lunch, marketing call, partner call, sync with Philippe.

LibreOffice development starts with setting up a development environment. After that, you can do the development in your favorite IDE. In this 80 minutes presentation, you will find everything you need to know to get started with LibreOffice development; from installing dependencies using distribution tools, LODE (LibreOffice Development Environment) or manual setup to compilation itself.
With this tutorial, you can build LibreOffice for yourself. Then we look at some simple tasks from LibreOffice EasyHacks. After that, you can try to get your submission merged into the LibreOffice code by submitting it to gerrit, and doing the fixes requested by the reviewers.

Please accept YouTube cookies to play this 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.

Presentation: Getting Started with LibreOffice Development Hossein Nourikhah

This talk was recorded presented in the LibreOffice Conference 2021 (LibOCon 2021) Slides

LibreOffice Conference 2021

LibreOffice Conference 2021


This is the first post of the LibreOffice Development Blog!

To know more about what is going on in LibreOffice, you can refer to the main Document Foundation blog. Also, if you want to learn more about the LibreOffice design, you can refer to the LibreOffice Design Team blog. And now, we have created a new blog, dedicated to the LibreOffice development!

Important Topics

Here is a good place to get more information about ongoing development efforts. Alongside the Document Foundation Wiki and #libreoffice-dev IRC, we will provide development related information here. We will talk about LibreOffice internals, and modules, how to fix bugs, write tests, and many other things! If you want to start LibreOffice development, this is a good place familiarize yourself with LibreOffice code, tools and developers.

Do you know C++, Java, Python, SQL, or other programming languages? If so, you can find useful information about the latest development related news and other up-to-date information here. Although we emphasize using these programming languages,  you may find some areas that you can help and contribute, even without being an expert in programming.

LibreOffice core, a mix of many modules used in LibreOffice development

LibreOffice core, a mix of many modules used in LibreOffice development

We will focus on LibreOffice core development, which contains many modules that are listed in LibreOffice modules documentation. LibreOffice applications like Writer,  Calc, Impress, Draw, Math and Base that any user interact with will be part of our focus. Additionally, there are modules like VCL (UI toolkit for LibreOffice) that normal users may not fully understand. As a developer, you should know a lot about the LibreOffice internals, so we will discuss these modules.

Additionally, we will also talk about git, Gerrit, Jenkins, Bugzilla, compilers, IDEs and many other tools and techniques.

Above all, you can improve your development skills here, so stay tuned for interesting contents soon. We hope to see your name in the list of LibreOffice developers, here!

Older blog entries ->