The Document Foundation Planet


October 17, 2017

Official TDF Blog

Coming up on Friday: first Bug Hunting Session for LibreOffice 6.0 Alpha 1

The LibreOffice community has returned from a great conference in Rome (more on that later this week), and we’re now working eagerly on LibreOffice 6.0, which is due to be released at the end of January 2018. This version will include a large number of new features – and those already implemented are summarised on the release notes page.

In order to find, report and triage bugs, the LibreOffice QA team is organizing the first Bug Hunting Session on Friday October 20, 2017. Tests will be performed on the first Alpha version of LibreOffice 6.0, which will be available on the pre-releases server a few days before the event. Builds will be available for Linux (DEB and RPM), macOS and Windows, and will run in parallel with the production version.

Mentors will be available from 08:00 UTC to 22:00 UTC. Of course, hunting bugs will be possible also on other days, as the builds of this particular Alpha release (LibreOffice 6.0.0 Alpha 1) will be available until mid November.

During the day there will be two dedicated sessions: the first to chase bugs on the main LibreOffice modules between 15:00 UTC and 17:00 UTC, and the second to test a set of the top 5 features between 17:00 UTC and 19:00 UTC. All details of the second bug hunting session are available on the wiki.

During the dedicated sessions, we will concentrate our efforts to chase and reproduce bugs, in order to confirm and file them in a more comprehensive way. Of course, the more comprehensive the bug report, the easier it will be for developers to solve the bugs in time for the final release. Thanks in advance for your help, and we look forward to your input!

by Mike Saunders at October 17, 2017 01:25 PM

October 16, 2017

Michael Meeks

2017-10-09 Monday.

  • Up, quick breakfast - Kendy & I tried to get Uber working to get us to the Hotel. Board meeting all day, board dinner until late.
  • Back with Kendy to try to locate somewhere to sleep; thankfuly found Miklos & woke Andras to let us in; quested for (and found) the necessary extra bed in the end; phew.
  • Worked until 3am polishing slides; tiring.

October 16, 2017 11:42 AM

2017-10-08 Sunday.

  • NCC in the morning, helped with the older kids work with Uche. Home for a quick Pizza lunch with Julie. Finished packing, J. drove me to Stansted, Ryan-Air-ness to Rome; got gotcha'd by an overly-expensive bus into town - should cost Eur 1.50 for a std. bus ticket.
  • Found Kendy, out for Pizza together; back to enjoy the free bottle of sparkling red & catch up until late.

October 16, 2017 11:42 AM

2017-10-12 Thursday.

  • Conference, lots of hallway-track goodness; positive CoC panel / discussion with Marina & Simon - good.
  • Lunch with friends great to see Pranav's Dialog Tunneling talk; gave a talk on Online Unit Testing:
    Collabora Online testing presentation
  • Off to the hack-fest in the evening, fine food, good company, lovely.

October 16, 2017 10:40 AM

2017-10-11 Wednesday.

  • Enjoyed the introduction, and the staggering depth of history, and richness of the venue - very grateful to the City of Rome for hosting us.
  • Massed board & MC & employees panel thing. gave my Collabora Opening keynote with some examples of the exciting thigns we've been up to for the last year:
    Collabora LibreOffice Keynote 2017
  • Lunch; and minuted a rather lengthy ESC meeting afterwards - with some ideas of where to go next in graphics & code cleanliness.
  • Out for a pleasant social event in the evening in town with the conference.

October 16, 2017 10:39 AM

2017-10-10 Tuesday.

  • Up early, breakfast from the Termini Station & waited around - sending scouts to find the missing bus, collecting partners and Collaborans variously. Eventually found the bus, got to the Airsoft venue, and played a surprisingly fun team-game - lots to learn:
    Collabora & Partners post-AirSofting
  • Coach to a nice Italian restaurant for lunch, and on for a presentation (minus working projector sadly), still - good stuff.
  • Back to Termini; and had an all-afternoon team meeting & brain-storming / planing session until late. Out for dinner together; talked until rather late, bed.

October 16, 2017 10:39 AM

October 15, 2017

October 13, 2017

Miklos Vajna

A year in LibreOffice’s PDF support LOCon talk

A year in LibreOffice’s PDF support was a talk I gave today at LibreOffice conference 2017. Given that this was one of the last talks at the whole conference, thanks to the ones who still did not go home, but listened. :-)

October 13, 2017 09:53 PM

October 12, 2017

>Marius Popa Adrian

Visual Studio 2017 Version 15.4 Released

You can now use CMake for Linux C++ development in Visual StudioThat could be interesting in cross compiling Firebird from Windows side to Linux/WSL

by Adrian Marius Popa ( at October 12, 2017 08:51 AM

October 11, 2017

Miklos Vajna

LibreOffice: Code Structure LOCon talk

Today I gave a LibreOffice: Code Structure talk at LibreOffice conference 2017. These are an updated version of Michael Meeks' original slides, it’s actually surprised me how many things changed since April 2016. :-)

October 11, 2017 03:26 PM

Official TDF Blog

The LibreOffice Conference 2017 begins!

This year’s LibreOffice Conference, which is being held in Rome, has started. Over 160 people have registered, and the event begins with an overview of The Document Foundation, LibreOffice and our sponsors. If you’re attending the conference, we hope you have a great time! We’ll be posting regular updates on social media.

(Photo: Simon Phipps)

by Mike Saunders at October 11, 2017 09:37 AM

October 05, 2017

>Marius Popa Adrian

Firebird 3 on Apple IOS

One side effect of new Firebird 3.0.3 builds for Apple Macosx is that now there is a Mach-O dynamically linked shared library for arm_v7 that can be used on IOS. You can ask for details on Firebird-devel  ps: For Firebird 2.5.x there is a build on Paul's blog also Egor Pugin created Cmake files for IOS Builds (I didn't tested that route yet)

