Welcome to The Document Foundation Planet

This is a feed aggregator that collects what LibreOffice and Document Foundation contributors are writing in their respective blogs.

To have your blog added to this aggregator, please mail the website@global.libreoffice.org mailinglist or file a ticket in Redmine.


Tuesday
21 May, 2019


face
  • Mail chew, M. ill at home; picked up H. and Charlotte after an exam; built slides, poked projections. Lunch. Monthly mgmt call. Admin.

face

OW2con 2019 is the annual open source event bringing together the OW2 community, technology experts, software architects, IT project managers and decision-makers from around the world. The conference will be hosted by the Orange Gardens Innovation Center, Paris-Châtillon, on June 12-13, 2019.

The central theme of OW2con 2019 is: “Open Source Toward Industry Maturity”. Indeed, with open source becoming mainstream, IT developers, vendors, users and even open source organisations such as OW2 have to adapt. Today, open source projects are becoming increasingly competitive and all IT developers, vendors and users must have an open source strategy.

During OW2con 2019, The Document Foundation and LibreOffice Online will be presented during two different talks:

  1. Breakout SessionAdding LibreOffice To Your Online Solution, managed by Michael Meeks (Collabora), Philippe Hemmel (Arawa) and Thorsten Behrens (CIB), on Wednesday June 12, from 1:45pm to 3:45pm.
    LibreOffice Online can be integrated into cloud solutions, as in the case of Nextcloud, ownCloud, Pydio and Seafile. The software is 100% open source and can be the perfect solution for GDPR issues in organizations. During the session it will be possible to get an overview of the application, and ask both technical and business-related questions.
  2. TalkIntroducing The Document Foundation, by Simon Phipps (TDF/OSI), on Thursday June 13, from 9:45am to 10:00am.
    The Document Foundation is one of OW2’s newest Affiliate organisations, and is a global charity based in Germany that works to promote open source productivity tools. Its flagship project, LibreOffice, is available across major desktop platforms and continues the fourth decade of impact from the code that started life as Star Writer on CP/M.

More information about OW2con 2019 are available on the event website: https://www.ow2con.org/view/2019/.


Monday
20 May, 2019


face
  • Out for a run, mail chew, pleased to see Lubos' improved script to render perf output in kcachegrind - mmerging a couple of cool tools. Picked up babes from school, customer calls until late.

face

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

LibreOffice 6.3 will be released as final in mid August ( Check the Release Plan ) being LibreOffice 6.3 Alpha1 the first pre-release since the development of version 6.3 started in mid November, 2018. Since then, 6390 commits have been submitted to the code repository and more than 1050 bugs have been set to FIXED in Bugzilla. Check the release notes to find the new features included in this version of LibreOffice.

LibreOffice 6.3 Alpha1 is already available for downloading here, for Linux, MacOS and Windows.

In case you find any problem in this pre-release, please report it in Bugzilla ( You just need a legit email account in order to create a new account ).

For help, you can contact the QA Team directly in the QA IRC channel or via Telegram.

Happy testing!!

Banner


face

If you occassionally do performance profiling as I do, you probably know Valgrind's Callgrind and the related UI KCachegrind. While Callgrind is a pretty powerful tool, running it takes quite a while (not exactly fun to do with something as big as e.g. LibreOffice).

Recently I finally gave Linux perf a try. Not quite sure why I didn't use it before, IIRC when I tried it somewhen long ago, it was probably difficult to set up or something. Using perf record has very little overhead, but I wasn't exactly thrilled by perf report. I mean, it's text UI, and it just gives a list of functions, so if I want to see anything close to a call graph, I have to manually expand one function, expand another function inside it, expand yet another function inside that, and so on. Not that it wouldn't work, but compared to just looking at what KCachegrind shows and seeing ...

When figuring out how to use perf, while watching a talk from Milian Wolff, on one slide I noticed a mention of a Callgrind script. Of course I had to try it. It was a bit slow, but hey, I could finally look at perf results without feeling like that's an effort. Well, and then I improved the part of the script that was slow, so I guess I've just put the effort elsewhere :).

