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.

16 November, 2018


Call the Logo functions before their definitions using the Logo syntax: In this dragon curve drawing program, write „y n-1” simply without parentheses, instead of its Python version „y(n-1)” – one of the LibreLogo improvements of the upcoming LibreOffice 6.2

With the support of the FSF.hu Foundation, I have successfully implemented some long-planned LibreLogo improvements. This has made LibreLogo more reliable in LibreOffice, helping more and more people to discover the beauty of programming with LibreLogo, like German schoolchildren or Italian kindergarten teachers. My developments:

  • Adding LibreOffice unit tests for LibreLogo program execution and compiling. Based on this automated testing, Red Hat developer Stephan Bergmann has already found an interesting regex change in Python 3.7 (LibreLogo was written in Python programming language), and he has fixed LibreLogo, too.
  • Compiling Logo expressions to Python, i.e. adding parentheses at the right places uses a parser instead of the former heuristic method. Thus, you can write arbitrarily complex expressions, either in combination with Python lists, and calling own Logo functions with more than one argument without parentheses. Note: In LibreLogo expressions you can use Logo and Python syntaxes at one time. To avoid conflict, now parenthesis directly following the function name, eg. in sin(x) * 2” denotes Python syntax, (meaning 2·sin(x)), while the space separated version, eg. sin (x) * 2”, denotes Logo syntax (meaning “sin(2·x)”, as the simpler Logo expression “sin x * 2”).
  • Function definitions and Logo-like function calls can be in any order, resulting for example completely Logo-like dragon curve drawing Logo program (see on the attached screenshot).
  • Fix of the “magic wand” icon enables a two-sided view, keeping also the debug function “jump text cursor to the wrong LibreLogo program line at compiling”.
  • We can write ASCII and typographical apostrophes in character strings.
  • The running program stops immediately by clicking the Cancel button on the dialog window of the commands INPUT and PRINT (no need to wait starting a new loop in cycles).
  • One of the goals of the planned future LibreLogo developments is to provide a more detailed documentation of LibreLogo’s Python source code. As you can see, I have already tried to do this in the current patches.

These developments will appear soon in the next preliminary version of LibreOffice 6.2.

15 November, 2018


what is new:

  • Elementary icon theme update
  • Tabbed Toolbar for writer, calc, impress and draw (Optional)

LibreOffice 6.2 Elementary


LibreOffice 6.2 is being developed by our worldwide community, and is due to be released in early February, 2019 – see the release notes describing the new features here. LibreOffice 6.2 will include a new (optional!) user interface design called the Notebookbarsee here for some screenshots. You can help us to test it, and make it super reliable!

After the first Bug Hunting Session for LibreOffice 6.2, which was held on October 22nd, we’re glad to announce the Second Bug Hunting Session on November 19th.

In order to find, report and triage bugs, the tests during the Second Bug Hunting Session will be performed on the first Beta version of LibreOffice 6.2, which will be available on the pre-releases server on the day of the event. Builds will be available for Linux (DEB and RPM), macOS and Windows, and can be run in parallel with the production version – so you can test without affecting your existing stable installation.

Mentors will be available on November 19th 2018, from 7 AM UTC to 9PM UTC for questions or help in the IRC channel: #libreoffice-qa (connect via webchat) and its Telegram bridge. Of course, hunting bugs will be possible also on other days, as the builds of this particular Beta release (LibreOffice 6.2.0 Beta1) will be available until mid December.

During the day there will be two dedicated sessions, one about the new KDE5 Integration between 11AM UTC and 13PM UTC and the other about the tabbed notebookbar from 15PM UTC to 17PM UTC, it is not experimental any more.

What has happened since the first Bug Hunting Session?

Since LibreOffice 6.2 Alpha 1 was released, 169 bugs have been reported against Alpha 1 by more than 40 people, of which 70 have been already closed, either by fixing them (30), as duplicates (27) or as invalid/notabug (13).

35 bugs have been reported for the ongoing KDE5 integration as a consequence of the dedicated session conducted during the first Bug Hunting Session.

Many thanks to the top five bug reporters: Telesto, Vera Blagoveschenskaya, Xisco Faulí, Andreas Kainz and Regina Henschel.


