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.

26 December, 2018


The LibreOffice Quality Assurance ( QA ) Team is happy to announce LibreOffice 6.2 RC1 is ready for testing!

LibreOffice 6.2 will be released as final at the beginning of February, 2019, being LibreOffice 6.2 RC1 the third pre-release since the development of version 6.2 started in mid May, 2018. See the release plan. Check the release notes to find the new features included in this version of LibreOffice.

LibreOffice 6.2 RC1 can be downloaded from here, and it’s available for Linux, MacOS and Windows.

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 ) so it can get fixed before LibreOffice 6.2 final is released.

For help, you can contact us directly in our IRC channel.

Happy testing!!

The post LibreOffice 6.2 RC1 is ready for testing appeared first on LibreOffice QA Blog.

19 December, 2018


LibreOffice has the capability to add references to a document and finally a bibliographical index, which is essential for scientific publications. The style of references depend on the journal and the discipline. So it is common to just add numbers in square brackets like [1] in engineering whereas humanities show name and year like (author, year).…

The post Save the bibliography? appeared first on LibreOffice Design Team.

17 December, 2018


Am 15.12.2018 wurde die neueste Special Edition des Linux Pro Magazine mit dem Thema #LibreOffice veröffentlicht. CIB ist als kompetenter Partner und langjähriger Supporter von LibreOffice natürlich in der Ausgabe vertreten und gleich mit zwei Anzeigen dabei. On 15.12.2018 the latest special edition of the Linux Pro Magazine concerning #LibreOffice has been published.  As a … LibreOffice powered by CIB @ Linux Pro Magazine weiterlesen

Der Beitrag LibreOffice powered by CIB @ Linux Pro Magazine erschien zuerst auf CIB events.

16 December, 2018


As you may know, I was participating in this year Gerrit User Summit, 15th-16th November 2018 in Palo Alto, CA.

I gave two talks: Bazel build gerrit: New and Noteworthy about optimizing Gerrit Build with Bazel and Gerrit Change Workflows with details about interesting multi stop journey that replaced somewhat confusing Draft change/Draft patchset workflows with streamlined Work-In-Progress workflow.

There were plenty of great talks, including Gerrit Analytics, Kubernetes, Multi-Site and Mulit-Master deployments and details about new and shiny Gerrit 3.0 that is going to be tentatively released in Q2 2019.

During the developer hackathon, that took place before the user conference, Gerrit 2.16 release was conducted. Major new feature is: new UI has reached parity with the old GWT UI and therefore old GWT UI is deprecated in 2.16 and in fact was already removed on master and will not be included any more in Gerrit 3.0. Another major feature is Git protocol version 2.0 is fully supported through HTTP and SSH layers.

This release also included small improvements, like simplified debugging capability for UI, SSH and GIT requests. Moreover, submit rules can now be written in Java language as a Gerrit plugin, in addition to Prolog rules.

I would like to thank GerritForge Ltd. for sponsoring travel cost for my participation.

2018 has been a very special year – we were celebrating the 10th anniversary of Gerrit, on 14th November, 2018. 10 years ago Shawn Pierce created a first commit in Gerrit repository. It is such a terrible loss for the whole open source community in general and for Gerrit ecosystem in particular that long-time Git contributor and founder of the Gerrit Code Review project, passed away in January this year.

14 December, 2018


Last year we revised the workflow to insert special characters. Based on a design proposal the dialog was reimplemented in a Google Summer of Code project by Akshay Deep. The new dialog allows to easily browse through the list and to search for glyphs contained in the selected font.…

The post Special Characters: The Final Touch appeared first on LibreOffice Design Team.

12 December, 2018


What i love in Ubuntu : woobly windows via compiz https://code.mradford.com/post/the-ubuntu-compiz-desktop/

10 December, 2018


After a great LibreOffice Conference, followed by the LibreOffice Hackfest held at modulE and the SFSCon in Bolzano sponsored by CIB, the LibreOffice community met again in Sanremo on December 1st, for the annual conference of the Italian supporters and contributors, members of the LibreItalia association. Unfortunately CIB wasn´t able to attend the event, but thanks … LibreItalia Conference 2018 weiterlesen

Der Beitrag LibreItalia Conference 2018 erschien zuerst auf CIB events.

04 December, 2018