And I thought this little script might be useful for others. After mailing Milian, it turns out he just created the script as a proof of concept and wasn't interested in it anymore, instead developing Hotspot as UI for perf. Fair enough, but I think I still prefer KCachegrind, I'm used to this, and I don't have to switch the UI when switching between perf and callgrind. So, with his agreement, I've submitted the script to KCachegrind. If you would find it useful, just download this do something like:

$ perf record -g ...
$ perf script -s perf2calltree.py > perf.out
$ kcachegrind perf.out




face

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

Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party.

YouTube privacy policy

If you accept this notice, your choice will be saved and the page will refresh.

And check out the suggested EasyHacks.

Then join us for a discussion via our #libreoffice-dev IRC channel on Freenode. You can ask experienced LibreOffice developers questions, and learn more about the language. We look forward to meeting you!


Sunday
19 May, 2019


face
  • All Saints; Fraser & Evelyn over for lunch, Frankie, Dorinda & daughter over for afternoon tea, lovely.

Saturday
18 May, 2019


face
  • Slugged in the morning, mail check, bit of Maths revision with H. Lunch. David over, out for a walk along a different stretch of a nearby (Devils) Dyke. Tea together, talked until late while the babes watched a movie.

Friday
17 May, 2019


face
  • Hacking on fixing a few issues, builds, customer call until rather late.

Thursday
16 May, 2019


face
  • Mail chew; interested to see the concerns from an apparently diverse group on the APPG definition of Islamophobia. I read the original as trying to avoiding racism being justified or concealed as anti-muslim prejudice which seems sensible. A shame if the controversy hinders positive improvement; would things have been improved by making the APPG more diverse initially ? The Secular Society and Southall Black Sisters were at least in both groups, but surely it would have been better to engage earlier to work together to solve the problem.
  • Admin, sync with Kendy. Lunch, catch up with Eloy. ESC call. Customer support call until late.

face

It’s the Month of LibreOffice, and we’re awarding sticker packs – and the chance to win cool mugs – to all contributors in the project! On this page we’re maintaining a list of names/usernames for people who’re helping out, and everyone there can claim a sticker pack at the end! We’ll also choose 10 people at random to get one of the mugs. So, how many packs have been awarded so far?

But there are still two weeks to go, so if your name isn’t there, check below to see how you can get involved! Many tasks only take 10 or 20 minutes, but make a big difference to the project. (And if you have already contributed this month, but your name isn’t there, email us with details and we’ll look into it.)

How to take part

There are many ways you can help out – and you don’t need to be a developer. For instance, you can be a…

  • Handy Helper, answering questions from users: over on Ask LibreOffice there are many users looking for help with the office suite. We’re keeping an eye on that site so if you give someone useful advice, you can claim your shiny stickers.
  • First Responder, helping to confirm new bug reports: go to our Bugzilla page and look for new bugs. If you can recreate one, add a comment like “CONFIRMED on Windows 10 and LibreOffice 6.2.3”. (Make sure you’re using the latest version of LibreOffice!)
  • Drum Beater, spreading the word: tell everyone about LibreOffice on Twitter or Mastodon! Just say why you love it or what you’re using it for, add the #libreoffice hashtag, and at the end of the month you can claim a sticker. (We have a maximum of 100 stickers for this category, in case the whole internet starts tweeting/tooting!)
  • Globetrotter, translating the user interface: LibreOffice is available in a wide range of languages, but its interface translations need to be kept up-to-date. Or maybe you want to translate the suite to a whole new language? Get involved here.
  • Code Cruncher, contributing source code: The codebase is big, but there are lots of places to get involved with small jobs. See our Developers page on the website and this page on the wiki to get started. Once you’ve submitted a patch, if it gets merged we’ll send you a sticker!
  • Docs Doctor, writing documentation: Another way to earn a badge is to help the LibreOffice documentation team. Whether you want to update the online help or add chapters to the handbooks, here’s where to start.