Can we say Elasticsearch is great for localized search? Let’s do a check. It is an engine that gives you most of the standard search features out of the box. There are many ways to look for an optimal window to implement fast and indexed document search, scoring docs based on certain formulas, autocomplete search, context suggestion, localized text comparison based on analyzers and so on!

I am here to discuss about implementing a localized search for remote languages, regardless of being supported by analyzers in ES or not and how to get good results (for starters), if not the best.

I will use Node.js and ES as the technical stack. Let’s define some standard types for our index schema. I have three cases considered here:

  1. English Analyzer
  2. Hindi Analyzer (Comes tagged with ES. See: Language Analyzers)
  3. Standard Analyzer (Use if your language does not have an inbuilt analyzer in ES)

We need to define the schema in a way to support all the standard types. I have chosen three languages to display search. English, Hindi ( Indian native ), and Telugu (Regional South Indian Language with no default analyzer in ES).

We have Telugu under standard analyzer as it is based on the Unicode Text Segmentation algorithm, as specified in Unicode Standard Annex #29 and works well for most languages. We can also use Simple Analyzer as it is a modified form of Standard Analyzer and divides text on characters which are not a letter.

Now, we have a schema defined. Next, you create an index with the schema and populate the index with related documents. I am not sharing actual documents which were used for my testing, but one can find text resources online to populate an index. For Node.js, one can use ES client for Node.js, or an easier way would be ES rest API.

There is a whole variety of search one can perform on a document having the above schema for all fields with custom analyzers. [ Full-Text Queries in ES ]

I was able to get great search results for English and Hindi, and search results for Telugu were not much below the bar. The ease with which one can create an almost real-time search engine is something unbelievable. I have not gone into many technical details of analyzers and how they function by combining the appropriate character filterstokenizer, and token filters. It is expected for a standard analyzer to be just acceptable with the results, of course, it is only for starters. An Elasticsearch user must implement full-fledged custom analyzer for a regional language to get more accurate results. Moreover, ES provides with few add-ons for Asian languages such as Korean, Chinese, etc.

So, we can conclude that Elasticsearch is indeed great to boost your product’s localization and accessibility in small time cost and high return value.

14 November, 2018


After releasing Hunspell 1.7 with several improvements, including the fast and better spelling suggestion, I publish the extended version of my presentation at LiboCon, Tirana: LibreOffice Language Technology – News & Best practices. I suggest checking its content especially for members of native language groups. I have listed several ideas, examples and code pointers to improve the support of your language in LibreOffice, helping your LibreOffice users.


Ich hatte an der HTW Dresden die Gelegenheit, einen Vortrag zum Thema “The Document Foundation als Beispiel für Governance in Open-Source-Projekten” zu halten.

Die Folien stehen hier zum Download zur Verfügung (PDF-Datei, 1,9 MB).

Als ergänzende Lektüre gibt’s noch die Folien zu den “Zehn Zutaten für eine zufriedene Community“.

The Document Foundation als Beispiel für Governance in Open-Source-Projekten (Vortrag an der HTW Dresden 2018)

13 November, 2018


Want to help spread the word about LibreOffice, free software and open standards? Attend a local computing event, and tell people about it! Stanislav Horáček writes about some recent events in the Czech Republic…

With our LibreOffice booth, Zdeněk Crhonek and I attended the two biggest Czech FOSS events, LinuxDays in Prague and OpenAlt in Brno. We would like to share some of what we experienced:

– as usual, generally positive feedback from users, interest in new features and what is going on

– many questions about the status of LibreOffice vs. OpenOffice, the role of The Document Foundation etc.

– low awareness about LibreOffice Online; people were surprised that it is ready and that people are using it; some in interest in how to install it, others sharing experience that its deployment is too complicated

– more advanced users aren’t using LibreOffice so much, replacing it by simpler things like Markdown docs

– it’s nice that videos from the marketing team are available (about LibreOffice, join the community, new features…), showing them on the screen attracted visitors to the booth; but we’re missing a video about LibreOffice online (maybe an idea for the marketing team)