General Activities

  • LibreOffice 6.2 beta1 was released
  • On November 19, the bug hunting session for LibreOffice 6.2 beta1 took place
  • Tabbed notebookbar moved out of experimental
  • Miklos Vajna (Collabora) worked on improving Smartart
  • In the FR community Pierre Choffardet has been very active these last days, helped by other members of FR QA team, he narrowed several bugs like: bug 121128, bug 121116, bug 121117, bug 121118, bug 121119, bug 121120
  • Németh László worked on improving LibreLogo
  • Telesto tested LibreOffice 6.2 on MacOSX in deep
  • Vera Blagoveschenskaya tested KDE5
  • Markus Mohrhard fixed many chart bugs
  • Mike Kaganski (Collabora) implemented a proper console mode on Windows.
  • Liad Skiva found some crashes in the properties dialog
  • Many bugs found by NISZ LibreOffice Team regarding interoperability
  • Franklin Weng, Cheng-Chia Tseng and Jeff Huang hosted a QA event at the University of Cheng-Kung, Taiwan, where 70 students attended.
  • Bartosz Kosiorek improved EMF+ support with several patches
  • Mark Hung improved slideshow rendering with several patches
  • Jens Carl moved dozens of Java tests to C++
  • Zdeněk Crhonek created two dozen UI tests
  • Tomaž Vajngerl ( Collabora ) worked on Document encription
  • Rizal Muttaqin worked on Elementary icons
  • Jim Raykowski collaborated with Andreas Kainz to make Notebookbars accessible
  • Daniel Silva rebase his work from the GSOC on the new print dialog into master
  • Michael Stahl rebase his work on redlinehide into master
  • Aleksei Nikiforov fixed some KDE5 issues

Reported Bugs

741 bugs have been reported by 390 people.

Top 10 Reporters

  1. NISZ LibreOffice Team ( 45 )
  2. Telesto ( 41 )
  3. Xisco Faulí ( 27 )
  4. Vera Blagoveschenskaya ( 20 )
  5. 和尚蟹 ( 12 )
  6. robert ( 11 )
  7. Roman Kuznetsov ( 11 )
  8. Gabor Kelemen ( 11 )
  9. Pedro ( 11 )
  10. Regina Henschel ( 11 )

Triaged Bugs

813 bugs have been triaged by 86 people.

Top 10 Triagers

  1. Xisco Faulí ( 286 )
  2. Dieter Praas ( 51 )
  3. Heiko Tietze ( 40 )
  4. Oliver Brinzing ( 34 )
  5. Timur ( 31 )
  6. V Stuart Foote ( 29 )
  7. raal ( 27 )
  8. Alex Thurgood ( 27 )
  9. Buovjaga ( 26 )
  10. Aron Budea ( 15 )

Fixed Bugs

176 bugs have been fixed by 52 people.

Top 10 Fixers

  1. Caolán McNamara ( 38 )
  2. Markus Mohrhard ( 12 )
  3. Mike Kaganski ( 9 )
  4. Eike Rathke ( 8 )
  5. Noel Grandin ( 7 )
  6. andreas kainz ( 7 )
  7. Regina Henschel ( 6 )
  8. Xisco Fauli ( 6 )
  9. Miklos Vajna ( 5 )
  10. Samuel Mehrbrodt ( 5 )

List of critical bugs fixed

  1. 121143 LibreOffice sends “your system has crashed” message if “Close Application” event is defined ( Thanks to Mike Kaganski )
  2. 121538 choosing additional formatting in dialog insert fields cause crash (gen/gtk) ( Thanks to Caolán McNamara )
  3. 121540 CRASH deleting a form from form navigator ( Thanks to Noel Grandin )
  4. 121607 Crash when closing a document (being the only active) while being prompted for data source password ( Thanks to Caolán McNamara )
  5. 121417 KDE5: Recent Documents -> Clear list leads to crash ( Thanks to Aleksei Nikiforov )
  6. 121290 Crash, if press F4 for a selected callout ( Thanks to Caolán McNamara )
  7. 121591 CRASH: Print Preview fails if cursor inside Floating frame ( Thanks to Mike Kaganski )
  8. 121743 CRASH closing LibreOffice with Parameter dialog open ( Thanks to Caolán McNamara )
  9. 121432 Pressing twice on the “Help” button causes LibreOffice application to crash when


I recently dived into the SmartArt support of LibreOffice, which is the component responsible for displaying complex diagrams from PPTX. I focused especially on the case when 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.

Accent Process

In this post I would like to present the progress regarding the Accent Process preset, available in PowerPoint — which is used in many documents.