So dive in, get involved and help make LibreOffice better for millions of people around the world – and enjoy your sticker as thanks from us. We’ll be posting regular updates on this blog and our Mastodon and Twitter accounts over the next four weeks!


Wednesday
15 May, 2019


face
  • Mail chew, bit of hacking. Lunch with James Southey - nice to catch up.

face

Every year, The Document Foundation produces an Annual Report, detailing its activities in the projects and community. We’ll be posting parts of it here on the blog, while we prepare a final printed version…

Election of TDF Chairperson and Deputy

In February, the Board of Directors of The Document Foundation – during its first meeting of the new term – confirmed Marina Latini in the role of Chairwoman, and appointed Björn Michaelsen to the role of Deputy Chairman.

Marina said: “Our project is growing fast with contributors from several countries, and we need to focus much more on lowering the barriers to being a really welcoming community. I would like our community to become as inclusive as possible, and never leave out those who, just in appearance, look different to us. Openness is a state of mind.”

Björn, who had previously served as a Deputy on the Board, added: “I am encouraged to see strong contributors to the project as new candidates in this election, and hope to share the duty of serving with them, together providing a strong and reasonable voice of independent and unaffiliated input in the Board. Ultimately, I hope after this one last term I can confidently leave TDF’s Board with many new diverse and independent voices in all parts of the project and foundation, and retire back to spending my contributions more on – for instance – the source code again.”

New Advisory Board member

In May, TDF announced that BPM-Conseil, a company focused on open source business intelligence and based in Lyon (France), had joined the project’s Advisory Board. BPM-Conseil will develop the integration of LibreOffice with its business intelligence solutions Aklabox and Vanilla, and also create business intelligence-related extensions for LibreOffice.

BPM-Conseil is focused both on development of open source business intelligence solutions and on the related consultancy and integration activities. The company has a large roster of clients in France, such as the Ministries of Environment, Energy and Sea, Lyon Metropole, Nimes Metropole and City, La Rochelle Agglomeration, Haute and Basse Normandie, the Aveyron Department, and the University of Corsica.

Tenders

In 2017, TDF launched four tenders aimed at sharing knowledge about improving LibreOffice in several strategic areas, where the tasks are beyond the capabilities of independent volunteer developers. In 2018, companies selected to implement two of the tenders reported back on their work.

Firstly, Collabora was selected for the tender “improve image handling in LibreOffice (#201705-01)”. A new image life-cycle was developed, with simpler memory management for handling images and new swapping strategy. The results were incorporated into the LibreOffice 6.1 release – and a more detailed technical description of the work is on the blog, in order to share knowledge and experience from this project with the developer community and the general public.

The second tender, “implement HSQLDB binary format import in LibreOffice (#201705-03)”, was also assigned to Collabora and implemented by Tamás Bunth. He developed a mechanism to import database files with high fidelity from the HSQLDB


face
https://lh3.googleusercontent.com/Jw_BHWWDubfGASjfFszFu6q9VRXaELjjLun974YCt7pQv3P-WIKqkISu5GHwTNndCHi8jGqv_FvYTZFXdWfxASIzXbgw0Et-7rAQZ3LzxA5Ntxx0GTxRH3y4m3hOYVLMKAyXtCQECQ=w640
Figure 1. Chart in drawingML group shape in DOCX, imported into Writer

Years ago I posted about a large rework to where Collabora helped a customer to make Writer read the drawingML markup for DOCX shapes. You can read the various benefits of this switch in that article — but similar to other large reworks, this also broke some previously working corner-cases, where test coverage lacked.

One of these is charts in group shapes. This needs explicit handling, as Writer normally handles charts as TextEmbeddedObjects, while code that imports charts from OOXML is not specific to Writer. The fix just tells the generic drawingML import to use a Writer-specific service name for the charts.

This is available in LibreOffice master (towards 6.3).


Tuesday
14 May, 2019


face
  • Built ESC minutes, mail chew, calls.

face

Brussels in the night

This year’s FOSDEM (Free and Open source Software Developers’ European Meeting) has been held in in the beautiful city of Brussels (Belgium), as usual, on February 2 & 3, 2019. It was organised by volunteers to promote the widespread use of free and open source software..

This was my first FOSDEM as a deputy member of the MC, and a fresh member of the Collabora team.

I will try to give some information about my talks, and share my experience.

TDF Meetings, LibreOffice Hackfest & LibreOffice Dinner…

The first 2 days was spent on the LibreOffice Hackfest, MC & BoD joint meetings. Seeing all friends face to face was a pleasure. We discussed some important matters face to face, and had a great time together.

Did some work on the LibreOffice themes, and discovered the ugly truth of major Mozilla API change.

We also had a community night/dinner with the LibreOffice community members on Saturday. Had pleasant chats with many friends, and a nice ‘kosher/halaal’ meal with Lior (thank you again!).

It was also a nice adventure, chasing Indian/Eastern/Asian tastes with Mike. :)

The Hotel

This year, I stayed with the pack in Bedford. Its location is perfect, but you may feel the building’s age. (In good & bad ways.) I had the first night with a semi-functional heater in the room. Not very pleasant, considering the winter of Brussels. Next day they gave a second portable heater -yay! :)-, and I survived with those.

