The Document Foundation Planet


October 07, 2015

Kohei Yoshida

mdds 1.0.0

A new version of mdds is out, and this time, we’ve decided to bump up the version to 1.0.0. As always, you can download it from the project’s main page.

Here is the highlight of this release.

First off, C++11 is now a hard requirement starting with this release. It’s been four years since the C++11 standard was finalized. It’s about time we made this a new baseline.

Secondly, we now have an official API documentation. It’s programatically generated from the source code documentation via Doxygen, Sphinx and Breathe. Huge thanks to the contributors of the aforementioned projects. You guys make publishing API documentation such a breathe (no pun intended).

This release has finally dropped mixed_type_matrix which has been deprecated for quite some time now in favor of multi_type_matrix.

The multi_type_vector data structure has received some performance optimization thanks to patches from William Bonnet.

Aside from that, there is one important bug fix in sorted_string_map, to fix false positives due to incorrect key matching.

API versioning

One thing I need to note with this release is the introduction of API versioning. Starting with this release, we’ll use API versions to flag any API-incompatible releases. Going forward, anytime we introduce an API-incompatible change, we’ll use the version of that release as the new API version. The API version will only contain major and minor components i.e. API versions can be 1.0, 1.2, 2.1 etc. but never 1.0.6, for instance. That also implies that we will never introduce API-incompatible changes in the micro releases.

The API version will be a part of the package name. For example, this release will have a package name of mdds-1.0 so that, when using tools like pkg-config to query for compiler/linker flags, you’ll need to query for mdds-1.0 instead of simply mdds. The package name will stay that way until we have another release with an API-incompatible change.

by Kohei Yoshida at October 07, 2015 01:59 AM

Italo Vignoli

LibreOffice & El Capitan


LibreOffice 5 works without any noticeable issue with the new Apple OS X El Capitan (Version 10.11). So far, I have used all four major applications – Writer, Calc, Impress and Draw – with a large number of different documents, and they have been working properly. I have also read and written several documents in the non standard Microsoft Office file formats (mostly DOCX and PPTX) and they have not created any issue to the people who have received the documents.

LibreOffice provides a solution where Microsoft Office 2016 fails, as there are several reports of hangs and crashes.

by italovignoli at October 07, 2015 12:44 AM

October 06, 2015

Official TDF Blog

The Document Foundation welcomes RusBITech in the project Advisory Board

The Document Foundation (TDF) announces that RusBITech, a large Russian software development company focusing on open source software, has joined the Advisory Board.

RusBITech is a Research and Production Association (RPA) which develops and supports the Astra Linux distribution based on Debian GNU/Linux, targeted to the Russian public administration. LibreOffice is included in Astra Linux, and is one of the main applications for the users of the operating system.

Astra Linux, which is licensed according to the principles of the GPL license, has been officially certified by the Russian Ministry of Defense, the Federal Service for Technical and Export Control and the Federal Security Service.

By joining TDF Advisory Board, RusBITech wants to leverage the LibreOffice ecosystem to provide a better productivity experience to the user of Astra Linux. The desktop operating system supports a tablet computer mode, and most users are interested in running LibreOffice on a tablet.

RusBITech is also planning to provide a support service for LibreOffice in Russia, to complement the Astra Linux Special Edition (commercial), which is used in many Russian state-related organizations.

by Italo Vignoli at October 06, 2015 04:05 PM

October 05, 2015

Jan Holešovský

Aarhus: Presentations & the Table Styles in Writer

It is already a week since I am back from the great LibreOffice Conference in Aarhus. I enjoyed it a lot - talked to lots of people [eg. met Heiko for the first time in person - after having spent quite some time with him over hangouts :-)], listened to many nice presentations, gave my talks, and - even managed to find some time for the late night's hacking. Oh, and the train there and back was a good choice too - I have travelled with Stanislav who's translating & managing the Czech translations; and on the way back we have also met Jos.

Before I tell you about the Table Styles in Writer, the feature I was working on, let me share the slides from my presentations. First of all, I presented work of my GSoC students, Nathan Yee and Krisztian Pinter, during the GSoC panel:

Click the slide to see the presentation.
Then I talked about the recent achievements & plans of the LibreOffice Design team:
Click the slide to see the presentation.
Then on Thursday, I talked about what we have done in VCL, our graphics toolkit, to be able to make our rendering double-buffered:
Click the slide to see the presentation.


Table Styles in Writer

And now - the Table Styles in Writer. It is a feature that we have missed for a long time. In LibreOffice, we have the Table -> AutoFormat..., but applies the formatting only once; after you modify the table (like insert rows / columns) later, you basically destroy the look of the table.

During summer 2013, Alex Ivan was working on implementing the table styles as GSoC project. I rebased his work to the current master, and made it to work again. Unfortunately, the approach there turned out to be very aggressive - the changes first destroyed the Table AutoFormat feature, and then started building the Table Styles. This means that we could merge that only after we have the import and export for Table Styles - but the GSoC work did not get that far.

I reconsidered the approach, and tried to find a way that implements the core of the Table Styles functionality without destroying the Table AutoFormat - and it worked :-)

I have pushed the results to master. Now, when you apply the Table AutoFormat in Writer, it behaves as a Table Style: When you insert more rows/columns, they still keep the correct formatting, similarly deleting, or splitting tables keeps the table formatted. Direct formatting is applied over the style too, and you can clear it via "Clear Direct Formatting".


Further work

Loading/saving is not implemented though, so once you save the table with Table Style, it turns into a "normal" AutoFormat - the next time you open it, you see the formatting, but it is "static", ie. works as before the Table Styles work.

I hope to get the load/save done before 5.1; and there's also lots to be improved in the UI of Table Styles - but I believe the current state is already an improvement, and a step in the right direction.

by Jan Holesovsky ( at October 05, 2015 09:47 AM

October 04, 2015

>Szymon Kłos

LibreOffice conference – Aarhus 2015

This year I attended at my first conference - The LibreOffice Conference, which took place from the 23rd to the 25th of September in Aarhus, Denmark.

Aarhus is a beautiful city with a lot of impressive buildings. One of them is a modern building used as a public library, called Dokk1. In this place we spent most of our time.

I really enjoyed the conference. It was very good opportunity to listen interesting talks and meet other open source enthusiasts.

Whole conference was very good organized. Except presentations we could take part in a hackfest, community dinners and visit Aarhus University. Especially I liked tasty food :)