This exposed several shortcomings of the current diagram layout we have in LibreOffice:

  • Values are not read from constraints (there was a reason for this, they can be complex, given that depending on the context, the unit is points or millimeters and the unit is always implicit).

  • ZOrder offsets were ignored.

  • Linear algorithm did not take size from constraints when it came to recursing into child algorithms.

  • Data point assumed that all text for it is a single "run" (i.e. either all text is bold or nothing, not half of it).

  • followSib axis was not implemented for forEach, so when you have arrow shapes between objects, we created N arrows, not N - 1 ones.

  • Connectors were created as invisible shapes and had the wrong width/height aspect.

With all these fixed, we reach a much better state for handling accent process.

Results so far

smartart-accent-process.pptx is what I used for testing of this work.

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

smartart-accent-process.pptx, baseline

smartart-accent-process.pptx, current

smartart-accent-process.pptx, reference

This is not not perfect yet, but it’s clearly a large improvement, all text is now readable from the diagram!

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

21 November, 2018


LibreOffice has always supported usage of command line switches that allow operations like conversion of documents to different file types, or batch-printing. Using LibreOffice CLI in various scripts is a very common scenario.

But until now, it had somewhat suboptimal support for this on Windows. The main executable module – soffice.bin – being a GUI subsystem application, it could not properly output its messages to the calling console, as well as return error codes to check ERRORLEVEL for success. The hacks used to redirect the output of the GUI application to the calling console were unreliable and didn’t work at all on some supported versions of Windows. Sometimes one could not even see why the entered command line was rejected as invalid.

I have just pushed a commit that changes the situation. Now LibreOffice has proper console mode on Windows. soffice.bin is now built for console subsystem, which allows using it in abovementioned scenarios, having the stdout and stderr output, as well as return code, properly sent to console (or redirected using normal means); in debug builds, the debug output is also visible on the console. To allow comfortable usage, a new console launcher executable is introduced, soffice.com, in LibreOffice installation’s program/ folder, alongside with familiar soffice.exe, which is retained for all GUI uses, as before. This allows to continue using command lines like
"c:\Program Files\LibreOffice\program\soffice" --convert-to odt file.doc
from cmd.exe command-line interpreter, without specifying the executable extension, and have the soffice.com launched to have proper console operation (subject to value of PATHEXT environment variable). The command properly “owns” the console (does not return to command prompt) until soffice finishes.

The change will be available in LibreOffice 6.3 scheduled for Summer 2019 (if testing does not reveal a major problem which would require to revert this). I hope this will make use of LibreOffice CLI more comfortable for Windows users, on par with other platforms. If you find any problems with the solution, please report bugs to our bug tracker. Early testing using daily builds is much appreciated!

20 November, 2018


Anyone who follows my LibreOffice work knows that I spent quite some time on the automated testing frameworks for LibreOffice. As part of this blog I want to use the LibreOffice 6.2 branch-off as a chance to look at current automated testing related statistics. All of the numbers were generated on 2018-11-1, so might already be slightly outdated.

We currently have 4804 different C++ based test cases in 357 different test suites and contain a total of 26215 test asserts. The largest test suite is ucalc (a test suite in Calc that links statically against the main calc library) with nearly 25000 lines of code in several files and 291 test cases.

In addition to our normal C++ based tests, we also have 409 UI tests in 39 test suites. As part of the UI tests we have another 2282 assert statements. A special thanks here to Zdeněk Crhonek who has written 154 commits adding UI tests in 2018. Everyone else together wrote about 45 patches this year touching the UI testing code.

Less well known test concepts in LibreOffice include our callgrind based performance testing (26 out-of-tree test cases and 25 in-tree test cases) and the automatic import and export crash testing with nearly 100000 documents. We managed to run the automatic import and export crash testing, which also generates more than 200000 documents for the export tests, a total of 73 times this year.

Another interesting statistics of this year is that the bug report with the most linked commits is related to the automated testing. As part of the Bug tdf#45904 several brave LibreOffice developers, including Jens Carl and Rahul Gurung, have converted more than 40000 lines of old Java based API tests to C++. In total they have produced more than 60 commits that have been linked to the bug report in 2018 alone and 132 since 2016.

I’m most likely forgetting some additional test frameworks but wanted to give a short overview of all the work that goes into LibreOffice’s automated testing framework. If you are interested in joining the effort please talk to us on #libreoffice-dev or mail the LibreOffice developer mailing list at libreoffice@lists.freedesktop.org. We have tasks in the automated testing area in C++, python, java and some web related tasks.



The LibreOffice Quality Assurance ( QA ) Team is happy to announce LibreOffice 6.2 Beta1 is ready for testing!