by Adrian Marius Popa ( at October 05, 2017 05:18 PM

Official TDF Blog

The Document Foundation announces LibreOffice 5.4.2

Berlin, October 5, 2017 – The Document Foundation (TDF) announces LibreOffice 5.4.2, the second minor release of the LibreOffice 5.4 family, which was originally announced in early August. LibreOffice 5.4.2 continues to represent the bleeding edge in terms of features, and as such is targeted at technology enthusiasts and early adopters.

TDF suggests that conservative users and enterprises deploy LibreOffice 5.3.6 with the backing of certified professionals (an updated list is available at:

LibreOffice 5.4.2 includes over 100 bug and regression fixes. Technical details about the release can be found in the change logs here: (fixed in RC1) and (fixed in RC2).

Download LibreOffice

LibreOffice 5.4.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 Donations help TDF to maintain its infrastructure, share knowledge, and organise events such as the LibreOffice Conference, which is taking place next week in Rome (

Several companies sitting on TDF’s Advisory Board ( provide either value-added Long Term Supported versions of LibreOffice or consultancy services for migrations and training, based on best practices distilled by The Document Foundation.

by Mike Saunders at October 05, 2017 02:11 PM

October 02, 2017

Mike Kaganski

Windows Unicode API usage in LibreOffice

Windows still provides two sets of many of its Win32 API functions taking or returning strings: a legacy “Ansi” (functions named like fooA) and Unicode (named like fooW; available since Windows NT, and in Windows 95 with Layer for Unicode – and thus on any Windows OS supported by LibreOffice).

The “Ansi” functions take 8-bit strings in current codepage (single- or multibyte). The repertoire of characters representable in those strings is, naturally, limited to that codepage (that is either setup in system’s Language for non-Unicode programs, or explicitly set by running application). Unfortunately, unlike in other contemporary OSes, Windows doesn’t allow setting its locale to use UTF-8. If a string arrives to such a function that contains characters outside of that set, the string content will be altered, and functions’ behaviour might change unexpectedly.

“W” versions of those functions take UCS-2 strings, that are able to represent most of Unicode range (I am unsure if those strings are actually UTF-16, and so are able to represent the full Unicode repertoire, but anyway, even UCS-2 is much wider than most of single- or multi-byte codepages).

In last two weeks, we have replaced many places (0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D) in LibreOffice codebase where legacy “A”-functions were still used, with explicit calls of their “W”-counterparts, removing redundant conversions of strings from LibreOffice internal UTF-16 string representation to 8-bit strings and back. One of most significant effects might be on file-management functions, where such conversions could alter paths/names containing Unicode characters not representable in currently selected 8-bit codepage, and lead to failed file operations. One example of such problems is tdf#103525.

The changes are included into master towards 6.0.

by mikekaganski at October 02, 2017 07:01 AM

App compatibility manifest

Last week, we’ve added application compatibility manifests to LibreOffice libraries and executables. This is intended to allow the program to run in current OS context, instead of switching to a previous (namely, Windows Vista in case of absent manifest section) OS compatibility context. The effects of this are listed in a MS KB (this is alternative link just in case).

Currently we declare compatibility with Windows 7 through Windows 10. This change is integrated into current master towards LibreOffice 6.0.

by mikekaganski at October 02, 2017 06:08 AM

October 01, 2017

Andreas Mantke

Worked With The Zope Instance

I took some time to set up the environment to forward the Zope server port to my local box. Because I want to log into the Zope Management Interface with the permissions of an admin user I had add one first to the Zope instance. I run the debug instance of the Plone CMS with the command ‚adduser <adminusername> <password>‘ for this purpose.

Then I started the debug-instance with the command ‚fg‘. Once the debug-instance ran in forground (fg) mode, I started the forwarding within a terminal on my local box:
$ ssh -L 8085:localhost:8085 -N <server_name> -v

The <server-name> is the login to the server, whose port I wanted to forward.

The I could reach the forwarded server port in my browser with: http://localhost:8085/manage

This pointed me to the login of the root of the Zope instance and the ZMI. There I could login with the newly created admin user.

by Andreas Mantke at October 01, 2017 08:09 PM

September 28, 2017

Lior Kaplan

LibreOffice community celebrates 7th anniversary

The Document foundation blog have a post about LibreOffice 7th anniversary:

Berlin, September 28, 2017 – Today, the LibreOffice community celebrates the 7th anniversary of the leading free office suite, adopted by millions of users in every continent. Since 2010, there have been 14 major releases and dozens of minor ones, fulfilling the personal productivity needs of both individuals and enterprises, on Linux, macOS and Windows.

I wanted to take a moment to remind people that 7 years ago the community decided to make the de facto fork of official after life under Sun (and then Oracle) were problematic. From the very first hours the project showed its effectiveness. See my post about LibreOffice first steps. Not to mention what it achieved in the past 7 years.

This is still one of my favourite open source contributions, not because it was sophisticated or hard, but because it as about using the freedom part of the free software:
Replace hardcoded “product by Oracle” with “product by %OOOVENDOR”.

On a personal note, for me, after years of trying to help with OOo l10n for Hebrew and RTL support, things started to go forward in a reasonable pace, getting patches in after years of trying, having upstream fix some of the issues, and actually able doing the translation. We made it to 100% with LibreOffice 3.5.0 in February 2012 (something we should redo soon…).

Filed under: i18n & l10n, Israeli Community, LibreOffice

by Kaplan at September 28, 2017 12:52 PM

Official TDF Blog

LibreOffice community celebrates 7th anniversary

Results of survey amongst desktop users confirm project’s momentum

Berlin, September 28, 2017 – Today, the LibreOffice community celebrates the 7th anniversary of the leading free office suite, adopted by millions of users in every continent. Since 2010, there have been 14 major releases and dozens of minor ones, fulfilling the personal productivity needs of both individuals and enterprises, on Linux, macOS and Windows.

LibreOffice deployments are supported by certified developers and professionals (list available at: Many are employed by companies sitting in TDF’s Advisory Board (, who provide either value-added Long Term Supported versions of LibreOffice or consultancy services for development, migrations and training.

LibreOffice is available in over 100 native languages, and as such is contributing to the preservation of native cultural heritages, as in the case – for instance – of the Guarani language in South America, and the Venitian language in Northern Italy. All localizations are managed by local volunteers.

LibreOffice is also a reference implementation of the Open Document Format (ODF) ISO standard for office documents, which today represents the only choice in the market for true interoperability.

Results of Ubuntu 18.04 LTS Default Desktop Applications Survey

LibreOffice’s leadership amongst office suites has been recently confirmed by the survey of Ubuntu users for desktop productivity software, with 85.52% of the votes. The closest competitors were Google Docs with 4.29%, WPS Office with 3.22% and Apache OpenOffice with 1.96%.

The Ubuntu 18.04 LTS Default Desktop Applications Survey produced over 15,000 responses in total, with over 6,400 for the office suite category. LibreOffice received the largest margin of preference of the entire survey. Results are available here: (video and slides).

Download LibreOffice

Current versions of LibreOffice are available for download from the following link:

LibreOffice users, free software advocates and community members can support The Document Foundation with a donation at Donations help TDF to maintain its infrastructure, share knowledge, and organise events such as the LibreOffice Conference, with the next one taking place in October in Rome (

by Mike Saunders at September 28, 2017 09:05 AM

LibreOffice Design Blog

A Flock of Hummingbirds: On the Search for the LibreOffice Mascot

tl;dr: Please vote on the LibreOffice Mascot until Oct/08th at

Additional to the unique branding of LibreOffice today, we want to introduce an alternative to TDF’s trademarked logo/icon elements that can be used by the community with minimal restrictions. And as an open source project we involve the community in the process and asked for design proposals.…

The post A Flock of Hummingbirds: On the Search for the LibreOffice Mascot appeared first on LibreOffice Design Team.

by The LibreOffice Design Team at September 28, 2017 08:58 AM

September 26, 2017

LibreOffice Design Blog

Default Margins that Users Apply in LibreOffice Writer

Earlier this year we run a survey about default margins in LibreOffice Writer. The results should prove that the default settings are what users apply in most cases.

For the first question, What should LibreOffice Writer’s default page margin should be?

The post Default Margins that Users Apply in LibreOffice Writer appeared first on LibreOffice Design Team.

by The LibreOffice Design Team at September 26, 2017 05:33 PM

Official TDF Blog

The Document Foundation welcomes Kopano to the project’s Advisory Board

Berlin, September 26, 2017 – The Document Foundation (TDF) announced today that Kopano, the leading European provider of open source groupware and collaboration software, has joined the project’s Advisory Board. Kopano wants to contribute to the project in areas of its expertise, for example in user experience.

Kopano is a continuation of Zarafa. It offers a platform for communication, content sharing and self-organization, is entirely modular, and provides third party software vendors with simple integration options (e.g. via widgets).

Most features and integrations are available via a browser, thanks to Kopano WebApp, while smartphones, tablets and Outlook can be connected through Z-Push – the open source implementation of the Exchange ActiveSync Protocol (EAS). Kopano’s desktop client DeskApp is available for Windows, macOS and Linux.

Solutions like Kopano, combined with LibreOffice, help users to free themselves from the dependency of Microsoft and other cloud software, and enable companies to retain freedom and ownership of their data and software stack.

“Kopano is a welcome addition to the LibreOffice community, as they are extending the reach of LibreOffice in self-hosted Enterprise-environments by integrating LibreOffice Online with their collaboration solution. By becoming a member of the project’s Advisory Board, Kopano will provide experiences and insights necessary to improve the presence of LibreOffice Online”, says Simon Phipps, TDF Board Member.

“With our collaboration-products for messaging, ChatOps, Video Meetings, e-mail and groupware we offer the benefits of cloud-software in a self-hosted open source-stack. A powerful LibreOffice Online is the missing puzzle-piece for Enterprise-customers to keep their whole stack of modern collaboration under their own control”, says Brian Joseph, CEO of Kopano.

TDF Advisory Board’s (AB) primary function is to represent sponsors of the project, and to provide the Board of Directors (BoD) with advice, guidance and proposals. In addition, the AB is at the kernel of the LibreOffice ecosystem, and as such is key to the further development of the project.

About Kopano

Kopano is a leading European provider of open source groupware and collaboration software serving thousands of customers ranging from European governments to larger organizations. As a continuation of Zarafa, Kopano puts messaging, collaborative editing, video meetings, email and calendaring in one single interface. Website:


by Italo Vignoli at September 26, 2017 06:30 AM

September 25, 2017

Miklos Vajna

pdfium path segment API for LibreOffice's test needs

I recently fixed tdf#108963, which is a PDF export bug — in case of highlighted and rotated text in e.g. Impress, the highlight rectangle in the PDF export was not rotated.

This is how the export result looked like:

And this is how it now looks like, after fixing:

For a long time the PDF export filter had no tests at all; the current approach I introduced is that we parse the PDF export result with pdfium, which is an excellent PDF rendering library (I covered it in general in an earlier post).

So given that pdfium knows how that rectangle looks like, we should be able to query the details of it from a test as well, correct? It depends. Yes, it’s possible technically, but no, most of the pdfium functionality is actually not exposed at its public API.

The current situation is that one could use FPDF_LoadMemDocument(), FPDF_LoadPage() to get access to a PDF page, then FPDFPage_CountObject() and FPDFPage_GetObject() to iterate over objects on a page. We can filter for the relevant object by using FPDFPageObj_GetType() and FPDFPath_GetFillColor(), that will give us the only path that has a yellow fill color.

But getting more info about the geometry of the path isn’t really possible. As a workaround I went with FPDFPageObj_GetBounds() for the test, but wouldn’t it be nicer to get the individual segments (the objects that are the children of a path) and then get coordinates and other properties of a segment? This is what the recent API I added to pdfium now does. It provides the followings:

  • FPDFPath_CountSegments() gives you the number of segments of a path

  • FPDFPath_GetPathSegment() gives you a given segment, via a new FPDF_PATHSEGMENT opaque type

  • you can use FPDFPathSegment_GetPoint() to get the coordinates, FPDFPathSegment_GetType() to get the type (move to, line to, etc.) and FPDFPathSegment_GetClose() to see if the segment closes the current subpath of the path (or not)

This means that after the next pdfium update in LibreOffice, PDF export tests can nicely assert these properties of paths instead of dubious bounding box should be larger after rotation assertions.

September 25, 2017 10:05 AM

September 20, 2017

Eike Rathke

Tooting at

Not been much active there, but is down since days (weeks?) without any sign of life. So I revived my account (

by erAck (23@ at September 20, 2017 07:26 PM

September 16, 2017

Andreas Mantke

Notification About New Projects On The Review List

If a member of the LibreOffice extensions and templates website submitted a new project for publication it was added to the review list. But there is currently no notification of the reviewer about this new entry on the list. Thus the reviewer had to log in to the site constantly to check if there is a new project on the list.

To make the life of the reviewer a bit easier I added a notification by email in case someone submitted a new project for publication. I did this for both Plone addons which drive the LibreOffice extensions and templates site. The site itself runs on Plone 5, a powerful Content Management System.

by Andreas Mantke at September 16, 2017 08:26 PM

September 13, 2017

LibreOffice Design Blog

What Open Source Means to LibreOffice Users

Being an open source project is one of the pillars of LibreOffice. Understanding the people who not only build and maintain but also use LibreOffice is important to anyone concerned about the sustainability of open source. So we asked the community what aspects are important and present the results now.…

The post What Open Source Means to LibreOffice Users appeared first on LibreOffice Design Team.

by The LibreOffice Design Team at September 13, 2017 08:48 PM

>Marius Popa Adrian

Firebird 4.0 Alpha 1 release is available for testing

Firebird Project announces the first Alpha release of Firebird 4.0, the next major version of the Firebird relational database, which is now available for testing.

by Adrian Marius Popa ( at September 13, 2017 02:12 PM

ADO.NET provider for Firebird is ready (with .NET Standard 2.0 support)

New version of ADO.NET provider for Firebird is ready for download. This release is about .NET Standard 2.0. Now the .NET Standard 2.0, with all the new APIs supported, version is available. Another new feature is support for passing key over the wire for encrypted databases (you need to have server side plugin for this feature, i.e. this from IBPhoenix). New connection string property

by Adrian Marius Popa ( at September 13, 2017 02:11 PM

Jaybird 3 with Firebird 3 embedded example

Mark Rotteveel published a guide and example program using Firebird 3 Embedded with Jaybird 3. The sample you can find it on

by Adrian Marius Popa ( at September 13, 2017 02:07 PM

September 11, 2017

Caolán McNamara

Flickerless Gtk3 OpenGL Transitions

While I got OpenGL transitions working under Gtk3 at the end of last year basically matching the Gtk2/Generic OpenGL quality the transition into and out of the OpenGL sequence wasn't very satisfying. And with access to HiDPI it was clearly even worse with an unscaled image momentarily appearing before the correct one.

So here's the before and after of the improvements that landed on upstream master today. Just screen-recordings with built in ctrl+shift+alt+t under gnome3 and positioned side by side and clipped roughly together in pitivi

by Caolán McNamara ( at September 11, 2017 08:13 PM

September 07, 2017

Lior Kaplan

FOSScamp Syros 2017 – day 3

The 3rd day should have started with a Debian sprint and then a LibreOffice one, taking advantage I’m still attending, as that’s my last day. But plans don’t always work out and we started 2 hours later. When everybody arrive we got everyone together for a short daily meeting (scrum style). The people were divided to 3 teams for translating:  Debian Installer, LibreOffice and Gnome. For each team we did a short list of what left and with what to start. And in the end – how does what so there will be no toe stepping. I was really proud with this and felt it was time well spent.

The current translation percentage for Albanian in LibreOffice is 60%. So my recommendation to the team is translate master only and do not touch the help translation. My plans ahead would be to improve the translation as much as possible for LibreOffice 6.0 and near the branching point (Set to November 20th by the release schedule) decide if it’s doable for the 6.0 life time or to set the goal at 6.1. In the 2nd case, we might try to backport translation back to 6.0.

For the translation itself, I’ve mentioned to the team about KeyID language pack and referred them to the nightly builds. These tools should help with keeping the translation quality high.

For the Debian team, after deciding who works on what, I’ve asked Silva to do review for the others, as doing it myself started to take more and more of my time. It’s also good that the reviewer know the target language and not like me, can catch more the syntax only mistakes. Another point, as she’s available more easily to the team while I’m leaving soon, so I hope this role of reviewer will stay as part of the team.

With the time left I mostly worked on my own tasks, which were packaging the Albanian dictionary, resulting in and making sure the dictionary is also part of LibreOffice resulting in . When it is accepted, I want to upload it to the LibreOffice repository so all users can download and use the dictionary.

During the voyage home (ferry, bus, plain and train), I mailed Sergio Durigan Junior, my NM applicant, with a set of questions. My first action as an AM (:

Overall FOSScamp results for Albanian translation were very close to the goal I set (100%):

  • Albanian (sq) level1 – 99%
  • Albanian (sq) level2 – 25% (the rest is pending at #874497)
  • Albanian (sq) level3 – 100%

That’s the result of work by Silva Arapi, Eva Vranici, Redon Skikuli, Anisa Kuci and Nafie Shehu.

Filed under: Debian GNU/Linux, i18n & l10n, LibreOffice

by Kaplan at September 07, 2017 03:13 PM

September 06, 2017

Florian Effenberger

Hilf mit, die LibreOffice Hackfeste zu verbessern!

Einer der Schwerpunkte in der LibreOffice-Community ist die Weitergabe von Wissen. Im Rahmen von zahlreichen Initiativen wie Workshops, Bug Hunting Sessions, Vorträgen und Hackfesten arbeiten wir gemeinsam daran, nicht nur das Programm zu verbessern, sondern vor allem auch das Wissen um den Aufbau, die Struktur und die Programmierung von LibreOffice weiterzugeben, um mehr Menschen die Mitwirkung an der Entwicklung zu ermöglichen.

Mein Kollege Björn Michaelsen hat jetzt einen neuen Vorschlag eingebracht, wie wir diesen Gedanken noch effektiver voranbringen können.

Die grobe Idee hat er bereits in einer E-Mail auf unserer öffentlichen Vorstandsliste skizziert. Vereinfacht gesagt geht es darum, dass wir das Wissen, das wir bislang vor allem oft „remote“ genutzt haben, jetzt direkt vor Ort an die Hackfeste holen und gemeinsam und live mit erfahrenen Programmierern an LibreOffice arbeiten.

Im Wiki finden sich zahlreiche LibreOffice-Hackfeste
Im Wiki finden sich zahlreiche LibreOffice-Hackfeste

Das Ganze ist derzeit eine grobe Idee, die gemeinsam mit der Community diskutiert und entwickelt werden soll. Dazu ist für

Sonntag, den 17. September 2017
um 16:30 Uhr

eine öffentliche Telefonkonferenz in englischer Sprache geplant, zu der wir alle Interessenten – ob alte Hasen oder neue Mitwirkende – ganz herzlich zum Mitdiskutieren und Mitdenken einladen wollen!

Die Telefonnummern zur Einwahl findet ihr in unserem Wiki, die Raumnummer ist die 21 24 86. Das Ganze richtet sich ausdrücklich auch an Nicht-Entwickler, die ihre Ideen und Vorschläge mit uns teilen wollen.

Wir freuen uns auf euch!

by Florian Effenberger at September 06, 2017 10:12 AM

September 04, 2017

Lior Kaplan

FOSScamp Syros 2017 – day 2

The morning stated by taking the bus to Kini beach. After some to enjoy the water (which were still cold in the morning), we sat for talking about the local Debian community and how can we help it grow. The main topic was localization (l10n), but we soon started to check other options. I reminded them that l10n isn’t only translation and we also talked about dictionaries for spell checking, fonts and local software which might be relevant (e.g. hdate for the Jewish/Hebrew calendar or Jcal for the Jalali calendar). For example it seems that regular Latin fonts are missing two Albanian characters.

We also talked about how to use Open Labs to better work together with two hats – member of the local FOSS community and also as members of various open source projects (not forgetting open content / data ones projects as well). So people can cooperate both on the local level, the international level or to mix (using the other’s project international resources). In short: connections, connections, connections.

Another aspect I tried to push the guys toward is cooperating with local companies about open source, whether it’s the local market, the municipal and general government. Such cooperation can take many forms, sponsoring events / giving resources (computers, physical space or employee’s time) and of course creating more jobs for open source people, which in turn will support more people doing open source for longer period.

One of the guys thought  benefit the local community will benefit from a mirror server, but that also requires to see the network topology of Albania to make sure it makes sense to invest in one (resources and effort).

We continued to how it would be best to contribute to open source, mostly that Debian, although great isn’t always the best target, and they should always try to work with the relevant upstream. It’s better to translate gnome upstream then sending the Debian maintainer the translation to be included in the package. That shortcut can work if there’s something urgent like a really problematic typo or something what unless done before the release would require a long long wait (e.g. the next Debian release). I gave an example that for important RTL bugs in LibreOffice I’ve asked Rene Engelhard to include the patch instead of waiting for the next release and its inclusion in Debian.

When I started the conversation I mentioned that we have 33% females out of the 12 participants. And that’s considered good comparing to other computer/technical events, especially open source. To my surprise the guys told me that in the Open Labs hackerspace the situation is the opposite, they have more female members than male (14 female to 12 male). Also in their last OSCAL event they had 220 women and 100 men. I think there’s grounds to learn what happens there, as the gals do something damn right over there. Maybe Outreachy rules for Albania should be different (:

Later that day I did another session with Redon Skikuli to be more practical, so I started to search on an Albanian dictionary for spell checking, found an old one and asked Redon to check the current status with the guy. And also check info about such technical stuff with Social Sciences and Albanological Section of the Academy of Sciences of Albania, who is officially the regulator for Albanian.

In parallel I started to check how to include the dictionary in LibreOffice, and asked Rene Engelhard to enable Albanian language pack in Debian (as upstream already provide one). Checking the dictionaries I’ve took the opportunity to update the Hebrew. It took me a little longer as I needed to get rust off my LibreOffice repositories (dictionaries is a different repository) and also the gerrit setup. But in the end:

With the talks toady and the starting to combine both Debian and LibreOffice work today (although much of it was talking) – I felt like I’m the right person on the right place. I’m happy to be here and contribute to two projects in parallel (:

Filed under: Debian GNU/Linux, i18n & l10n, LibreOffice

by Kaplan at September 04, 2017 09:44 AM

August 27, 2017

Björn Michaelsen

Hackfests: The Next Generation

Reports of my assimilation are greatly exaggerated.

— Jean Luc Picard, Star Trek: First Contact

(This is a repost from the discussion on the discussion — including all typos and misspellings — for more visibility.)

Hi all,

I recently had a look at a variety of challenges the LibreOffice community is facing wrt Hackfests and especially also tenders:

Status Quo

– due to a set of reasons based in the size of the project, the scope and selection of tender topics, the rules of properly running an NGO and the distibution of skilsets and available time in the BoD it is a lot harder to oversee the tenders for TDF than it would be for a for-profit organization.

– also, for historic reasons mostly, these tasks have been limited to the BoD mostly, while as an open disttributed and tranmsparent community we should not needlessly concentrate this work: rather the challenges and solutions should be shared as widely as possible in the community (and beyond).

– the waterfall modelled tenders have no iterative approach. Because of this they also tend to be mostly quite small, leading to significant overhead at both TDF and for the business implementing the tender.

– contracting out tender in bulk in a blackbox fashion naturally limits the ressources spend on documentation of discovered challenges. It thereby also needlessly limits the educational output to the community. There is such output, but it clearly could be better.

– beyond that we reduced doing Hackfests ~2 years ago, limiting the exchange of knowledge they provide.

– Unlike in the good old days, we dont have urgent infrastructual problems and the like to solve that would rally developers around topics. So motivation for certified devs to attend has shrunk. And those that do attend usually use the facetime for syncing on various issues, while the actual work on the code is somewhat limited. Even more when there is an emergency at the (professional) developers employer (Unfortunately, there often is.)

Suggested new format

So everyone hip in the last decade would see the words “waterfall”, “non-iterative”, “controlling overhead” would scream “get agile” from the top of their lungs. In general that might solve the practical problems, but as agile is essentially a way to move the customer in close enough to create the trust and bond allowing the overhead to go away, that is exactly what we need to watch out for and avoid: the foundation should not bind itself too close to any single commercial provider of services in its core operations.

But maybe revitalizing Hackfests are an opportunity here. Here is a suggested new format:

– TDF selects a small of the tenderable topics (6 man days)

– TDF selects a “product owner” for the topic (could be an TDF employee or a qualified and motivated TDF member)

– TDF hires 2 certified developers from LibreOffices companies for 3 days each

– TDF offers 2 days “development training” to its members, but also to the general community: ideally we select four people for this.

– All are invited to a two day Hackfest.

– Hired consultants are expect to pair program with one of the volunteers on each day, with the hired person not distracted by other business and doing the main effort with the paired volunteer focusing on learning.

– On each day, one of the hired developers works on the projector of the room, allowing other partcipants to the Hackfest to observe and learn.

– Closing the day, each paired team will give a 5-15 minutes lightning talk on their progress and challenges over the day. This presentation should be done by the paired volunteer to the best of their ability and recorded e.g. by TDF staff for publication.

– Rest of the extra booked day should be used for a 1-hour prep Hangouts, follow ups and overtime.

– Selected paired volunteers should ideally be 50% certified or uncertified developers and at least 25% volunteers active in non-development areas (e.g. documentation, l10n …).

– Beyond this, it will be a “normal” Hackfest allowing others to mix an mingle.

What this might solve (hopefully)
– Controlling and the need to proof due diligence going away as it is performed right in the open and self-documented, reducing the vast redtape needed to set up and run tenders in the first place

– the involving the broader community is much more involved in this major aspect of the foundations work

– the community gets a much better transparency on the real cost and challenges
of development

– we approach a more iterative/agile approach without being hit by the challenges this usually implies for an NGO

– we provide clear and visible progress and effort on education for the community and the general public

– we might help onboarding of new developers and make LibreOffice more interesting for contribution

– if this works on this 4-6 man day scale, we might consider extending it (e.g. a three developer week[1] with prep is already a 21 man day project)

There has already been some internal feedback from a smaller circle I shared this with first: There was some concern (one pointing out this new format isnt free of challenges[1], one asking for bigger steps as this proposal was considered to small/iterative[2]), but beyond that the feedback was generally quite positive.

As such, Im looking for people who would like to join in and help giving this new format a try: The starting point would be organizing a broad, welcoming and well-organized Hackfest at a location easily reachable for many in the community: Thus at well-connected place in europe. It should also have local people on the ground, who are enthusiastic to make this a success.

If you are interested in helping with this, either as:

– someone on the ground helping to organize the Hackfest

– someone who wants to pair program with a hired certified developer at a Hackfest

– someone who is just interested in joining the Hackfest in general

– someone who helps fleshing out the details of this idea

feel free to contact me. I will try to set up a team of people interested in getting this off the ground. As noted above, if this proves to be successful, this might be the start of something excited and big bringing this community and project to a new level!

Another (final) note: This list is currently unfortunately less used than it should be to provide information on the proceedings of the foundation. The Board is mindful of that and tries to change this. This is a start. Feel free to share this message to those in the community who might have missed it as they are not (yet) subscribed to board-discuss@.



[1] But neither is the status quo — in many more ways.
[2] note that the two kinds of criticism pointed in exactly opposite directions

If you are interested in this effort, feel free to:

UPDATE: Time and date for the call are set: Sunday 2017-09-03 14:30 UTC, Talkyoo room 21 24 86 #. Please join!

by bmichaelsen at August 27, 2017 11:22 AM

August 25, 2017

Cor Nouws

LibreOffice at Tilburg University Orientation Program

At the beginning of the new year, the Tilburg University organizes the Tilburg Orientation Program (TOP) presenting all kind of interesting and cool stuff for the new students. So at August 22, a nice and sunny day, there was a huge event in a park with lots of plays and booths and music and beer. And: three people from the Dutch LibreOffice team were there!
We had a nice booth and prepared both flyers and small cards. Especially the cards were handsome to reach out to people: "want a free card for free software" is a short and appealing message. Thus we handed out a six to seven hundred of the cards. Of course we had good talks too: dozens of individuals and groups wanted more information. And there are people that know and use open source. Or were just in need for a good office-suite for their new bought Mac book ;)
It's always interesting to see how people react. For example if you tell that Microsoft doesn't really loves students, when they offer software very cheap, but that they just want to make you very well used to it, so that they can charge high prices when you've finished your study.. And compare that to LibreOffice: free always, at school, home, office. And of course free choice for donations or paid support if desired! Was fun to hear some of the students call the way Microsoft does this "the drugs dealer method" ;) Anyways: Pieter Kristensen, Freek de Kruijf and me had great fun with the people and the music and showing LibreOffice. To be continued next years, as far as I'm concerned.. :) Not the least since universities are an excellent place to support the importance of ODF as sustainable and durable document standard.

by Cor & OfficeBuzz ( at August 25, 2017 03:25 PM

Miklos Vajna

Split sections inside tables for LibreOffice Writer

Tables and sections in LibreOffice Writer are both containers, and in some cases it makes sense to have sections inside tables or tables inside sections. (For example you can mark a group of paragraphs as read-only by including them in a read-only section.) Tables in sections, split over multiple pages was already working, but now it’s possible to have sections in tables split over multiple pages as well.

First, thanks Escriba who made this work possible.

There were 3 parts of this work, you can read some details about them below.

Split of multi-line paragraphs

The first goal was to handle the split of multi-line paragraphs inside sections inside tables. Initially this looked like this:

Split of one-liner paragraphs

Technically this is a situation different to the previous one, as split paragraphs have a master (first) frame and one or more follow (non-first) frames; and the previous stage only addressed the move of follow frames to next pages. Initially such a document looked like this:

Merge a split section

The last piece was moving paragraphs back to previous pages when there is again space for them. Initially we did not use the newly available space:

After commit tdf#108524 sw: handle sections inside tables in SwFrame::GetPrevSctLeaf() the paragraph is moved back properly:

One more thing…

Given that all code changes affect how sections in tables are handled in a parent frame in general (which is a body frame in all the above pictures), the same changes are also usable for other parent containers as well, e.g. linked TextFrames. Here is how that looks like:

That’s it for now — as usual the commits are in master, so you can try this right now with a 6.0 daily build. :-)

August 25, 2017 09:09 AM

August 23, 2017

Andreas Mantke

Installed WordPress On A Small PC

I worked further on the small pc with an wireless access point and added a wordpress instance. I exported the work, I already did on my notebook and imported it into the database on the small pc. I configured wordpress to point to the imported database. I copied also the wordpress theme over and installed a missing event calendar plugin. There is only one missing point. I had to copy the content from the uploads directory too. That’s on my todo.

by Andreas Mantke at August 23, 2017 08:06 PM

August 22, 2017

Markus Mohrhard

Announcing automatically updating daily Windows Libreoffice builds

I announced my work on automatically updating builds and the support for Linux daily builds a while ago. The plan has always been to get this feature ready for Windows release builds in time for the 6.0 release. We are by now about halfway through the feature development cycle for the release and I’m finally able to announce the accomplishment of the next milestone: automatically updating daily Windows builds.

You can fetch the daily builds from the @38-updater build directory. The builds are currently produced on my TDF-owned Windows 7 build bot and will normally be updated during the European night. Currently the builds are en-US only but I plan to add additional languages and a few more disabled features over time.

Note that the archives contain one extra level of directories compared to Linux archives with long directory names which can cause problems with the Windows path length limit. If your build does not start, move the installation up in the directory hierarchy and shorten the directory names.


After many comments related to my last blog post about the automatic updater were by people not reading the limitations and plans (or missing plans) of our Linux updater builds (we don’t plan to provide updater enabled release builds on Linux!!) I’m going to list them first this time.

The support that has been finished by now is limited to daily builds that are “installed” in user writeable locations. This is not yet a complete updater for our release builds and is mainly for the QA team and power users that want to test the current daily master builds.

We can not yet update builds installed through MSI and can not handle the user account control which will be necessary for correctly installed LibreOffice. However, similar to the automatically updating Linux builds, this is one step on the way to automatically updating Windows release builds.


Many parts of the original blog post about the updater are also true for the Windows updater code. The biggest change is the switch from a two step update, first downloading and creating an updated copy and later replacing the installation with the updated copy, to a one step update, first downloading and later applying the update in place. This change was necessary as Windows prevents modifying files that are already open. Additionally, this makes it significantly easier to implement a secure updater for MSI/MSP installations.

One small additional feature managed to creep into the code while I was waiting for builds to finish. I managed to enable the updater executable GUI so that we can now show a dialog with a progress bar while the update is running. The GUI is already working on Windows and I’m close to finishing the work on the Linux version.

Screenshot of the LibreOffice Updater GUI.

The new LibreOffice Updater GUI.

Apart from these two larger changes, I was mostly fixing the Windows integration. This includes handling windows paths, integrating the updater with the windows crypto system, and making sure that my tooling handles the special cases of our Windows updates. For anyone interested in the details I try to tag all commits with the updater prefix.


As I mentioned in the beginning the overall goal is still an automatic updater for our 6.0 release builds. On the way to this goal I still have two big milestones:

  1. Generation of MSP updates and infrastructure to apply them through our MAR file based updater. The Mozilla developers were once working on integrating MSI support into their updater code as part of moz#231062 but abandoned that work.
  2. Integration of the updater service to allow installing in the normal Program Files directory and integration with the UAC. Most of the code is already there and already built as part of the updater builds but the integration into our (horrible Perl mess of) packaging and installer code is still missing.

If I manage to finish these two milestones by mid of November in time for the feature freeze and the release engineering team and ESC are satisfied we will have automatically updating builds in time for the LibreOffice 6.0 release. By using the current updater builds and reporting any problems to me, you can help making sure that this will become reality.

As always additional help is welcome. Just ping me (moggi) on IRC (#libreoffice-dev channel on Freenode) and talk to me how you can help. We also always have tasks that don’t require any C++ skills and I’m currently looking especially for interested developers with python and django skills (The whole server side of the automatic updater as well as a large part of the crash reporter is written in python with django). If you know another programming language and want to help with LibreOffice please contact us on IRC or on our developer mailing list (



by Markus Mohrhard at August 22, 2017 03:01 AM

August 21, 2017

>Akshay Deep

GSoC 2017: Charmap Integration

These awesome three months of summer spent developing for LibreOffice under Google Summer of Code, have filled me with great zeal and zest. A plethora of important additions was made to the software bundle under the project titled “Usability of Special Characters”, and these new features will be made available in the version 6.0 of LibreOffice (Release Notes for 6.0). Here is a glimpse of what the users will be receiving in the new update.

Note: Please zoom-in the web page or open the GIF’s in the new tab if the character grid is not correctly visible.

Screenshot from 2017-08-22 21-21-46.png

Special Characters in LibreOffice Master


‣ Search functionality via generic code point name


Glyph name properties have been introduced to LibreOffice using the API provided by International Components for Unicode (ICU). The program identifies glyphs according to their names provided by ICU and then, the search results are displayed. There’s a display label which is dedicated to glyph’s Unicode name.

‣ Inter-font dynamic glyph search

inter-font search.gif

As simple as it could be made, a user can now type the name of the glyph and scroll between fonts until the desired results are shown.

‣ Recently Used Characters and Favorite Characters


‣ Toolbar Dropdown control for Quick Access!

In pursuance of providing quick access to the above Recent and Favorite character list, a toolbar dropdown control has been developed. It is supposed to replace the current toolbar button which opens the special character dialog in the currently circulated LibreOffice 5.3.


The GIF below is an example of how easy a user can find the desired symbols and can pin it for quick access in future.


‣ Context-menu and Mouse click controls for easier interaction


Link to the major patch submissions:

Glyph View and Recent Characters Control in Special Characters dialog

Favourites feature in Special characters

‣ Special Characters Toolbar Dropdown Control

‣ Unicode Character Names Integration using ICU

‣ Search feature for Special Characters

I was mentored by Samuel Mehrbrodt, Heiko Tietze, and Thorsten Behrens in GSoC 2017. I would like to give my regards to the LibreOffice community which helped me through the deadlocks I faced during the project. It has been an awesome two-year journey with LibreOffice, and I hope it will remain the same in future and the open-source technologies will flourish with their full potential and thrive to its zenith.

by Akshay at August 21, 2017 08:47 AM

August 20, 2017

Andreas Mantke

Upgrade To Leap 42.3

I upgradet my notebook to openSuSE Leap 42.3 with zypper dup and everything went well. It took only a relatively short time in comparison with an upgrade of MS Windows and I had not to restart my box several times.

The upgrade needed only some edits to the software repositories that I used for the notebook. Nearly all of them needed only a change of the version number in the URL Form 42.2 to 42.3. The LibreOffice Factory repository (needed especially for building) needed a different tweek. There is no sub-repo for 42.3 yet. This I had to change to the sub-repo ‚openSUSE_Factory‘ instead. That was all I had to do before I run the zypper dup command.

Really easy to update the Linux distribution. And I had not to reedit my user configuration etc. Everything works AS before.

by Andreas Mantke at August 20, 2017 10:26 AM