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.

15 February, 2019


I’d like to share the results of the quick benchmark tests I’ve done to measure the performance of the R-tree implementation included in the mdds library since 1.4.0.

Brief overview on R-tree

R-tree is a data structure designed for optimal query performance on spatial data. It is especially well suited when you need to store a large number of spatial objects in a single store and need to perform point- or range-based queries. The version of R-tree implemented in mdds is a variant known as R*-tree, which differs from the original R-tree in that it occasionally forces re-insertion of stored objects when inserting a new object would cause the target node to exceed its capacity. The original R-tree would simply split the node unconditionally in such cases. The reason behind R*-tree’s choice of re-insertion is that re-insertion would result in the tree being more balanced than simply splitting the node without re-insertion. The downside of such re-insertion is that it would severely affect the worst case performance of object insertion; however, it is claimed that in most real world use cases, the worst case performance would rarely be hit.

That being said, the insertion performance of R-tree is still not very optimal especially when you need to insert a large number of objects up-front, and unfortunately this is a very common scenario in many applications. To mitigate this, the mdds implementation includes a bulk loader that is suitable for mass-insertion of objects at tree initialization time.

What is measured in this benchmark

What I measured in this benchmark are the following:

  • bulk-loading of objects at tree initialization,
  • the size() method call, and
  • the average query performance.

I have written a specially-crafted benchmark program to measure these three cateroesi, and you can find its source code here. The size() method is included here because in a way it represents the worst case query since what it does is visit every single leaf node in the entire tree and count the number of stored objects.

The mdds implementation of R-tree supports arbitrary dimension sizes, but in this test, the dimension size was set to 2, for storing 2-dimensional objects.

Benchmark test design

Here is how I designed my benchmark tests.

First, I decided to use map data which I obtained from OpenStreetMap (OSM) for regions large enough to contain the number of objects in the millions. Since OSM does not allow you to specify a very large export region from its web interface, I went to the Geofabrik download server to download the region data. For this benchmark test, I used the region data for North Carolina, California, and Japan’s Chubu region. The latitude and longitude were used as the dimensions for the objects.

All data were in the OSM XML format, and I used the XML parser from the orcus project to parse the input data and build the input objects.

Since the map objects are not necessarily of rectangular shape, and not