LibreOffice 6.2 will be released as final at the beginning of February, 2019, being LibreOffice 6.2 Beta1 the second pre-release since the development of version 6.2 started in mid May, 2018. See the release plan. Since LibreOffice Alpha 1, 1252 commits have been submitted to the code repository and more than 178 bugs have been set to FIXED in Bugzilla. Check the release notes to find the new features included in this version of LibreOffice.

LibreOffice 6.2 Beta1 can be downloaded from here, and it’s available for Linux, MacOS and Windows. Besides, it can be installed along with your actual installation.

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 ) so it can get fixed before LibreOffice 6.2 final is released.

For help, you can contact us directly in our IRC channel.

Happy testing!!

The post LibreOffice 6.2 Beta1 ready for testing appeared first on LibreOffice QA Blog.

19 November, 2018


On Friday 16th we attended the SFScon, the most important and biggest Free Software conference in Italy, and a well known event all over Europe, too. We are proud to have sponsored this enlightening conference where experts from all over the world were discussing about free and open source software, community and innovative solutions for … Free Software Conference – SFScon weiterlesen

Der Beitrag Free Software Conference – SFScon erschien zuerst auf CIB events.

18 November, 2018


It was all started with the 16px blue folder that had a striking color at the time. I was really uncomfortable seeing an icon which had unmatched color choice with the larger one. It was looked so so out of place.

You Are So Out of Place, Boy

That is part of the elementary icon theme in LibreOffice that placed in LIBREOFFICE-INST-DIR/share/config/images_elementary.zip.
As soon as I unpacked the compressed file, my response at that time was "Wow, it looks like this icon theme needs more touch"

Maybe some of you know that in the latest fresh release (6.1), I managed to send my work to upstream: Karasa Jaga icon theme. That was my first real "visible" contribution so far. Unfortunately, Karasa Jaga has not been being default in any desktop environment nor operating system. So when I saw elementary, which is
now the default theme of the GNOME desktop environment and its derivatives, I suddenly felt called back to plunge and immediately give more attention to this another colored icon theme.

elementary icon theme has indeed been "completed" last year, but I think there are many things that turn out to be many home works. Here some issues I've found:

1. Blurry Appearance, The Pixels Did Not Fit Right

Blurred icons are usually due to drawing process that did not follow the guide lines that are commonly available in drawing applications such as Inkscape. This causes the icon to look less clear and certainly not satisfying.

Let me show you some of the opaque icons I've found and also the work that has been done:

Blurred icons
2. Childish Appearance
Looked so unprofessional, such as being drawn in a hurry situation, especially the smallest size of 16 px, they did not meet the official HIG from elementary own.

Childish, yeaa
3. Different Appearance Between 16px*16px and 24px*24px Version
This is quite funny, but still annoying
Inconsistencies Here and There

3. Missing Many Fall Backed uno: Commands
So by default if a theme lack of an icon it will be eventually fall back to default - defined another icon theme. 
Fall Backed Menu Items

4. Missing Many Non cmd Components
This part argumentatively is a hard part since I have to check every menu or dialog available which took icons from non cmd directory (cmd directory is  just contains .uno command so they are easier to be tracked). Here I show you direct comparisons:

Writer's Sidebar Navigator

Impress' Display Mode

View Datasource and Exchange Database

Impress' Sidebar Navigator

Draw's Sidebar Shapes
5. Lack Of Support for Extra Large Size
I should say this frankly. My first focus was adding extra large (32px*32px) after seeing that blue out of place icons, and this one so satisfying me.


There are also a number of additional new icons that did not exist in the previous version, especially to support the Tabbed Notebookbar interface and some context menus. Here are some of

17 November, 2018





Reference: https://gerrit.libreoffice.org/#/c/63315/


Now I would like to show you my two months work against LibreOffice elementary icon theme. This one just show you standard toolbar comparison between 6.1 version and 6.2 beta. To switch icon theme, select Tools > Options > View > Icon Style
To test latest work, you can download LibreOffice 6.2 beta : https://dev-builds.libreoffice.org/daily/master/

LibreOffice Writer

6.2 Beta

LibreOffice Calc

6.2 Beta

LibreOffice Impress
6.2 Beta

LibreOffice Draw
6.2 Beta

LibreOffice Base

6.2 Beta caption

16 November, 2018


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


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)

11 November, 2018


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.

08 November, 2018


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

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



  • 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


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. :-)


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.

<- Current blog entries