The Talks

Talk 1: Resurrecting Mozilla Themes for LibreOffice

Past, present, and the future of LibreOffice’s Personalization dialog.

LibreOffice has had the ability to use Mozilla Themes (Personas) for some time (Tools > Options > Personalization); but it kept breaking all the time, and never had an acceptable UX. Also tons of errors/warnings, and very slow search and apply processes almost brought it to the point of being killed for good. But I couldn’t let it die, started looking into the related code and the bug reports. Now it has a better UX/UI, and got most annoying bugs/crashers fixed, and is much faster.

I tried to present a summary about the journey so far, and the plans for the future.

Talk 2: Document Redaction with LibreOffice

Redaction in its sanitization sense (as distinguished from its other editing sense) is the blacking out or deletion of text in a document, or the result of such an effort. It is intended to allow the selective disclosure of information in a document while keeping other parts of the document secret. Typically the result is a document that is suitable for publication or for dissemination to others than the intended audience of the original document. For example, when a document is subpoenaed in a court case, information not specifically relevant to the case at hand is often redacted. Another example is patient information of hospitals, which is distributed to be used for research purposes


face

You are one of the people who have been around from the beginning of The Document Foundation, and one of the oldest members of the community (including the years of OpenOffice.Org). How were you involved in the project?

I was using StarOffice 5.2 and was contributing support on the French speaking users list. When Sun Microsystems was about to open source the code and create the OpenOffice.org project, they invited me to join and support the community. From there, I’ve been involved in various tasks like localization, quality assurance or documentation.

We are getting close to the 10th anniversary of the LibreOffice project, and the 20th anniversary of the FLOSS office suite. Which are the milestones of this long history?

I may not remember all of them, but I guess the creation of the Native Language projects with the French speaking one as a Proof of Concept in 2001. Then the many community supported projects such as marketing, documentation, etc.

And then of course, the birth of the LibreOffice project. Since then I’ve the impression that each year is a milestone ;-)

There have been so many exciting things to do in each corner of the project. The community is pushing a lot of good ideas and energy. Considering the work done on QA, UX/Design and marketing for the product or the community, the new help system and the size of our infra, we have achieved more than we could even imagine ten years ago!

You have been involved in the localization of the software since the very first version, and now you are coordinating the activity of native language projects. Can you talk about the localization activity?

Localization is a complicated task, and sometime tedious. LibreOffice is a big software with thousands of different strings. Localization happens at the end of the software making process, so the workload depends on development, UX/Design and marketing projects.

Recently, there have been changes on the strings format for almost the entire interface of each module, on the help system and more and more marketing activities. Each localization member should be very proud of his/her work.

We want to cover more languages because localization is a way to preserve those languages, preserve the local culture and give all users the opportunity to express themselves in their own language. This is where my activities lie: understand the needs of localizers, voice their concerns, update the workflow and try to make them happy to translate the different projects.

You have been a member of the team for almost six years, with a number of different responsibilities. From your point of view, how well did the project during this time?