– discussion with someone from the National Technical Library in Prague (enthusiastic about FOSS, migrated client computers to Linux and LibreOffice, encouraging us to spread the word about it) and a representative of an organization trying to coordinate using FOSS in Czech municipalities (two towns running LibreOffice, with the intention to pay for some bug fixing)

– a meeting with the Slovak community (Miloš Šrámek and Andrej Kapuš) in Brno

– a meeting with the Czech localization community (Mozilla, Linux distributions), discussing mainly the possibility of a new Czech dictionary

– and a discussion with a marketing specialist who suggested ways to simplify the LibreOffice webpage (there are too many confusing subpages).

So in summary, we informed Czech FOSS people that there is active development of LibreOffice and that there is even some Czech community – thanks to organizers for the opportunity and to TDF for the support!

Thanks to Stanislav and Zdeněk for their help! Find out more: here’s the Czech LibreOffice website, Czech Ask site (for user support), and Czech mailing lists.

12 November, 2018

  • Mail; admin; lunch, status report, sync. with Andras.


Our community is working on LibreOffice 6.2, which is due to be released in early February 2019! While developers are adding new features, other community members are helping to test them, in the form of Bug Hunting Sessions. You can learn more about these on our Quality Assurance blog, and in the meantime, here’s a quick report from an in-person session in Ankara, Turkey…

Here’s what Muhammet Kara, who helped to organise the event, had to say:

Eight people (including one remotely from Istanbul) participated in our live session in Ankara, and we tested LibreOffice 6.2 Alpha on Linux, Windows and macOS.

We always held our past live sessions in Pardus’ venue. This time we decided to make a change, and I think it brought good results. All people in the session, except me, were new faces, from different schools and workplaces.

We started with self-introductions, and chatted for a short while, to get to know each other. Then I went through our bug reporting and QA process briefly, and introduced the participants to our Bugzilla installation.

We identified several bugs, and created bug reports for them. Some of our new community members are following up the bug reports, and some have even started contributing to localization).

We also created a Telegram channel to communicate during the event, and later on as well. Overall, I think it was a productive, and fun event.

So thanks to Muhammet and the awesome Turkish LibreOffice community for their help! LibreOffice 6.2 is shaping up to be an excellent release…

11 November, 2018

  • All Saints, played bass; pizza lunch, dropped H. and M. off to the Rememberance parade & service with Scouts. Watched Man in the High Castle, and a large nativity silhouette with J. Worked on mending J's old Galaxy S3 for M. in the evening - struggled to find compatible PIT files that would not be rejected; grim. Rather unclear why Android's Download mode doesn't let you read the flash contents smoothly.


Standard toolbar will be standard, there is NO change planned!

Click to view slideshow.

But that doesn’t mean that you are not allowed to play with different UI designes.

Check out LibreOffice master: Download LibreOffice Master

If you like my work, become a downloads_wordmark_white_on_coral2x.jpg

10 November, 2018


Tabbed Toolbar Table

Edit your Tables wherever you want


Tabbed Toolbar Text

LibreOffice individual apps universal useful.

  • Off to Sue & Clive's - worked in the car. Saw their new porch, enjoyed a fine lunch, out for a walk - saw some deer in the fields. Adrian. Georgina & Isabelle arrived - enjoyed fireworks together. Drove home - bed extremely late.

09 November, 2018

  • Mail chew; admin, board call during lunch; interview, marketing call, interview. LOTR in the evening.

08 November, 2018

  • Mail chew, lots of it. Customer call, TDF marketing, sales & marketing, ESC calls. Two partner calls. Back to some quick patch review. Some hacking in the evening on urgent code bits.


Started with unsubscribing from mailinglists after a long day of skil enhencement.


One week ago we started a new Month of LibreOffice, celebrating contributions all across the project. And over 100 sticker packs have already been awarded!

Not got one yet? Then join in – here are some ways to get involved and claim your stickers:

07 November, 2018

  • Guilty hacking and bug-fixing through the day, poked at a perennial annoyance of not complaining when people send SSL/TLS frames to a plain HTTP port in online, timeouts on slow document conversions and more - fun. Band practice in the evening. Worked excessively late tackling some bugs.