Thanks to The Document Foundation and sponsors for this conference. It was fantastic experience. See you next year in Brno!

by Szymon Kłos ( at October 04, 2015 03:45 PM

October 01, 2015

Official TDF Blog

Tender for design and implementation of “All about LibreOffice” community and developer dashboard (#201510-01)

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

design and implement an “All about LibreOffice” community and developer dashboard

to start work as soon as possible.

TDF wants to invest in a webpage showing latest activity, summaries and trends of the LibreOffice project in all areas, like development, QA, user-to-user support and other key areas of the project. The developed webpage should be easily extensible for developers providing scripts analysing current and historic data from various project infrastructure.

Further details on this project can be found at

TDF is looking for an individual or company to, as a turnkey project, design and implement the following:

  1. a dashboard that displays the latest events and actions happening in the project, with a maximum latency of 2 hours
    1. on a webpage
    2. in RSS and Atom feeds for displaying in feedreaders and embedding into websites
    3. both including displaying of graphics, images and charts
    4. an integration into our Silverstripe content management system, for easy implementation of the generated content into our website
  2. extensive support of individual filters, queries, tags and summaries, to modify the output
  3. a feature to have fixed subpages for incorporation and reference in our existing websites
  4. support for filtering if an event creates or resolves an action item for a specific subproject
    Samples based on Bugzilla: regression filed would be qa-task-created (need confirmation/triage), regression triaged/moved to NEW (qa-task-resolved, dev-task-created), regression fixed (dev-task-resolved).
  5. collection of historic data for displaying and analysis
  6. a statistics feature, to output contributor numbers and top contributors like on our credits page (
  7. implementation of an easy theming features for designers to improve the visual layout of the dashboard
  8. adding data to the dashboard should be possible by providing a RSS or Atom newsfeed, created by common *nix script languages (Python, Perl, Ruby, PHO); optionally also support for C/C++/Haskell/Ocaml
  9. for #8, integration with our existing Gerrit instance for authentication
  10. proper documentation, including a working Salt recipe for deployment and installation of the dashboard on Debian 8-based machines
  11. regular blogposts about the project progress, and a final blog posts that advertises the dashboard to the LibreOffice community and invite contributions

The developer area should be a git repository containing scripts (Python/Perl/Ruby/PHP/etc.) generating RSS and Atom feeds. These will be triggered to be run in regular intervals of approximately five minutes and their output will be published for the database cronjob to pick up. The same is true for scripts creating images, graphics and charts. Ideally, the developer area regularly polls the hosted repository on e.g. gerrit for updates, thus adding new events/actions/summaries to the database (and thus the websites which present a view on the database). Additionally there should be an directory that can be read from the scripts, but isn’t part of the repository to store auth tokens/credentials for scripts to access their source systems (e.g. bugzilla, askbot, git, etc.) if needed.

Required Skills

Programming Languages and Framework

  • Frameworks, languages and tools used should be popular and widely used to allow the result to be community maintained and sustained after initial development. Extensibility should allow developers to refine the dashboard without deep insight in the used frameworks and tools.
  • We exclusively use free, libre and open source (FLOSS) software for development whereever possible and the resulting work must be licensed under MPLv2.
  • For the creation of the frontend (website, feeds) a lean web framework like Django or CodeIgniter should be used. The use of a full-blown CMS should be avoided. Both the language and the framework should have a reasonable wide community supporting it (e.g. Top10 at and more popular that most of the competition at The Backend DBMS is recommended to be PostgreSQL.
  • Website and feeds should be delivered by a small application based on a lean web framework presenting the data out of the backend database. The application layer should really be thin — it should essentially only present the database as as good-looking webpage and well-formed feeds. A cronjob running on this machine will fetch a set of RSS/Atom feeds and import them into the database.

Other Skills

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

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

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

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

TDF is looking forward to receiving your applications, your financial expectations (name the final price for the turnkey project), and the earliest date of your availability, via e-mail to Florian Effenberger at no later than November 2, 2015. You can encrypt your message via PGP/GnuPG.

Applicants who have not received feedback by December 2, 2015 should consider that their application, after careful review, was not accepted.

by Florian Effenberger at October 01, 2015 02:56 PM

September 30, 2015

Caolán McNamara

impress save background image

Impress has a "Set Background Image" option in its slide context menu for a while. For 5.1 I've added a matching "Save Background Image" to save the current background image to file.

by Caolán McNamara ( at September 30, 2015 04:32 PM

Florian Effenberger

Open Source für Stiftungen

Stiftungen und freie Softwareprojekte haben sehr viel gemeinsam, denn beide versuchen, mit großem Engagement und einer starken Gemeinschaft ein gemeinsames Ziel zu erreichen. Was liegt also näher, als einmal die Nutzbarkeit von Open-Source-Programmen für die Stiftungsarbeit zu beleuchten?

Zusammen mit Rechtsanwalt Michael Schinagl aus Berlin habe ich in der aktuellen Ausgabe 03-2015 des Magazins Magazins „StiftungsWelt“ des Bundesverbandes Deutscher Stiftungen einen Artikel geschrieben, in dem wir die Hintergründe zu freier Software beleuchten und konkrete Tipps für die Nutzung im Stiftungsalltag geben.

Der Bundesverband stellt den Lesern dieses Blogs den Artikel freundlicherweise kostenfrei zum Download zur Verfügung (PDF-Datei, 345 KB). Die Rechte am Artikel liegen beim Verlag.

Zudem ist das gedruckte Heft direkt im Shop des Stiftungsverbands erhältlich.

by Florian Effenberger at September 30, 2015 07:46 AM

September 29, 2015

Florian Effenberger

LibreOffice Conference 2015

„On Monday after the conference we will all miss each other,“ my colleague Leif said to me, who was one of this year’s organizers. Seems he was right.

LibreOffice Conference 2015 is over, and it was an amazing and incredible event. With approximately 150 participants from more than 30 countries, we not only had a conference, but a true family meeting. It was so exciting catching up with colleagues whom we haven’t seen for months, meeting new friends, and sharing good times and joyful moments in beautiful Aarhus in Denmark, in an exciting venue called Dokk1, which supported our creative gathering with its fresh, inspiring and open architecture – a perfect match for the LibreOffice community.

„As every year, we intend this conference to be the best ever“, Leif said during his opening speech, and he didn’t promise too much. Contributors and users from around the globe gathered for one week to catch up with the latest developments on LibreOffice, the OpenDocument format and free software in general. TDF staff spent a day together to discuss upcoming projects, the Board of Directors met to discuss strategic milestones, and our native-language community exchanged thoughts and ideas on the translation process and various other aspects of their work. What makes me particularly proud is that many of them took a long travel from other continents, most of them for the first time, to meet with us in person.

The conference was surrounded by several events, like a community dinner, a conference meeting, a hackfest and a party, organized by the volunteers from the Danish community.

As a lucky coincidence, the conference took place around a very special day: the fifth anniversary of LibreOffice, which was born on September 28, 2010. The conference crowd took the opportunity and celebrated this milestone with a big cake, looking back at all the amazing things we have achieved in such a short glimpse of time, and looking forward with pleasure to all the exciting projects that are yet to come.

<figure class="wp-caption aligncenter" id="attachment_88" style="width: 300px;">Happy Birthday, LibreOffice!<figcaption class="wp-caption-text">Happy Birthday, LibreOffice!</figcaption></figure>

During this week, while I met fantastic new friends, experienced Denmark’s beauty and had an exciting time, I have to admit that I did not learn that much of the Danish language. There’s one word, however, that I did learn, and I can’t say it often enough to those who have given us this amazing event, a present we won’t forget – and this word is called: Tak.

Tak (thank you), to all the organizers, tak to all the speakers, tak to all the contributors, tak to all the enthusiastic supporters, tak to a wonderful and amazing community, and – last but not least – tak to all the sponsors who made this event an unforgettable week. It’s incredible to be a part of this wonderful family, having friends around the world, working together jointly on our goals, and achieving something everyone can benefit from.

In the closing session of this year’s event, we could announce that the next LibreOffice Conference will take place in September 2016 in Brno, Czech Republic, and I for sure already count the days until we will all meet again.


by Florian Effenberger at September 29, 2015 08:27 PM

Mihai Varga

LibreOffice Online - LibreOffice Conference 2015

The annual LibreOffice Conference took place in Aarhus, Denmark and it was hosted at Dokk1, which is a wonderful example of modern architecture in a northern European city.

Since my last post about it, LibreOffice Online has developed quite a lot.
Here are some of the most important features that we've added:

Editing - the document now has a blinking cursor and it can handle text input
Selections - the user can now select and copy text from the document

Images and shapes can be resized and moved around

We now have an advanced toolbar that enhances the editing experience.

Presentations have slides previews.

LibreOffice Online is part of Collabora ColudSuite, more information can be found at where you can also request access to a demo.

An demo that was presented at the conference:

<script> // 2. This code loads the IFrame Player API code asynchronously. var tag = document.createElement('script'); tag.src = ""; var firstScriptTag = document.getElementsByTagName('script')[0]; firstScriptTag.parentNode.insertBefore(tag, firstScriptTag); // 3. This function creates an <iframe> (and YouTube player) // after the API code downloads. var player; function onYouTubeIframeAPIReady() { player = new YT.Player('player', { height: '390', width: '640', videoId: 'L2bAFkD2QkU', events: { 'onReady': onPlayerReady } }); } // 4. The API will call this function when the video player is ready. function onPlayerReady(event) { player.setPlaybackQuality('hd720'); } </script>

And finally here you can find my presentation slides 

<iframe allowfullscreen="" frameborder="0" height="420" marginheight="0" marginwidth="0" scrolling="no" src="" style="border-width: 1px; border: 1px solid #CCC; margin-bottom: 5px; max-width: 100%;" width="510"> </iframe>

by Mihai Varga ( at September 29, 2015 06:40 PM

September 28, 2015

Eike Rathke

Five years of LibreOffice – Happy Birthday, LibreOffice!

The huge success of LibreOffice, not only as a software package but as a Free Software project as a whole, can only be measured and expressed by giving credit to all who are involved and all that has been done. So thank you, all contributors to the project! To celebrate, The Document Foundation has compiled a history "leaflet" (well, it's more like a midsize tree ;-) of blog posts, articles, release notes, work that has been done etceteraetcetera. It is available in two versions, the "mini" (700 pages, 11MB) and the "maxi" (1300 pages, 18MB) versions as PDF files. For URLs see the TDF's Five years of LibreOffice blog post.

Happy Birthday, LibreOffice!

by erAck (23@ at September 28, 2015 05:49 PM

Official TDF Blog

Five years of LibreOffice

LibreOffice, the historyLibreOffice was launched as a fork of on September 28, 2010, by a tiny group of people representing the community in their capacity of community project leaders. At the time it was a brave – although necessary – decision, because it was rather clear to everyone that was not going to survive for a long time under Oracle stewardship.

In fact, the group of 16 founders launched an independent free software project under the stewardship of The Document Foundation, to fulfil the promise made by Sun ten years before – at the time of the first announcement of – of an independent free software foundation capable of pushing forward the free office suite to the next level.

After five years, LibreOffice is acknowledged in the marketplace as the sole Microsoft Office contender, based on a sheer feature by feature comparison, and on the number of successful migrations. Migrating to LibreOffice has never been easier, thanks to the Migration Protocol drafted by the most experienced people at The Document Foundation, which outlines the best practices adopted by several large projects worldwide.

A success confirmed by the Future of Open Source Survey 2015, which has put LibreOffice amongst the seven most valuable open source projects, based on the answers provided by over 1,300 professionals worldwide.

It has been an amazing journey. In five years, LibreOffice developers have not missed a single time based release, with major announcements in late January and late July, and minor announcements on a monthly basis. Thanks to this sustained pace, LibreOffice has reached a richness of features and a level of interoperability which are second to none.

LibreOffice 5.0, launched in early August, has been the most successful major release ever, triggering an unprecedented 8,000 donations in 30 days. Of course, the success has been reflected in the number of adoptions, which has soared. The icing on the cake has been the announcement of the Italian Defence Organization, which will be migrating some 150,000 PCs to LibreOffice starting from October 2015.

To celebrate our 5th anniversary, we have put together a book based on the blog post of the people who have made the history, which is available in a mini (700 pages) and a maxi (1,300 pages) version. Enjoy.

by Italo Vignoli at September 28, 2015 09:01 AM

>Pranav Kant

LibOCon 2015 -- Aarhus

I spent my last week with the LibreOffice community talking, hacking and altogether enjoying a lot with them. It was my first LibreOffice conference, and I have brought home a lot of learning this time. I relish each moment that I spent amongst such awesome people around me.

The conference was very well organized in the beautiful city of Aarhus, in Denmark (little bit colder than I had anticipated). As they say, more than a city, Aarhus was a feeling. The local organizing team left no stone unturned to take care of the participants, and everything went smoothly. I also really liked the newly constructed venue where the event was organized.

More than anything else, it was pleasure meeting my GSoC mentors, Michael Meeks and Miklos Vajna, in person, and presenting my work before LibreOffice community. Hacking together with them was a wonderful learning experience for me, especially hacking in the train with Miklos, and trying to fix some bugs. It was also a good experience meeting faces behind IRC nicks, talking to them and sharing ideas, and grow your social skills, altogether (I hope I did) – :).

At last, I would like to thank The Document Foundation for sponsoring this conference for me, without which it would not have been possible for me to come that far and gain this experience. Aforementioned, attending this conference was a good learning experience which has motivated me to excel as a programmer, and a will to keep this relationship strong with LibreOffice in future.

September 28, 2015 12:00 AM

September 27, 2015

Michael Meeks

2015-09-27 Sunday.

  • Up late, listened to a rather fine sermon; packed, passed the cathedral, coach to the airport, slept on the flight, slept on the train, picked up in Cambridge by wonderful wife & babes. Home for pizza tea.

September 27, 2015 09:00 PM

September 26, 2015

Michael Meeks

2015-09-26 Saturday.

  • Out to board meetings much of the morning with employees; lunch together, back for more talks at the Cabinn (somehow fell asleep) - out to a fine Italian restaurant in the evening.

September 26, 2015 09:00 PM

Leif Lodahl

Templates - Avoid the pitfalls

This article is an addition to my speak at the LibreOffice Conference in Aarhus. You can find the introduction here:  The presentation and video of the presentation will be available as soon as possible. Introduction to templates If you provide your users with

by Leif Lodahl ( at September 26, 2015 05:55 PM

Something about styles

Styles are much more than defining the look and feel of text in a paragraph. Its almost everything about how paragraphs behave in the context. A Paragraph style for example defines how words are hyphenated and in what language the text in the paragraph should be spell checked.Remember also to take advantage of the benefits of Page styles and Frame styles. Page styles are mostly used to setup the

by Leif Lodahl ( at September 26, 2015 03:24 PM

September 25, 2015

Michael Meeks

2015-09-25 Friday.

  • Dragged myself from sleep somehow; gave a final talk on regressions (as hybrid PDF):
    Regressions - hybrid PDF
  • Wandered the conference talking to people variously; fun. Out for dinner afterwards with some friends, bed earlyish.

September 25, 2015 09:00 PM

Caolán McNamara

crash testing and coverity, conference report

Slides for this morning's Crash Testing and Coverity numbers presentation. Summary, all ok, numbers ~0. If I'm analysing this right, then the highest quality is achieved at the height of the holiday season.

by Caolán McNamara ( at September 25, 2015 09:04 AM

vertical text columns preview

My small contribution to last night's LibreOffice conference hack-fest. In vertical text mode, the column view for pages now previews in the correct direction.

by Caolán McNamara ( at September 25, 2015 08:57 AM

Miklos Vajna

LibreOffice's Android port

(via Andras Timar)

I had the pleasure to share where we are wrt. the Android port of LibreOffice yesterday. Abstract on the conference website, slides at the usual place, video record "soon" as usual. :-)

September 25, 2015 07:39 AM

September 24, 2015

Michael Meeks

2015-09-24 Thursday.

  • To the conference, enjoyed various talks - great to hear from Eliane / EDX in Brazil. Hacked on slides. Gave a talk that tried to capture some of the work that has been done in the last year as hybrid PDF:
    A year of VCL - hybrid PDF
  • Lunch; Thorsten's talk, partner meeting. Out to a rather fine party in the evening (via. a rather circuitous route). Bed rather late.

September 24, 2015 09:00 PM

September 23, 2015

Michael Meeks

2015-09-23 Wednesday.

  • Up early, poked slides; rushed breakfast; out to the conference - enjoyed the opening talks; lunch with Simon, gave a keynote on LibreOffice and Collabora:
    LibreOffice and Collabora slides - hybrid PDF
  • Caught up with Noel Grandin & fixed Peralex' gitdm-config affiliation, Noel: an impressive proportion of commits.
  • Talked to partners, customers, awesome hackers, wandered the conference - scads of old friends; up late with Caolan, Cor & Kendy. Up late writing slides on VCL.

September 23, 2015 09:00 PM

Official TDF Blog

LibreOffice 5.0.2 announced at LibreOffice Conference

Map of Conference Attendees Countries

Conference Attendees Map

Berlin/Aarhus, September 23, 2015 – The Document Foundation has announced LibreOffice 5.0.2 during the opening session of the LibreOffice Conference, to underline the importance of the event for the community. LibreOffice Conference has opened today, and will be closing on Friday, September 25.

LibreOffice 5.0.2 is the second minor release of the LibreOffice 5.0 family, with a large number of fixes over the first minor release announced in August. So far, the LibreOffice 5.0 family is the most popular LibreOffice ever, based on feedback from the marketplace.

LibreOffice 5.02 will offer OpenGL rendering by default on Windows for the first time, for those with the very latest windows drivers. The functionality is easy to disable in case of issues by accessing Tools > Options.

LibreOffice 5.0.2 is targeted to technology enthusiasts, early adopters and power users. For more conservative users, and for enterprise deployments, TDF suggests the “still” version: LibreOffice 4.4.5. For enterprise deployments, The Document Foundation recommends the backing of professional support by certified people (a list is available at:

People interested in technical details about the release can access the change log here: (fixed in RC1) and (fixed in RC2).

Follow the LibreOffice Conference

Regular updates about the LibreOffice Conference 2015 will be published on the @libocon Twitter account and on the blogs of several participants. The conference website is at the following address:

Download LibreOffice

LibreOffice 5.0.2 is immediately available for download from the following link: LibreOffice users, free software advocates and community members can support The Document Foundation with a donation at They can also buy LibreOffice merchandise from the brand new project shop:

by Italo Vignoli at September 23, 2015 10:08 AM

September 22, 2015

Official TDF Blog

LibreOffice merchandising is available from Spreadshirt.Net

The Document Foundation has opened a store for LibreOffice merchandising at Spreadshirt.Net.

LibreOffice Merchandising Shop

We have a few items at the moment, mostly mugs and t-shirts, but we are open to suggestions and new designs. If you want to contribute, or if you already have a design to suggest, send an email to

The shop is managed by Spreadshirt, which is also responsible for the production of the items, the collection of the payment and the delivery of the items. The Document Foundation will get a small percentage of each item cost, to support the project.

by Italo Vignoli at September 22, 2015 06:39 AM

September 16, 2015

Miklos Vajna

Fixing Base form image backgrounds

In this post I want to go further, and after touching Calc, here is my first story about Base. Of course I lie, it seems that Base forms are kind of read-only Writer documents, at least that’s how I could fix the bug I’m describing here. :-) The topic is still the same, rounding rough edges after the fill attributes rework, this time a stretched background of a Base form. (Which was not stretched at all, it was simply centered both horizontally and vertically on the page.)

I’m not entirely sure how the document from tdf#92586 is created, but the interesting part from styles.xml is:

<style:page-layout-properties ... style:repeat="no-repeat">
     <style:background-image ... style:repeat="stretch"/>

So the schema allows specifying the way how the bitmap is repeated at two places, and in the past the later attribute won, and with the rework this got lost.

An additional problem that the commit had to solve is that the attribute on the page-layout-properties XML element is mapped to our FillBitmapMode API, while the attribute with the same name on the background-image XML element is mapped to the BackGraphicLocation API, which is specific to Writer. As a result, now there is a compatibility map from the old enumeration to the new one, that’s how the bug document is now rendered the same again, as in the past.

The fix is already backported to the libreoffice-5-0 branch.

September 16, 2015 07:10 AM

September 13, 2015

Andreas Mantke

New Extension and Templates Testwebsite updated

I added all my last changes for the new LibreOffice extensions and templates repository to the Plone test instance running on a resource of The Document Foundation today. The site is running on:

The site is currently using the default theming of the Content Management System Plone.

If you want to help test the current status you could ask for an account on the LibreOffice website mailing list: website <at>

by andreasma at September 13, 2015 08:22 PM

September 12, 2015

Andreas Mantke

New LibreOffice Extension-Template Site: Further Work

I worked on the Plone add-ons for the new LibreOffice extension and templates website very intensely in the last weeks. I added some more messaging for both, the site administrator and the contributor. I’ll show that at the upcoming LibreOffice conference in Aarhus during my talk.

I decided to add another Dexterity content type to both add-ons thus a contributor could also create a release that contains (a) link(s) to the extension or template file. This lead to a larger rework of the page templates for extension and template projects.

Currently I created the workflow for the releases of templates and will work on the same bits for extension releases during the next days.

You will get more details about the new LibreOffice extension and templates website during my talk at the LibreOffice conference in Aarhus.

by andreasma at September 12, 2015 08:37 PM

Charles Schulz

Drawing with LibreOffice

There are only very few software packages that can claim to be as feature-packed as LibreOffice. The thing is, sometimes it is even possible to forget about everything you can do with it. I’m not necessarily talking about the avalanche of features and improvements you can see listed on our wiki after each major releases; I’m rather pointing out that there is a little understood value in bundling and integrating various applicative uses together. This is the case for instance with Emacs (wait, am I actually blogging about LibreOffice and Emacs at the same time? That’s crazy!). I’m only one of the many users of Emacs that started using it with org-mode, text and code editing -so far, that’s what it says it’s supposed to do on the box- and ended up relying on this text editor for things such as IRC, email, rss feeds and document viewing. My point is that when it comes to LibreOffice, everybody thinks about its word processor, its spreadsheet module, perhaps Impress as well, but what about its vector graphics module Draw? Now that’s an interesting part of LibreOffice few people talk about. LibreOffice_4.0_Draw_Icon.svg

… And yet, it’s not because there are others, more powerful Free Software for graphical design and drawing out there: The Gimp is available of course, and perhaps more in line with Draw, Inkscape, Scribus and Krita all do a wonderful job. But have you ever given Draw a try?

LibreOffice Draw will not let you redesign a picture of a posing model so that it may go to print in a magazine. I doubt you will design the next generation of Airbus planes with it. But I can tell you it will go a long way in enabling you to draw charts, complex industrial schemas for plans and processes, and more simply, design graphical stuff anyone needs at some point in a business or a household (cards, menus, branding elements, process mapping, etc.)

There are really two sides to LibreOffice Draw’s own value:

  • Draw is powerful: the breadth of the things you can do with it, from the simplest skteches to the more complex charts, the use cases are really broad: brochures, 3D designs, photo galleries, process and org charts, there’s a lot you can do. And I should point out that the now famous LibreOffice Magazine is entirely designed with LibreOffice Draw!
  • Draw is fully integrated within LibreOffice: this means that your learning curve is reduced thanks to a familiar interface, and that it is possible to gain time if you do not have access to other tools such as Inkscape, or do not really know how to use them. Also, integrating files and images produced by Draw within other documents opened and edited by LibreOffice is possible, easy and really useful.

At the end of the day, I won’t claim that LibreOffice Draw is the best vector graphics editor out there. It clearly isn’t. But then it’s not MS Paint either, and it is not put to shame by its Visio and Inkscape counterparts either. Give it a try, especially if you rely on LibreOffice to work on your documents. You will be pleasantly surprized by how much time you can save and how creative you can be.

by Charles at September 12, 2015 12:31 PM

September 11, 2015

Jacobo Aragunde Pérez

An update on LibreOffice for Android

Summer time is for hacking! I booked some time in the last weeks to carry on with the work on the Android port we started earlier this year at Igalia, merging the pending bits in master, completing features and adding some polish. Now that everything is upstream, let me share it with you!

Merge ownCloud document provider

I had used the ownCloud Android library to speed up the implementation of the ownCloud document provider. Unfortunately, it included some libraries as dependencies in binary form and that was not acceptable to integrate the library in LibreOffice.

My solution was creating a Github fork of the library and replace the binary dependencies with the corresponding sources. Now a tarball containing the sources in that repository is downloaded and compiled by LibreOffice build system when asked for the Android target.

Implement save to cloud

While I was working on the Document Providers infrastructure, Miklos and Tomaž were implementing document edition on the LibreOffice port. Now there is some basic support to edit and save documents, I must enable the save operation in the Document Providers framework and in particular in the ownCloud test implementation.

The ownCloud save operation itself was easy, but knowing whether the local save operation had finished or not proved to be a bit more challenging. LibreOfficeKit API does not yet provide a way to set a callback on the save operation so we can check its status and do something after it has finished. As a workaround, I periodically check the modification date field in the file to know if LibreOffice core is already done with it.

This is meant to be a temporary solution, but at least, we can provide some feedback on the save operation now.

Feedback on save

A hamburger in my LibreOffice

Without any indication, the drawer containing the list of document providers was completely hidden from users; only a handful of people I showed the app to, besides myself, were aware of it. For that reason, I enabled the application home button, the one on the left of the action bar, to become a drawer indicator, the famous “hamburger” icon found in many Android apps.

It took me some time to figure out the way to put everything together so the button changes its icon and behavior according to the context. When the user is on the root folder, the “hamburger” will indicate the presence of a drawer menu with the additional locations implemented by the available document providers. When browsing some directory, it will become a back arrow to browse the parent directory. Finally, when the drawer is open it will also become an arrow to close the drawer.

Drawer indicator

Smart behavior for system back key

Tapping the system back key when browsing some directory and see the app close was a bit frustrating, because most users expect it to go back to the previous location, the parent directory. I’ve overridden the default behavior to make it smarter and context-aware. When browsing some directory, it will open the parent directory; when the drawer is open, it will close it; when browsing the root directory, it will ask for an additional tap for confirmation to exit the application.

Exit confirmation

All these patches are in master branch and will be part of the next major release. Impatient people will also find them in the daily builds from tomorrow onward.

by Jacobo Aragunde Pérez at September 11, 2015 06:44 PM

September 10, 2015

September 08, 2015

Markus Mohrhard

Performance tests are now executed regularly in LibreOffice

Someone following the LibreOffice development closely might know that we have actually two types of performance tests. I’ll will talk mostly about the newer in-tree tests but will also give a short explanation of the out-of-tree tests to explain the difference and when to use which of the two.

Out-of-tree performance tests

The out-of-tree tests have been written by Matúš Kukan and Michael Meeks quite some time ago and they have been running regularly on a LibreOffice server. Sadly until now they have not been as visible as necessary to alert us of newly introduced regressions. Thanks to some awesome work by Norbert we have now a nice website that shows the results of all performance tests.

Technically these tests are taking a full LibreOffice (built with optimization and symbols) and execute it under callgrind. We do this for import and export of some sample documents and later analyse the generated callgrind log files.

This allows to quickly generate numbers for import and export tasks. However it always includes a full LibreOffice start-up and shut down. Additionally it tests a whole bunch of unrelated parts of the import and export and makes it nearly impossible to test the performance of any dynamic operation. The “new” tests (they are already more than half a year old) help to solve a number of these problems.


In-tree performance tests

Matúš together with Laurent Godard added another kind of performance tests to solve some of the limitations mentioned above. They can be run in our build as part of make perfcheck and use the LibreOffice testing framework.

Instead of testing a whole LibreOffice start-up, import, export, shut down cycle under callgrind these tests just test some calls that you annotate in the code. It allows us to quickly write tests that just measure the performance of the small part of code that we are really interested in. It also allows us to test more or less user input by calling the methods, that the user input would call, directly in the test. Obviously this gives us more flexibility in testing the performance of LibreOffice and opens the possibility to find performance regressions in code outside of the import and export filters.

These tests in itself are sadly not that useful unless they are executed regularly and the results are easily accessible. Norbert has been working recently on making these results more visible and run them regularly on TDF hardware. You can find the latest results now also at together with the out-of-tree tests.

To show you how easy it is to add a new performance test I’ll document here the steps necessary for adding a test case to sc/qa/perf/scperfobj.cxx.

  1. add a new class method
  2. register the new class method inside the CPPUNIT_TEST_SUITE/CPPUNIT_TEST_SUITE_END block
  3. Use callgrindStart(); before the part that you want to include in your performance test
  4. Use callgrindDump(“module:a_nice_id”); after the last call that should be included in your performance test

You can even use several callgrindStart(), callgrindDump(“”) pairs in the same cppunit test. The new test case should appear automatically on the status page once the tests are run the next time.

As can be seen it is quite easy to write a new performance test and hopefully this motivates people to add new tests.


When should I use an out-of-tree test now?

Reading my section about the in-tree tests I might sound that you should always use an in-tree test. As a general rule you should put tests where you want to test the performance of the whole import or the export into the out-of-tree tests and all other tests into the in-tree tests.

However try to test as close to user interactions as possible. Testing some code that is never exposed directly to the user might give misleading results as some of its code might have been moved to another function that is always called with it, or some code was moved from a related method to the one that you are testing.


Helping with the web development

On a only slightly related note: We are still actively looking for an experienced web developer who helps us improve the results page and the new devcentral webpage. If you are interested in that task please contact Norbert or myself.



by Markus Mohrhard at September 08, 2015 03:08 AM

September 03, 2015

Charles Schulz

Open Source’s money issue

I tend to write a lot about how Free and Open Source Software projects rely on a community of contributors to grow and expand, and how projects without a healthy community tend to face problems and in some cases disappear. Today, I would like to discuss a sad reality of Free and Open Source Software: funding.

These past years -and months- we have had several examples how lack of funding can cut a project’s ability to develop, patch and maintain its codebase and by project I mean developers not getting adequate money, if no money at all, for what they do. There is really two sides to the same coin here. There’s the one where an entire industry re-uses entire FOSS stacks or components, sometimes without even acknowledging it licence-wise or even just in name. And there’s the other side, where the same industry will not compensate anyone upstream, because the license terms enables simple reuse and distribution of those software components.

Don’t believe the remaining few who will tell you that they do not believe that Free and Open Source Software is everywhere. It is pretty much everywhere, from your web server to your corporate I.T. infrastructure in the cloud and your plasma screen at home. But what those people don’t see is revenue streams, existing business transactions from the downstream (the distributors, integrators and users) to the upstream, the original developers. Or if they see it does not exist and know about it, then they should feel there’s a problem. This is how we have situations like the Heartbleed episode: the number of platforms, software products, hardware and custom designed and integrated systems embedding OpenSSL and OpenSSH is astonishingly large. In fact, pretty much everyone out there uses these components. But everyone thinks it’s up to the neighbour to buck the chef. And in the end, nobody did, leaving the developers without any real revenue to maintain this stack.

Choosing alternative licences -open source licences that is- won’t change anything. GPL software may have specific clauses preventing a distributor to alter its Free Software nature on the downstream (the famous “copyleft”) but I believe that this level of protection works only marginally better than any other licence. The Apache license and the whole Apache Foundation’s posture about setting corporations free from donating back does not work well or better either: If you are to believe the whole Apache theory about being more permissive and therefore encouraging contributions (I’m skeptical of that), you cannot claim that Apache licensed software has a better track record in working out developers’ revenue stream.

What could work then? I have no real answer to this. In some cases, we know that donations work. The Document Foundation is a good example of that, but there are others. Yet the donations mostly come from small, individual donations by our users. It is one way to solve the problem, even though in the case of the Document Foundation the money collected goes into investment made by the foundation itself, not necessarily to developers directly. For software stacks that are less “user facing” or consumer oriented, donations do not work as well. The ideal way is to hire or contract the orginal developers to work on the code itself or on jobs aimed at improving the software stack itself.

I happen to think that regulatory constraints will not work at all here. After all, it’s Free and Open Source Software. What is required is a shift in the culture of the industry about Free and Open Source Software. Our ecosystem is actually pretty tighly integrated, and it is rare to see an entire software stack developed from scratch overnight. Software components are used and reused everywhere, and Open Source licences are a key enabler of these practices. Compensating the upstream should be a matter of collective hygiene. But the awareness of the industry at large has only started to be raised, unfortunately. How many Heartbleed will we have to witness before we change?

by Charles at September 03, 2015 09:49 AM

September 02, 2015

Miklos Vajna

Fixing Calc header image backgrounds

I think this is my first Calc bugfix. :-) The problem I wanted to fix is that while LibreOffice 4.4 learned advanced fill attributes (gradients, hatches, etc) for page headers / footers in Writer, this broke the saving of simple graphic header backgrounds in Calc. Seeing that no-one stepped up to fix this, I tried to do this myself — and luckily the problem was in the ODF export filter, which is much more familiar to me, compared to Calc core.

Part of that larger feature was changes to the ODF filter, and the bug was exactly about touching shared ODF filter code to please Writer without testing other LibreOffice applications.

The actual problem was overlapping constants: as in multiple constants had the same numeric value. Such issues are sometimes hard to track down, in this case it wasn’t that hard: the context filter that tried to make sure we don’t write duplicated XML attributes removed the background property when it tried to guard header repeat offsets.

Given that this affected the LibreOffice 4.4 and 5.0 series, both branches got a backport of the commit, and so the next release from those lines will have the fix.

September 02, 2015 04:08 PM

Collabora Community

LibreOffice 5 Vanilla and LibreOffice-from-Collabora 4.4 released in Mac App Store

Today we release two major upgrades for OS X users:  LibreOffice Vanilla, the latest LibreOffice from the Document Foundation for early adopters, packaged by Collabora, hits version 5.0. At the same time LibreOffice-from-Collabora, our extra-stable productivity suite for professionals and  enterprise users, reaches version 4.4.

LibreOffice Vanilla

LibreOffice 5 Vanilla announcement splash

Released last month, LibreOffice 5 Vanilla brings an overhauled user interface, brand new icon set, and, especially relevant for Mac owners: improved support for high resolution (HiDPI) Retina displays, among many other improvements.

Of these, 18 new features were contributed by Collabora Engineers, including improved interoperability with OOXML and RTF documents, preview of styles and formatting in the sidebar, and all-new support for customisable shortcodes.


LibreOffice-from-Collabora 4.4 Mac App Store release

Following hot the heels of last week’s general release, LibreOffice-from-Collabora 4.4 is now available via the Mac App Store for $10. Combining rigorously tested features from LibreOffice 4.4 with new features developed by Collabora, this release offers new compatibility, deployment management, and document integrity features. Read more about our latest enterprise release in the release announcement.

No effort necessary

Existing users of Collabora’s apps from the Mac App Store need not lift a finger — today’s updates will be automatically detected and prompt you for upgrade. All prior purchases of LibreOffice-from-Collabora include the 4.4 upgrade as well as future patches. Once your update is installed, don’t forget to leave an updated review of your experience for other iTunes users!

by Sam Tuke at September 02, 2015 09:52 AM

August 24, 2015

August 23, 2015

Markus Mohrhard

Help for the VBA export work

So Rosemary has been working on one of my core hacks (actually she is the first to work on any of our core hacks, so congratulations for that), namely the VBA export to OOXML.

The missing VBA export is one of the old limitations of our OOXML filter. While we are able to save the unchanged stream back to an OOXML file we can’t save any modifications at the moment. With Rosemary’s work this will hopefully change in 5.1 and we will no longer loose macro changes when saving to OOXML.

To make sure that we deliver a good new feature it would be awesome if some of you who have real VBA documents can send a few to libreoffice.vba.export !at! gmail dot com. Currently we are using a few simple self generated documents but they surely miss a lot of the real world corner cases. This includes especially Excel functions defined in VBA and their use case. While I’m reading the VBA and the OOXML spec I ha to discover that MSO documents don’t completely follow the spec.

I’ll write a more detailed blog post once this feature hits master and I have an idea which features we can preserve during our export.

by Markus Mohrhard at August 23, 2015 06:38 PM

Charles Schulz

A word to the Wise…

I have been recently reminded that while it may be hard enough to discuss the role and importance of communities for Free and Open Source Software, it is equally important to understand the complexities and the challenges that a Free and Open Source Software foundation has to meet.
It may come as a surprise that the objectives and the issues faced by a FOSS foundation sometimes takes its members (its directors, board members or employees) to places and into discussions that they never would have imagined. It shouldn’t. A foundation may have its own set of challenges and issues that are distinct from the very members whose interests it is supposed to protect; and perhaps it is for the best.

A foundation cannot be a subsitute or an ersatz of a community. The community itself is the very thing without which the foundation has no purpose. However, the foundation exists both to protect assets (tangible or intangible) and to plan ahead into the future. The foundation therefore tries to have an insight into what lies ahead for its community. It “thinks” in strategic terms, which is precisely what a community cannot do under its usual form and because many in that community are simply not interested about these matters. Yet these matters must be addressed.

I realize that this could be seen as a slippery slope towards a situation where a foundation would be cut off from its community, from its project(s), and ultimately from its very roots. It is not. It is much easier -despite the amount of work the daily tasks represent- to get dragged down into the minutiae and the busy humdrum of everyday. One week is a release, the other day there’s some quarterly meeting; yet another day and the infrastructure has some hardware problems that must be dealt with immediately. Since days only last 24 hours, the day is quickly over, regardless of one’s talent. But when a foundation is only doing this, it is also not reaching outside its own boundaries, its own comfort zone. It refuses to acknowledge that while its role is to protect the community and enforce healthy principles across its projects and teams, it blinds itself from its very role in the broader industry. It does not look at the public policy landscape, even though digital policies directly impact the adoption of Free Software. It sees anything coming its way as yet another problem, and never as an opportunity. Anything that may threaten the status quo of the daily routine quickly becomes a problem that has to be shot down before it becomes even real.

All this is done in the name of the community. But the community, to paraphrase the famous movie, the community will be just fine. FOSS communities rely on foundations to fulfill a broad range of needs. But a community can very well work without a foundation. At least for 5 days; for the time required to do something that matter to the foundation as a foundation.

I know of no Free and Open Source Software foundation that has not been founded by thinking out of the box. Mozilla, Apache, the Document Foundation, etc. are no exception. A foundation that invokes its own principles to justify its lack of vision and its lack of prospective will ultimately turn the very community it was supposed to protect in the first place into something it has not wished, something that could be very much the opposite it was founded for. Ultimately people move on, things change and nothing ever stays the same; to think things can remain the way they are is foolish; they never will.

Serious literature about FOSS foundations may be found in a few places around the Net; these are three selected locations interested readers may wish to visit :

by Charles at August 23, 2015 02:56 PM


LibreOffice 5.0

The Document Foundation has announced LibreOffice 5.0, bringing new features including the following useful LibreLogo extension: now it’s possible to join arbitrary number of points using the command POINT with CLOSE and FILL in PENUP mode. For example, drawing a chord is quite easy:


or drawing a “flat” star:


    FORWARD 100
    BACK 100
    RIGHT 360/10
    FORWARD 70
    BACK 70
    RIGHT 360/10

and drawing nice sheriff badges:

TO star n m
    BACK n
    RIGHT 360/m/2
    FORWARD n*0.6
    BACK n*0.6
    RIGHT 360/m/2
CIRCLE 2*n*0.6-n/m/3

POSITION [130, 200]
    star 70 2+REPCOUNT
  RIGHT 90
  LEFT 90
  IF REPCOUNT % 3 = 0 [
    BACK 160
    RIGHT 90
    BACK 160*3
    LEFT 90

by Németh László at August 23, 2015 01:25 PM

August 21, 2015

Cor Nouws

Microsoft uses controversial publication to promote Office 365

The giant from Redmond must be desperate since it has to use a controversial story from a relatively small Italian city to combat open source software, as in the mean time many larger deployments also in Italy are happy with LibreOffice and the numbers produced by Provincia di Perugia prove the opposite of the Microsoft-publication.

Microsoft writes about the switch of the city of Pesaro from OpenOffice to Office 365. There are however many questions around the publication that should provide backing for the switch. Yet Microsoft uses that publication on it's website for promotion goals.
There are several facts that make the publication controversial. It mentions, for example, the sum of € 300.000 for migration and training costs and extra phone costs of € 85 a year without any data to back that. Sonia Motegiove, an Italian IT consultant, comments that an extensive training for 600 people would cost € 25.000 maximum.
The publication also claims that the interface would cause problems, but apparently the new 365 environment is not considered to cause users any problems.. When a lack of compatibility of OpenOffice is mentioned, Motegiove asks why Pesaro didn't choose for LibreOffice, with a much improved exchange of documents.
In another publication Italo Vignoli from LibreOffice-Italy points to the fact that Pesaro ignores facts such as the security issues that come with the use of Microsoft Office but in stead chooses wording to explain the migration that read as Microsoft propaganda.
All questions to the city of Pesaro or the project manager however, have remained unanswered.
Sources around Pesaro tell that the whole migration project was broken. First the involved IT company could not finish the project, and also half way there was a new IT-director with less focus on the project.

All this does not prevent Microsoft from using a 'study' to make false claims.
This situation looks similar to what happened with a Microsoft sponsored HP publication regarding the city of Munich, that works with Linux and LibreOffice. The HP publication 'proved' high costs in Munich coming with the open source solution. Yet the reality is that during the migration alone, 13 million was saved. That apart from the million or more license fees that ware saved every year since 2013. Savings that are partly spend to support the development of the open source software that Munich uses, and that also stimulate local/regional IT-firms.
Does these actions from Microsoft look so desperate because now also it's office-business faces serious competition?

by Cor & OfficeBuzz ( at August 21, 2015 12:12 PM