Happy to say: fairly well :-) The task was not easy but I believe we are doing right. Some people would like to see more things happening, or the project going faster or further. But we are a diverse community with different cultures, different business or occupations and different time


Monday
13 May, 2019


face
  • Mail chew; admin, booked Eurostar to OW2Con in Paris next month. Trawled through task backlog. Tech mgmt call. Built ESC agenda.

Sunday
12 May, 2019


face
  • All Saints, Margarit back for lunch; played Badmington together in the sun in the garden; rested variously. Stories, bed.

Saturday
11 May, 2019


face
  • Slept in, out to Bury to pick up 'cello with fixed pegs & sat in the Bury Gardens & enjoyed the sun while M. and E. played. Home, lunch with H. out to pick up a tired N. read stories, put people to bed variously.

Friday
10 May, 2019


face
  • N. off on her DofE practice expedition. Admin, reference call, sync with Florian & Thorsten. More admin, sync with Miklos, Kendy & Andras. Hackery.

Thursday
09 May, 2019


face
  • Mail, catch-up with Florian, interview, sync with Eloy. ESC call, bit of hacking.

Wednesday
08 May, 2019


face
  • Interview, sales call, mail, extraordinary TDF BoD call.

Tuesday
07 May, 2019


face
  • Sync with Miklos, chewed though status reports; long tech mgmt call, more mail.

face

General Activities

  1. LibreOffice 6.2.3 was released on April 18, 2019
  2. László Németh (NISZ) fixed the Autocorrect capitalization of the English i’m
  3. László Németh (NISZ) continues his work with pasting table from Calc to table in Writer. Now Calc table with hidden rows pastes in Writer table without these rows
  4. Grzegorz Araminowicz (Collabora) improved SmartArt interoperability
  5. Stephan Bergmann added support for JRE installations with unknown java vendor
  6. Andreas Kainz ended update Sifr icon theme. Some review and feedback are welcome
  7. Heiko Tietze implemented a nice Tip-of-the-Day dialog that is prompted when LibreOffice is launched.
  8. Miklos Vajna (Collabora) has fixed many OpenGL bugs
  9. Mike Kaganski (Collabora) has fixed some Pivot table interoperability problems when import/export them into XLSX format
  10. Using the new Windows bibisect repo for 4.3 created by Cloph, Buovjaga was able to solve many old regression mysteries
  11. Gábor Kelemen (NISZ) closed many reports as duplicates, Chart issues in particular
  12. Noel Grandin (Collabora) improved different opening/saving performance hotspots for some documents in Writer, like documents with lots of bookmarks. Buovjaga decided to profile dozens of existing file saving issues just in case.
  13. Noel Grandin (Collabora) improved the opening time of different documents in Calc.
  14. Xisco Fauli found many crashes ( many of which are already fixed ) using UITests for mass testing
  15. Telesto and Buovjaga wrote instructions for Windows performance tracing using UiforETW
  16. New contributor Tasanim Mulla continued to do significant contributions in the area of confirming bugs
  17. Miklos Vajna (Collabora) keeps working on improving btLr text direction
  18. Tomaž Vajngerl (Collabora) has fixed some bugs affecting macOS
  19. Tamás Zolnai (Collabora) implemented Interoperable text-based form controls
  20. Muhammet Kara (Collabora) disabled the Firefox theme search
  21. Michael Stahl (CIB) added Undo for ToX Update

Reported Bugs

580 bugs, 63 of which are enhancements, have been reported by 339 people.

Top 10 Reporters

  1. Xisco Faulí ( 31 )
  2. andreas_k ( 31 )
  3. Mike Kaganski ( 19 )
  4. NISZ LibreOffice Team ( 16 )
  5. Andreas Gruhler ( 15 )
  6. Roman Kuznetsov ( 9 )
  7. Buovjaga ( 9 )
  8. Aron Budea ( 8 )
  9. Heiko Tietze ( 8 )
  10. Patrick Jaap ( 7 )

Triaged Bugs

585 bugs have been triaged by 87 people.