06 November, 2018


In addition to finish rework in tabbed toolbar, context menu I also update the toolbar’s to have them more consistent between the different apps and within the app, so the UI jumping was reduced as much as possible.


Check out LibreOffice master: Download LibreOffice Master

If you like my work, become a downloads_wordmark_white_on_coral2x.jpg


Context Menu rework is in master, check out what’s new.

The biggest change is consistency. The sort arrangement is in all context menues the same and it doesn’t matter if you use right click on graphic in writer, calc, draw, impress or any other awesome LibreOffice module.


In addition to make LibreOffice consistent you now can add styles with right click like here in writer


Don’t forget to report bugs cause I change around 80 % of the context menu xml files.

Check out LibreOffice master: Download LibreOffice Master

If you like my work, become a downloads_wordmark_white_on_coral2x.jpg

  • Mail chew, built ESC agenda/stats. Some patch review, admin, filed bugs.



  • Text autofit confusion solved by Maxim Monastirsky.
  • Several NotebookBar issues turned out to be gone after Andreas Kainz re-tested them.
  • Jim Raykowski kept improving the Navigator and Sidebar with many commits.
  • Brian Fraser continued to work on improvements to reordering of Impress animations.
  • Justin Luth committed dozen of OOXML fixes.
  • Mark Hung committed dozen of Impress fixes.
  • Dozens of small fixes as a response to a PVS-Studio report. (Mike Kaganski (Collabora), Caolán McNamara (Red Hat), Xisco Fauli (TDF))
  • Numerous performance issues reported by Telesto were triaged, some already fixed.
  • Katarina Behrens (CIB) added drag&drop support to KDE5.
  • Dozens of KDE5 backend issues in the 6.2 alpha1 were reported and triaged during the Bug Hunting Session.
  • Usama and Buovjaga split an unusually complex report about Calc hyperlinks into multiple reports.
  • Eike Rathke (Red Hat) implemented REGEX function
  • Mert added language support to Android Viewer.
  • Roman Kuznetsov re-tested many old bugs, some of which got closed as RESOLVED WORKSFORME.
  • Zdeněk Crhonek added some new Uitests
  • Muhammet Kara modernized and optimized Personas
  • Rizal Muttaqin continues working on elementary icons

Reported Bugs

845 bugs have been reported by 408 people.

Top 10 Reporters

  1. Telesto ( 67 )
  2. Xisco Faulí ( 33 )
  3. Daniel ( 32 )
  4. Vera ( 23 )
  5. Thomas Lendo ( 21 )
  6. Aron Budea ( 19 )
  7. Michael Weghorn ( 18 )
  8. 和尚蟹 ( 15 )
  9. andreas_k ( 15 )
  10. Heiko Tietze ( 14 )

Triaged Bugs

861 bugs have been triaged by 81 people.

Top 10 Triagers

  1. Xisco Faulí ( 205 )
  2. Buovjaga ( 141 )
  3. Dieter Praas ( 38 )
  4. Heiko Tietze ( 38 )
  5. Alex Thurgood ( 37 )
  6. Oliver Brinzing ( 33 )
  7. raal ( 29 )
  8. V Stuart Foote ( 28 )
  9. m.a.riosv ( 22 )
  10. Mike Kaganski ( 22 )

Fixed Bugs

170 bugs have been fixed by 39 people.

Top 10 Fixers

  1. Caolán McNamara ( 31 )
  2. Eike Rathke ( 12 )
  3. andreas kainz ( 11 )
  4. Jim Raykowski ( 8 )
  5. Julien Nabet ( 8 )
  6. heiko tietze ( 8 )
  7. Miklos Vajna ( 8 )
  8. Muhammet Kara ( 7 )
  9. Mike Kaganski ( 7 )
  10. Jan-Marek Glogowski ( 6 )