If you want to migrate content from or to a Plone site it is always the best use of ressources, if you ask volunteers to copy and paste the content items from one environment to another ;-(

But seriously: The Plone community created a tool for such tasks with a funny name: ‘Transmogrifier’. You could find some information on this at https://docs.plone.org/external/collective.transmogrifier/docs/source/index.html#transmogrifier and a training session at https://training.plone.org/5/transmogrifier/.

But it is not that easy and fast to create pipelines and blueprints for a migration yourself. Thus I recommend to ask and pay a Plone professional service to do the migration. It would preserve your nerves and you get results very fast.


Cientos de personas de todo el mundo contribuyen a cada nueva versión de LibreOffice, y hemos entrevistado a muchas de ellas en este blog. Ahora los hemos reunido en un mapa (gracias a OpenStreetMap), para que puedas ver …


全世界有數百個人為每個新版本的 LibreOffice 做出貢獻,我們在官方部落格上採訪了許多人。現在我們將它們收集到地圖上並顯示(感謝開放街圖),這樣您就可以看看誰在您附近,並了解更多訊息!點選圖片以檢視即時地圖:


新聞來源:Find a LibreOffice community member near you!


Hundreds of people around the world contribute to each new version of LibreOffice, and we’ve interviewed many of them on this blog. Now we’ve collected them together on a map (thanks to OpenStreetMap), so you can see who’s near you, and find out more! Click the image to see the live map:

Don’t see anyone near you? Help us to create a new native language community in your country! (Or if you’re already active in the project and would like to be interviewed, just drop us a line.)

14 February, 2019

[en] Andreas Mantke: TDF Dashboard

20:40 UTC


I tried to have a look onto the TDF dashboard at https://dashboard.documentfoundation.org using an Internet Explorer 11, but with no success. The website didn’t render. I got only a retry of rendering actions. According to the browser stats at least 5.26 % of the internet user are not able to view the site (https://www.stetic.com/de/market-share/browser/).

And in addition for those who prefer webservices with ‘mobile first’ implementation: it’s not for you ;-(

The site doesn’t render proper on smaller mobile devices. It’s not usable on such devices.

[en] Michael Meeks: 2019-02-14 Thursday

19:30 UTC

  • Particularly gratified to get a very touching birthday-card this morning: it's normally me that does that sort of thing.
  • Valentine's day release of Collabora Online 4.0 with an associated CODE update too. Tons of rather excellent work from the team there - its a privilege to be able work with them, and to fund almost all of that at Collabora. Then again - if you'd like to help out with both the funding, and directing the next round of feature work, we'd really appreciate you as a partner or customer.

LibreOffice 社群的其中一個目標是為所有人提供強大的生產力套裝軟體。無償釋出軟體是其中一部份,但自由軟體與價格並沒有關係。其是為使用者提供他們使用軟體與電腦的基本自由,將控制權交還給他們。

舉例來說,LibreOffice 的原始碼,也就是程式背後人類可讀的「食譜」,可供所有人檢視、研究並修改。您可以下載原始碼,看看它做了哪些事,根據您的需求進行更改,然後將其重新轉換為電腦可執行的版本。已經有數百人這麼做過了,為 LibreOffice 做出重要的修改與更新。然後您就可以自由地與其他使用者分享修改過的版本。

所以我們不一樣。但 LibreOffice 只是自由軟體的其中一個例子。還有其他許多眾所週知的軟體,例如 Firefox 網路瀏覽器與 GNU/Linux 作業系統。歐洲自由軟體基金會正在協助宣傳自由,並為此舉辦了許多活動

所以我們在這一天支援他們,您也可以幫助他們!在社群媒體上使用 #ilovefs 主題標籤,說說為什麼自由軟體對你來說很重要,讓我們協助人們重新掌控他們的數位生活。

新聞來源:Let’s celebrate “I love Free Software Day”!


Uno de nuestros objetivos en la comunidad de LibreOffice es hacer que poderosas herramientas de productividad estén  al alcance de todos. Lanzar el software de manera libre es una parte importante de eso, pero el “software libre” se trata de …


One of our goals in the LibreOffice community is to make powerful productivity tools available to everyone. Releasing the software for free is an important part of that, but “free software” is about more than just the price. It’s about giving users fundamental freedoms in how they use their software and computers – giving control back to them.

For instance, the source code for LibreOffice – that is, the human-readable “recipe” behind the program – is available for everyone to see, study and modify. You can download this code, see what it does, change it for your needs, and then turn it back into an executable version for your computer. Many hundreds of people have done this already, contributing back important changes and updates to LibreOffice. And then you’re free to share the changes with other users.

In contrast, most other office suites don’t give users these freedoms; they are “closed”, so users can’t look under the hood, can’t study how they work, can’t make changes, and can’t share the software. Users become restricted and trapped, controlled by and locked into specific software from a specific company. That’s the very opposite of freedom!

So we’re different. But LibreOffice is just one example of free software. There are many other well-known programs, such as the Firefox web browser, and GNU/Linux operating system. The Free Software Foundation Europe is helping to spread the word about freedom, and has a number of campaigns to this end.

So we’re happy to support them on this day – and you can help them too! Use the hashtag #ilovefs on social media, talk about why free software is important to you, and let’s help people to get back control over their digital lives.

13 February, 2019

[en] Michael Meeks: 2019-02-13 Wednesday

21:00 UTC

  • Customer call, sales & marketing call.
  • Up late applying my limited caligraphic skills to J's Valentine's card: what a lady !


I read a time ago about the myth of an expensive LibreOffice extensions and templates website. I investigated about this and had a look at the real numbers (they are public available on the wiki page: https://wiki.documentfoundation.org/TDF/Ledgers). I found some expenses only in two fiscal period: 2017 and 2018. TDF spent in 2017 6399.44 Euro and in 2018 642.60 Euro. The money was predominantly spent for content migration and an improved server environment. It included also an individual training for the TDF infrastructure team.

The most work on the website was done by volunteer work within some support from the Plone open source community. All in all TDF spent 7042.04 Euro for running the site for about seven and a half years, thus about 938.39 Euro per year. Seemed a very expensive tool in comparison to the financial and personal ressources used for running other TDF tools 😉

LibreOffice 大會2019年將於9月11日(週三)至9月13日(週五)於西班牙的阿爾梅里亞市舉辦。


至於社交晚宴與 Hackfest 之類的附加活動(這是 LibreOffice 大會的傳統)則尚未決定。

如果您想定期更新 LibOCon 阿爾梅里亞的資訊,您可以訂閱 Telegram 上的 LibOCon 討論群組或是 LibOCon 的公告頻道。

新聞來源:Announcing the dates of LibOCon Almeria


Por Italo Vignoli

La Conferencia LibreOffice, o LibOCon, en su edición 2019, se llevará a cabo en la ciudad de Almería, España, del 11 al 13 de septiembre.

El jueves, 10 de septiembre, se celebrarán las reuniones comunitarias habituales, para …


LibreOffice Conference 2019 will be hosted by the Spanish city of Almeria during the month of September, from September 11 (Wednesday) to September 13 (Friday).

On Tuesday, September 10, there will be the usual meetings of the community, to discuss topics of general interest for native language projects, such as localization, documentation, quality assurance, design and marketing.

Collateral events such as the social dinner and the hackfest, which are a tradition of the LibreOffice Schedule, have not yet been scheduled.

If you want to be regularly updated about LibOCon Almeria you can subscribe to the LibOCon Discussions Telegram group or the LibOCon Announcements Telegram channel.

12 February, 2019

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

21:00 UTC

  • Isolated my weird Galaxy S4 hanging / power-off state to it being inside the bumper. Wondered if its too tight fitting and presses power/volume buttons constantly; cut these out - and bingo, a stable phone. Nice.
  • Built ESC agenda, prodded applications, ferried babes and friends to different places. Learned more WordPress than I was hoping to until late.


A new edition of FOSDEM (Free and Open source Software Developers‘ European Meeting) just ended. Our CIB LibreOffice team this year was represented by Thorsten Behrens, Michael Stahl and Marina Latini. The event is held annually during the first weekend of February, at the „Université Libre de Bruxelles„. For our team, attending FOSDEM means to be … CIB visiting FOSDEM 2019 weiterlesen

Der Beitrag CIB visiting FOSDEM 2019 erschien zuerst auf CIB events.

透過 LibreOffice 開發者的協助來強化您的 C++ 技能!我們會定期舉辦專注於特定主題的工作坊,並有即時的 IRC 會議。接下來的這一個的主題是遞迴。請先看這份簡報:

然後在 UTC 時間2月14日晚上7點(亦即台灣時間2月15日凌晨3點)透過我們在 Freenode 上的 #libreoffice-dev 頻道進行討論。您可以詢問經驗老道的 LibreOffice 開發者問題,然後學習更多關於 C++ 的知識。回頭見!

新聞來源:Next C++ workshop: Recursion (14 February at 19:00 UTC)


With the release of 6.2 I read a lot of comments on the different threads. Several issues are listed. One was that Ribbons waste vertical space.

Tabbed toolbar waste vertical space

With default settings the standard toolbar need 110 px vertical space (menubar + 2 toolbar height), tabbed toolbar need 100 px and groupedbar compact 72 px. So the default toolbar need most vertical space.


Difference in height (with GTK3 backend)

  • 110 px for standard toolbar need most vertical space cause the default icon size is 24px (large icons) and you have two toolbars and the menubar
  • 100 px for tabbed toolbar cause the default icon size is 16px (small) and you don’t need an menubar.
  • 72 px for groupedbar compact need the same vertical space than single toolbar.

Yes MSO Ribbons need a lot of vertical space, which is an issue on laptops. Therefore you can show the tabbs only. In LibreOffice we have different UI’s for different workflows, but also for different screen’s. For example on your 32 inch office screen you’d like to work with standard toolbar but on mobile you prefer tabbed compact toolbar (which will be released with 6.3).

On windows the difference between LibreOffice tabbed toolbare and MS Office ribbons is

94 px vs. 110 px

If you like my work, become a downloads_wordmark_white_on_coral2x.jpg


Improve your C++ skills with the help of LibreOffice developers! We’re running regular workshops which focus on a specific topic, and are accompanied by a real-time IRC meeting. For the next one, the topics is recursion. Start by watching this presentation:

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.

Then join us on 14 February, 2019 at 19:00 UTC for a discussion via our #libreoffice-dev IRC channel on Freenode. You can ask experienced LibreOffice developers questions, and learn more about the language. See you then!

11 February, 2019


Nel 1799, la massa di un litro d’acqua è stata usata per definire il chilo, e nel 1889 è stato creato un cilindro di metallo con la stessa identica massa come oggetto di riferimento. In questi anni, la natura fisica del metallo ha portato questi cilindri a non essere più una rappresentazione fedele di quella […]

[en] Michael Meeks: 2019-02-11 Monday

21:00 UTC

  • H. to Hills Road; missed it - calls with team; sync with Amir.
  • Worked through CVs at some length: we're trying to hire - for Libre/Collabora Office related bits: a Javascript Dev, a QA / DevOps / Build eng, and a Technical Writer. Added a number of more open-source experience style criteria to try to somewhat reduce the flow of applicants: encouraging.
  • H. returned early and worked, played some 'go' with her till she beat me.


With LibreOffice 6.2 now available, we return to our regular chats with LibreOffice community members! Today we’re talking to Khaled Hosny, who is working on the software’s font handling and user interface…

To start with, tell us a bit about yourself!

I’m based in Cairo, Egypt. I use IRC but not very actively – my nick is KhaledHosny. I’m a bit active on Twitter as well. I’m also on GitHub (which, after all, is a social network of sorts): https://github.com/khaledhosny.

Outside of my work on LibreOffice, I’m also a localizer and typeface designer, both in a professional capacity and as a hobby. I’m also an avid reader, and an amateur calligrapher and artist.

Do you work for a LibreOffice-related company or just contribute in your spare time?

I contribute in my spare time mostly, but some of my work was sponsored by The Document Foundation.

How did you get involved with LibreOffice?

I was trying to fix some bugs with Arabic text layout in OpenOffice.org (the predecessor to LibreOffice) on Linux. It wasn’t the most pleasant experience, to say the least, and I never got to finish the fix I was working on. So, when I became aware of LibreOffice in early 2011, I switched immediately and was able to finish and submit my first patch, which got reviewed and accepted. I have been contributing to LibreOffice intermittently since then.

What areas of the project do you normally work on? Anything else you want to tackle?

I’m mostly interested in areas of text layout and font handling, especially for Arabic and other writing systems that require advanced text layout. I also sometimes work on UI issues affecting right-to-left writing systems, as well as layout of mathematical equations.

What was your initial experience of contributing to LibreOffice like?

That was over eight years ago, so my memory is fading away, but I remember that it was much better than working on OpenOffice.org, and the build system (even then) was much more pleasant to use. Also, I think my first patch was accepted without much friction and delay, which is not my experience with many other open source projects.

What does LibreOffice need most right now?

In my humble opinion, I think the project needs a clearer vision and development agenda. Right now things seem to be moving organically without much coordination, and every one is working on whatever interests them. I understand that such development organisation is not easy or even feasible in an open source development model and might not even be desirable, but maybe The Document Foundation should take a more active role in steering LibreOffice development.

Thanks to Khaled for his time, and contributions to LibreOffice! Our community would benefit from more help in translating the website and user interface into Arabic, so if you’re interested, start here!

10 February, 2019

[en] Michael Meeks: 2019-02-10 Sunday

21:00 UTC

  • All Saints, confirmation service: got confirmed by the Bishop; interesting. A fine shared lunch afterwards, nice biography of Ryle from Mary.
  • Home, relaxed, read some Vinge to the family; movie, bed.

09 February, 2019

[en] Michael Meeks: 2019-02-09 Saturday

21:00 UTC

  • Family Birthday visits B&A, A&L, S&C,A&J all over for a fine lunch at Prezzo. Anne brought her car for us. Slugged in the evening.


Pure Elixir database driver for Firebird https://github.com/nakagami/firebirdex


Firebird 4.0 is using Ubuntu xenial on travis . https://travis-ci.org/FirebirdSQL/firebird .travis.yml looks a lot simpler after this change.   ps: Here is official Travis CI announcement: Ubuntu Xenial 16.04 is available


Firebird 4.0 implemented Built-in logical replication is now merged Here is the pull request https://github.com/FirebirdSQL/firebird/pull/182 We know that is a long standing feature request Wow! @firebirdsql team implemented a feature that I asked 10+ years ago!https://t.co/tRrg9YvkWW"Built-in logical replication"Thank you guys.— Daniele Teti (@danieleteti) January 25, 2019

08 February, 2019

[en] Michael Meeks: 2019-02-08 Friday

21:00 UTC

  • Admin catch-up day, calls variously.

Older blog entries ->