Top 10 Triagers

  1. Xisco Faulí ( 130 )
  2. Heiko Tietze ( 39 )
  3. Dieter Praas ( 31 )
  4. Buovjaga ( 30 )
  5. V Stuart Foote ( 25 )
  6. raal ( 25 )
  7. Roman Kuznetsov ( 24 )
  8. Oliver Brinzing ( 24 )
  9. Aron Budea ( 23 )
  10. mulla.tasanim ( 22 )

Resolution of Resolved bugs

520 bugs have been set to RESOLVED.

Check the following sections for more information about bugs resolved as FIXED, WORKSFORME and DUPLICATE.

Fixed Bugs

231 bugs have been fixed by 42 people.

Top 10 Fixers

  1. Caolán McNamara ( 31 )
  2. Mike Kaganski ( 17 )
  3. andreas kainz ( 14 )
  4. Noel Grandin ( 14 )
  5. Miklos Vajna ( 13 )
  6. Tor Lillqvist ( 10 )
  7. Tomaž Vajngerl ( 8 )
  8. Michael Stahl ( 8 )
  9. László Németh ( 5 )
  10. Balazs Varga ( 5 )

List of critical bugs fixed

  1. tdf#109376 Crash after accepting all changes from compared documents ( Thanks to Michael Stahl )
  2. tdf#120754 Crashes on UNDO ( Thanks to Caolán McNamara )
  3. tdf#123502 crash: use of “com.sun.star.ui.dialogs.FolderPicker” crashes ( Thanks to Mike Kaganski )
  4. tdf#123747 digital

Monday
06 May, 2019


face
  • Cooked breakfast, out for a longish walk in the countryside around Linton - refreshing. Bit of mail in the afternoon.

Saturday
04 May, 2019


face

The work around user experience often requires to create a minimal working example. Either users report an issue or request enhancements, the comparison with the current situation is necessary. LibreOffice has a built-in feature to create dummy text (type dt and press F3) but this function inserts only unformatted text.…


Tuesday
30 April, 2019


face

On vecation I ordinary have the best ideas. So this time I made an single line contextual toolbar for writer.

ContextualSingle.PNG

It’s how the single line toolbar should look like. One toolbar which is fully contextual. As one toolbar didn’t have that much space, you have the menubar for all available commands in LibreOffice.

It’s the most compact LibreOffice UI done on my smal Laptop screen (1366 x 768 px). But Contextual single work not only on small screens it’s flexible and suites all screen sizes.

contexts.png

Context Standard, Table, Image, Shape

If you’d like to test contextual single download the daily master build, enable experimental features (Menubar -> Tools -> Configure -> Advanced -> Enable experimental features) and change in Writer Menubar -> View -> User Interface -> Contextual Single.

To test download the daily build
https://dev-builds.libreoffice.org/daily/master/Win-x86@39/current

I broke the linux builds but now daily build for linux is available to check out the context single layout

https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86@87-TDF/current


Monday
29 April, 2019


face

The next release for LibreOffice will have a small but handy improvement for every macro developer, either experienced or beginner.

Hover the mouse on BASIC and Python code in the new Help pages and a tip shows that when you click your mouse, the code exerpt is copied in the system clipboard. You can paste in the BASIC IDE (Integrated Development environment) or any other text application in your system.



With this little feature, you save time of typing the exerpt to test in your IDE or document. Another alternative was to use a collateral file, however, collateral files with embedded macros is likely to trigger security warnings in most LibreOffice installations. Just copying the fragment is easier.

Happy Basic macro programming!
Happy Python macro programming!

face

Recently we at Collabora Productivity have made some substantial improvements to XLSX interoperability related to pivot tables, fixing many issues existed in Calc.

Personally I have committed these patches:

These changes allow our customers, and the whole LibreOffice user community, to enjoy better interoperability when using XLSX format. They will be available in LibreOffice version 6.3 later this summer; and they are immediately available for our customers in this week’s Collabora Office 6.0 update 28.

Thanks to our valuable customers who make these improvements possible funding the work!

Older blog entries ->