List of critical bugs fixed

  1. 120706 Crash in: SbxArray::Count() when trying to call a WinAPI function ( Thanks to Mike Kaganski )
  2. 120387 EDITING Copy Chart Axis Title causes LibreOffice Calc crash ( Thanks to Jan-Marek Glogowski )
  3. 120452 kde5: Impress crashes when opening slide containing video ( Thanks to Katarina Behrens )
  4. 120261 gtk3_kde5: Crash with file dialog when Java extension “WollMux” is installed ( Thanks to Michael Weghorn )
  5. 120782 Crash when dragging column from datasource to spreadsheet ( Thanks to Julien Nabet )
  6. 120291 Attaching a connector makes draw Draw busy-loop and crash ( Thanks to Noel Grandin )
  7. 120528 Crash when closing context menu in Data Provider dialog ( Thanks to Mike Kaganski )
  8. 120785 CRASH: LibreOffice can be closed while Slide Design is open ( Thanks to Caolán McNamara )
  9. 120451 kde5: Impress presentation mode crashes in single-monitor setup ( Thanks to Katarina Behrens )
  10. 120334 Crash when closing dialog Position and Size ( Thanks to Caolán McNamara )
  11. 120794 CRASH while selecting a drawing line ( Thanks to Noel Grandin )
  12. 120731 Crash cuilo!makeAutoCorrEdit when open character dialog with large amount of text selected ( Thanks to Caolán McNamara )
  13. 120862 Crash selecting a bullets or number item with double click ( Thanks to Caolán McNamara )
  14. 120803 kde5

05 November, 2018

  • Mail chew; drove into Cambridge to swap hardware around & see Dorée home for a late lunch. Mail chew. Physics lesson for H. and Katie in the evening kindly provided by David.


I recently dived into the SmartArt support of LibreOffice, which is the component responsible for displaying complex diagrams from PPTX, especially in case only document model and the layout constraints are given, not a pre-rendered result.

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

The problem

There are several ones. :-) If you are just interested in high quality viewing of PPTX files, then your problem started with PowerPoint 2007 not writing a pre-rendered drawingML markup of the diagram to the files, only PowerPoint 2010 started behaving like this. Additionally, if a diagram is not edited, then re-saving with PowerPoint 2010 doesn’t seem to generate the drawingML markup, either. This means that data + constraints cases are quite frequent even today.

Also, one day Impress should be able to actually edit these SmartArts as well, so having the knowledge how to lay out SmartArt (even if it’s import-time-only at the moment) is a good thing.

Results so far

I always write cppunit tests when I work on filter code (in this case OOXML), so far all fixes were visible in just two test files: smartart-vertial-box-list.pptx and vertical-bracket-list.pptx.

Here is how the baseline, the current and the reference rendering of these test documents look like:

smartart-vertial-box-list.pptx, baseline

smartart-vertial-box-list.pptx, current

smartart-vertial-box-list.pptx, reference

vertical-bracket-list.pptx, baseline

vertical-bracket-list.pptx, current

vertical-bracket-list.pptx, reference

In terms of code commits, the fixes are split into several ones:

Clearly the results are not perfect yet, but in both cases nothing was visible, and now all text is readable, so we’re moving in the right direction!

All this is available in master (towards LibreOffice 6.2), so you can grab a daily build and try it out right now. :-)


Berlin, November 5, 2018 – The Document Foundation announces the release of LibreOffice 6.0.7 and LibreOffice 6.1.3, which improve the quality and stability of previous releases, and integrate a security patch.

All LibreOffice users are therefore strongly recommended to update to the new versions:

  • Power users, early adopters and technology enthusiasts should update from LibreOffice 6.1.2 to LibreOffice 6.1.3, which represents the bleeding edge in term of features for open source office suites;
  • All other individual users and organizations of any size should update from any previous version of LibreOffice to LibreOffice 6.0.7, which is more mature and as such targeted at production environments and enterprise-class deployments.

Organizations should source LibreOffice 6.0.7 from one of the companies providing a Long Term Supported version of the suite, for additional value-added services which make the software better suited to enterprise deployments, thanks to professional support (the companies are all members of TDF’s Advisory Board, and are listed here: https://www.documentfoundation.org/governance/advisory-board/). When it is sourced from The Document Foundation, LibreOffice is supported by volunteers.

Also, value-added services for migrations and trainings, to support enterprise-class deployments in large organizations, should be sourced from certified professionals (a list is available here: https://www.libreoffice.org/get-help/professional-support/).

LibreOffice is deployed by large organizations in every continent. A list of some large or significant migrations announced in the media is available on the TDF wiki: https://wiki.documentfoundation.org/LibreOffice_Migrations.

LibreOffice 6.0.7 bug and regression fixes are described here: https://wiki.documentfoundation.org/Releases/6.0.7/RC1 (fixed in RC1), https://wiki.documentfoundation.org/Releases/6.0.7/RC2 (fixed in RC2) and https://wiki.documentfoundation.org/Releases/6.0.7/RC3 (fixed in RC3), while LibreOffice 6.1.3 bug and regression fixes are described here: https://wiki.documentfoundation.org/Releases/6.1.3/RC1 (fixed in RC1) and https://wiki.documentfoundation.org/Releases/6.1.3/RC2 (fixed in RC2).

Download LibreOffice

LibreOffice 6.0.7 and LibreOffice 6.1.3 are immediately available from the following link: https://www.libreoffice.org/download/. Builds of the LibreOffice Online source code can be downloaded as Docker images: https://hub.docker.com/r/libreoffice/online/.

LibreOffice Online is fundamentally a server service, and should be installed and configured by adding cloud storage and an SSL certificate. It might be considered an enabling technology for the cloud services offered by ISPs or the private cloud of enterprises and large organizations.

LibreOffice users, free software advocates and community members can support The Document Foundation with a donation at https://www.libreoffice.org/donate. Donations help TDF to maintain its infrastructure, share knowledge, and fund the presence of volunteers at events, where they can meet with other free software advocates.

LibreOffice 6.0.7 and LibreOffice 6.1.3 are built with document conversion libraries developed and maintained by the Document Liberation Project (DLP): https://www.documentliberation.org. Several of


The icon theme Karasa Jaga has been introduced in release 6.1. It was originally created for Sundara OS and is heavily inspired (and derived) from the discontinued Oxygen icon. The icon designer Rizal Muttaqin seeks now for your input how to continue his work:

The question is:

(Firefox users: please disable content blocking)

Here are examples of how it looks:

The post Quick poll on the design of the Karasa Jaga icon theme appeared first on LibreOffice Design Team.

04 November, 2018


Hey everybody,

long time I didn’t reported any progress, simply because I hadn’t that much spare time to work on this any topic. So basically the Munich Hackatron last weekend was exactly the “weekend blocker” I needed to get back into this topic. At that weekend I finally was able to import most edits from the old Turkish “eskiwiki” (OpenOffice.org.tr)-wiki. I’m still cleaning up the imported edits and I still do even find missing pages as you can see at the Special:Log page. With all the amount of spam in ESKIWIKI it is really not that easy to find pages with real content. I should have found every page, but as you can see in the ImportLog that I found another few pages this weekend.

Now my focus is at the image cleanup and preparing all pages to move over to TDFwiki. Sadly all this work is very time consuming so it lasts very long.

I do have a special request to the Turkish speaking community members:

Can you “merge” the content of the old OOo Writer page and the newer one. The other component pages do have the same problem. A list of the old OOo pages are linked in this old revision. Otherwise the links on the old OOo pages are unlinked and very hard to find.

Fun fact: After 9½ years I fixed a bug and embed the correct image at the page “SIKLIK”, see this revision. The problem was that both images were first uploaded and then a simple copy and past error followed when creating the page. I found this fact as I simply uploaded all images from the eskiwiki and now checking all unused images and wanted images (and either try to fix it, or delete them again for not uploaded the old stuff to TDFwiki later). Sadly a few images are borked (1x1px) and aren’t even archived at archive.org – so even borked ages ago.

Let’s see how much spare time I find in the next weeks to finish the rest.

  • Played at family service; M. reading, H. piano & organ, N. games & violin. Lots of people for shared lunch - fun. Back with Mary for some more slugging, organ practice, sheet cutting & sewing machine dis-assembly with J. relaxed variously. Stories, bed.

03 November, 2018

  • Cooked breakfast, H. out singing, played Paper.io with the babes. Put up fixings in M's room, nice. Caulked plasterwork - still not dry, and considered the kitchen mess.

Older blog entries ->