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.

27 May, 2020


Mark Rotteveel and documentation team migrated the first documents to asciidoc – Docbuilding Howto https://www.firebirdsql.org/file/documentation/html/en/firebirddocs/docbuildhowto/firebird-docbuilding-howto.html – Docwriting Guide https://www.firebirdsql.org/file/documentation/html/en/firebirddocs/docwritehowto/firebird-docwriting-guide.html ps: Since May/June 2020, the Firebird

25 May, 2020


To start with, tell us a bit about yourself!

Hi! I live in the Special Region of Yogyakarta, Indonesia, and work remotely on PT Sakti Kinerja Kolaborasindo (the office is in Bogor, West Java) as UI and Graphic Designer. Aside from being an active member of the Indonesian LibreOffice community, I am also one of the founders of the Gimpscape ID community (a design community focused on open source applications). Regarding hobbies – hmm, I have an interest in ancient manuscripts (Malay manuscripts), Kamen Rider, and really always enjoy detective, mystery, adventure, and comedy-themed drama films.

You can find me on Instagram, Twitter and Telegram.

Why did you decide to become a member of The Document Foundation?

The first reason is, because Ahmad Haris (he’s my boss in the office) “sudo’d” me to apply for membership :-) But to be honest, I was indeed very interested in becoming a member since the LibreOffice Conference Indonesia in Surabaya about two years ago.

By becoming a member, I think I can do things related to contributing to LibreOffice better than before. Being a member is a responsibility, in my opinion. Because it means I have to do my best from time to time for the LibreOffice community, both in Indonesia and outside. LibreOffice will get better if the community ecosystem is also good. Well, one of the tasks of members (in my mind) is to ensure that these communities can actively give feedback to LibreOffice, so that they can grow and develop better.

What are you working on right now?

At the moment I am still improving the LibreOffice Theme Changer extension (which I presented some time ago at FOSDEM), occasionally helping with translations, QA, managing Indonesian LibreOffice social media (Instagram, Twitter, and the blog), and inviting community members to learn how to be active contributors. For example, I invited two female members to work on two sets of icons named that we named Srikandi and LibreKids. Making these two icons is a form of learning to contribute to LibreOffice in terms of design.

When there isn’t too much work (both at office or at the university), I usually take time to create a video tutorial related to LibreOffice or other FOSS that I upload on my YouTube channel.

In addition, I and many other Asians (Haris, Frank, Shinji, Naruhiko, DaeHyun, and others) are currently spreading the spirit of Open Document format in the Asian region, through the LibreOffice Asia League.

Anything else you plan to do in the future? What does LibreOffice really need?

I really wanted to realize the LibreOffice for Kids task with Marina Latini – I heard she was one of the people who was also working on this topic. One of the reasons why LibreOffice is still less popular in Indonesia, compared to similar applications, is this: since elementary school, children have already been introduced to proprietary office applications.

I know that change cannot happen overnight, but if it does not start from now it will not

21 May, 2020

Paulo José Amaro published a blog post about new LibreOffice icons. He said in our Telegram design channel: "I've just posted an article on my personal blog with an extensive recap of my new icons development. This is an old practice from the past decades that I enjoy doing, and it really helps me don't get lost in the changes. So thank you guys for allowing me to quote your comments. Please, feel free to ask me to remove anything, if you change your mind". Just follow by link below.



Berlin, May 21, 2020 – The Document Foundation announces the availability of LibreOffice 6.4.4, the 4th minor release of the LibreOffice 6.4 family, targeted at technology enthusiasts and power users. LibreOffice 6.4.4 includes many bug fixes and improvements to document compatibility.

LibreOffice 6.4.4 represents the bleeding edge in term of features for open source office suites, and as such is not optimized for enterprise-class deployments, where features are less important than robustness. Users wanting a more mature version can download LibreOffice 6.3.6, which includes some months of back-ported fixes.

For enterprise class deployments, TDF strongly recommends sourcing LibreOffice from one of the ecosystem partners, to get long-term supported releases, dedicated assistance, custom new features and other benefits, including SLAs (Service Level Agreements): https://www.libreoffice.org/download/libreoffice-in-business/. Also, the work done by ecosystem partners flows back into the LibreOffice project, benefiting everyone.

LibreOffice’s individual users are helped by a global community of volunteers: https://www.libreoffice.org/get-help/community-support/. On the website and the wiki there are guides, manuals, tutorials and HowTos. Donations help us to make all of these resources available.

Availability of LibreOffice 6.4.4

LibreOffice 6.4.4 is immediately available from the following link: https://www.libreoffice.org/download/. Minimum requirements are specified on the download page. TDF builds of the latest LibreOffice Online source code are available as Docker images: https://hub.docker.com/r/libreoffice/online/.

LibreOffice 6.4.4’s change log pages are available on TDF’s wiki: https://wiki.documentfoundation.org/Releases/6.4.4/RC1 (changed in RC1) and https://wiki.documentfoundation.org/Releases/6.4.4/RC2 (changed in RC2).

All versions of LibreOffice are built with document conversion libraries from the Document Liberation Project: https://www.documentliberation.org.

Support LibreOffice

LibreOffice users are invited to join the community at https://ask.libreoffice.org, where they can get and provide user-to-user support. People willing to contribute their time and professional skills to the project can visit the dedicated website at https://whatcanidoforlibreoffice.org.

LibreOffice users, free software advocates and community members can provide financial support to The Document Foundation with a donation via PayPal, credit card or other tools at https://www.libreoffice.org/donate.

20 May, 2020


(Note: this is a section from The Document Foundation’s Annual Report 2019, which will be published in full in the coming weeks.)

The LibreOffice Conference is the annual gathering of the community, our end-users, developers, and everyone interested in free office software. Every year, it takes place in a different country and is supported by members of the LibreOffice commercial ecosystem.

In 2019, the conference was organized in Almeria by the Spanish community, and took place from Tuesday, September 10 to Friday, September 13. Most of the conference took place in the Universidad de Almeria, next to the sea, but some social events and meetups were held in the city itself.

Over 100 people from across the globe attended the conference; for several people, it was their first LibreOffice Conference and therefore the first time they could meet other community members in-person.

On Tuesday, before the main conference presentations got underway, there was a community meeting. Various members of the LibreOffice community joined for informal talks about marketing and localisation of the software, and what we can do to bring more people into the project.

Conference Tracks

Wednesday kicked off with the opening session: a welcome and introduction from the university’s staff; the “state of the project” (summarising the last 12 months of activity in LibreOffice); quick introductions to the TDF team, Board of Directors and Membership Committee; and messages from the sponsors.

During the conference, there were over 70 talks, workshops and feedback sessions on all manner of topics. Some talks focused on technical aspects, such as continuous integration, build systems and debugging, while others were geared towards the community and other non-technical matters – for instance, getting new contributors, how the Membership Committee works, and reports from events in Asia.

In addition, community members and developers gave talks about LibreOffice Online, the PDF export feature, SmartArt editing in Impress, reproducible builds, and a neural machine translation plugin for the suite. Videos of most of the presentations – and a quick summary of the whole conference – are available on TDF’s YouTube channel as a playlist:

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.

Additional Events

Outside of the conference tracks, various social events and meetups took place over the four days. On Tuesday evening we had a welcome party outside the accommodation, with drinks and light snacks. A beach dinner party was held on Wednesday, with more great local food to try, while a hackfest took place on Thursday, giving developers the opportunity to work shoulder-to-shoulder and discuss ideas in person.

On Friday, the conference organisers took us on a visit to the Alcazaba – the city’s castle – parts of which date back around 1,000 years. We had an entertaining guided tour with excellent views over the

19 May, 2020


Microsoft released Windows 7 on October 22, 2009, and ended the support on January 14, 2020. Technical assistance and software updates from Windows Update that help protect PCs are no longer available for the product.

Microsoft released the first Service Pack for Windows 7, also known as Windows 7 SP1, in February 2011, just a few days after the release of LibreOffice 3.3, the very first release after the fork. Only the first few versions of LibreOffice could run without Windows 7 SP1, which was turning Windows 7 into a stable operating system by solving 893 bug fixes and 77 security fixes.

In 2020, we still receive complaints from users who cannot install LibreOffice because the system asks them to install Windows 7 SP1. Nine years after the release of Service Pack 1 they are surprised when they are told to update their operating system. Although Windows 7 users are now a minority, the fact that there are people who have unconsciously used their completely unsecure PCs for years is a sign of a global security issue, as these users would not behave in a different way when using a different OS.

Anyway, users who are requested to update their PCs to Windows 7 SP1 can find more details about Windows 7 SP1 and the installation instructions on this Microsoft web page: https://support.microsoft.com/en-au/help/15090/windows-7-install-service-pack-1-sp1.


Firebird Project announces the second (and last) Beta release of Firebird 4.0, the next major version of the Firebird relational database, which is now available for testing on Windows and Linux platforms. This Beta release arrives with features and improvements already implemented by the Firebird development team, as well as with countless bugfixes. Our users are appreciated giving it a try and

Possibly, you are a great C++ developer or conversely you write your first strings in C++ and you want make LibreOffice better with pair (or more!) string of code.
Note, the same way uses for Help changes.
We'll suppose you already know what strings and in which file(s) of the LibreOffice source code you age going to change.
I'll talk here about using gerrit for that change making. 
So open your browser and type in address bar - gerrit.libreoffice.org. Click on SIGN IN in top right corner of the site. You'll see something like this:
For gerrit using you must have a TDF account, so just create it by that orange button ;-) Then login in to the site.
For making your change select Browse->Repositories on top of the site:

Then in the Filter field type one word "core" and click on link "core" in row below (if you want change Help, then type "help" instead "core" and click to "help"):
In left side of the site press Commands and then press CREATE CHANGE button by center of screen:
In opened window type in to Select branch for new change field word master and select "master" from drop-down list. Type something like tdf#bug_number <description> into Description area. Please use short description here, about only 75 characters on the first line; if you need a longer description, then add one empty line, and then add as many 75-character lines as you want. Press CREATE button.
Screen updates. Press EDIT in right top corner of the site:
There is a row with commands in right side of the site:
Press OPEN. In a new window type a name for file where you want make your change:
Please use a tooltip for selecting a full path to file! Click OPEN. It opens a source code editor:
Make your changes in the source code and click SAVE in right top site corner. Please wait, it shows a message like "All changes saved" in left bottom corner, then click CLOSE in right top site corner. You'll back to main site where you'll can see the changed file with your change. 
If your changes are in more than one file then just repeat operations from OPEN command as you need.
So, you made all your changes. Now you need someone who will review your patch. 
If you have a friend from LibreOffice developers (as me;-), then you can add it to reviewers directly. Click ADD REVIEWER in left side of the site and in first row of new window type his nickname or e-mail to add him in opening window. Then press START REVIEW there.
If you know nobody from LibreOffice developers then you can ask them to review your patch on #libreoffice-dev IRC channel in Freenode.net.
In that case click START REVIEW in main window and finally click PUBLISH EDIT in top right corner of the site.
Now you should just wait. You'll get one

18 May, 2020


LibreOffice communities around the world love to meet in person, share ideas, work on the software, and have a good time. Of course, “real life” meetings have been difficult in recent months, so communities are going online instead. Daniel A. Rodriguez, LibreOffice contributor based in Argentina and TDF Board member, tells us about an online meetup at the weekend:

On Saturday, the Hispanic LibreOffice community held an online event via TDF’s Jitsi instance, and streamed on YouTube. The event started 17:00 UTC and last almost 4 hours. More that 35 people took part, which benefited from the presence of several members who are well-recognised for their participation and collaboration in the project:

  • Celia Palacios, from Mexico, told us about the work of the documentation team.
  • Mauricio Baeza, also from the Aztec land, talked about the potential of macros using Python.
  • Xisco Fauli, from Spain, explained how quality control is applied to software in the development stages.
  • Ismael Fanlo, another Spaniard, presented pivot tables.
  • Gustavo Pacheco, from Brazil, talked about becoming a member and invited everyone to apply.

Meanwhile, I gave a tour of the collaboration possibilities presented by the project. This was, of course, an open event – free and aimed at anyone interested in the FOSS office suite per excellence. The event took place on Saturday May 16th on our Jitsi server. Also, thanks to our friend Servio from the open-source Latin community, we had a live broadcast through YouTube, now available as recording.

Thanks to everyone who took part! LibreOffice benefits enormously from the work of communities around the globe. If you’re reading this and want to boost LibreOffice in your country or language, check out our native-language projects and give us a hand!

15 May, 2020


Two weeks ago, we started a new Month of LibreOffice, saying thanks to contributors from our worldwide community. Everyone who helps out with our projects this month can claim a cool sticker pack at the end – and also has a chance to win a hoodie, T-shirt or mug!

So far 259 sticker packs have been awarded – click the link to see if your name/username is in the list. If not, read on and find out what you can do, to take part!

How to get your stickers

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 on Ask LibreOffice. 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.4.3”.
  • 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 your stickers.
  • 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.
  • Docs Doctor, writing documentation: Whether you want to update the online help or add chapters to the handbooks, here’s where to start.

We’ll be posting regular updates on this blog and our Mastodon and Twitter accounts over the next two weeks – stay tuned!

13 May, 2020


General Activities

  1. LibreOffice 6.4.3 was released on April, 16
  2. LibreOffice 6.3.6 was released on April, 30
  3. Ilmari Lauhakangas (TDF) published a couple of blogposts showing the progress done by the PPTX Team and the Macro Team in the last months
  4. Adolfo Jayme Barrientos and Steve Fanning made many Help improvements and cleanups
  5. Andreas Kainz continued to improve the galleries and dialog layouts. As a new task he took on improving Impress templates
  6. Rizal Muttaqin made many improvements in most of the icon themes and removed Tango icon theme from the core
  7. Miklos Vajna (Collabora) fixed import and export issues with PDF, SVG, HTML and DOCX. He also continued with padded numbering support in Writer
  8. Gábor Kelemen (NISZ) dropped Flash export filter and made many code cleanups
  9. Noel Grandin (Collabora) cleaned up the code in many places while improving readability
  10. Michael Weghorn fixed issues with the Android application and mail merge
  11. Luboš Luňák (Collabora) continued with the Skia engine integration and fixed a chart wizard freezing issue
  12. Justin Luth (SIL & Collabora) made many DOC/DOCX import improvements and did a lot of quality assurance work on DOC issues
  13. Balázs Varga (NISZ) fixed several chart label issues, related to both ODF and OOXML formats
  14. Samuel Mehrbrodt (CIB) fixed several OOXML-related issues, including one about remembering the last used file type
  15. Caolán McNamara (Red Hat) continued the crucial user interface backend work and did many cleanups and crash fixes
  16. Mike Kaganski (Collabora) fixed some regressions and made many code cleanups
  17. László Németh (NISZ) fixed many issues with DOCX tables and numbered list formatting
  18. Xisco Faulí (TDF) added nearly 40 unit tests for old bug fixes and added and improved many UI tests. He also created a script that helps to identify missing unittests. Check this wiki page for more information
  19. Stephan Bergmann (Red Hat) made many cleanups, build fixes and UI test fixes
  20. Szabolcs Tóth and Regényi Balázs (NISZ) fixed several DOCX import and export issues related to shapes
  21. Eike Rathke (Red Hat) fixed some issues with Calc functions
  22. Heiko Tietze (TDF) implemented a brand new About dialog
  23. Michael Stahl (CIB) killed Python 2 support with fire and fixed some DOCX import and export issues
  24. Tomaž Vajngerl (Collabora) did a lot of graphics handling improvements and cleanups
  25. Tor Lillqvist (Collabora) made improvements to debugging. He also made fixes and cleanups in code related to macOS and iOS
  26. Julien Nabet fixed exporting right-to-left content as HTML, the behaviour of Calc’s switch function, a problem with function wizard, an SQL parser issue and some crashes
  27. Tünde Tóth (NISZ) implemented chart axis position type property
  28. Pranam Lashkari (Collabora) fixed some issues with gradient fill
  29. Attila Bakos (NISZ) fixed some issues with graphical objects in DOCX files
  30. Tibor Nagy (NISZ) fixed a spacing issue with grouped shapes in DOCX files
  31. Thorsten Behrens (CIB) improved handling of JPEG images in the PDF export process
  32. Aditya Sahu added unit tests for creation of


(Note: this is a section from The Document Foundation’s Annual Report 2019, which will be published in full in the coming weeks.)

2019 was a busy year for The Document Foundation, with elections for the Chairperson and Deputy, new staff members, and other activities.

Election of new TDF Board of Directors

The Board of Directors (or “BoD”) is the Foundation’s Board of Directors, the main administration of the Foundation’s projects and teams. Directors are directly elected by Community Members. The Board of Directors consists of seven (7) members and two (2) deputies. The Board of Directors may launch any other teams or committees ad hoc if necessary. In December, an election was held for a new Board.

Gabriele Ponzo, Chairman of TDF’s Membership Committee, announced the results:

The vote preliminary results were in conflict with § 8 IV of our statutes, as three candidates – Michael Meeks, Cor Nouws and Jan Holešovský – have the same affiliation. The elected candidates and the membership committee discussed the options to resolve the conflict and Jan Holešovský decided to not accept the role. The Membership Committee would like to thank Kendy for his support in this and especially for his longtime work in the board!

Elected as member of the Board of Directors, in this order, were: Michael Meeks, Thorsten Behrens, Franklin Weng, Daniel Armando Rodriguez, Cor Nouws, Lothar Becker and Emiliano Vavassori. Elected as deputies of the Board of Directors were: Nicolas Christener and Paolo Vecchi.

Advisory Board members and meetings

The Document Foundation relies on its Advisory Board Members in order to receive advice and support. The Advisory Board’s primary function is to represent The Document Foundation’s supporters and to provide the Board of Directors with advice, guidance and proposals. Members are the Free Software Foundation Europe (FSFE), Software in the Public Interest (SPI), UK Government Digital Services (joined in 2019), City of Munich (Landeshaupstadt München), BPM-Conseil, Kopano b.v., GNOME, Google, Adfinis SyGroup (joined in 2019), RPA RusBITech, KDE e.V., the Free Software Foundation (FSF), Collabora, CIB Software and Red Hat.

Throughout the year, TDF had regular calls with representatives of the Advisory Board. Staff and Board members at TDF provided updates on the foundation, software and community, and described plans for the future. Advisory Board members were invited to provide valuable feedback on TDF’s activities, and various ideas and proposals were discussed. TDF would like to express its thanks to all Advisory Board members for their help.

New staff members

In 2019, two new staff members joined The Document Foundation’s team. Ilmari Lauhakangas (aka “buovjaga”) was well known in the community for his work in Bugzilla, and joined TDF as a Development Mentor. He described his work and plans in an interview here on the blog.

In addition, Stefan Ficht joined as an Administrative Assistant, helping Florian Effenberger (Executive Director) and the rest of the team with various tasks.

Highlights of activities

Throughout the year, TDF supported various campaigns and

12 May, 2020


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

LibreOffice 7.0 will be released as final at the beginning of August, 2020 ( Check the Release Plan ) being LibreOffice 7.0 Alpha1 the first pre-release since the development of version 7.0 started in the beginning of June, 2019. Since then, 6213 commits have been submitted to the code repository and more than 1200 bugs set to FIXED in Bugzilla. Check the release notes to find the new features included in this version of LibreOffice.

LibreOffice 7.0 Alpha1 can be downloaded from here for Linux, MacOS and Windows, and it can be installed alongside the standard version.

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.

LibreOffice is a volunteer-driven community project, so please help us to test – we appreciate it!

Happy testing!!

Download it now!


According to our estimates, worldwide there are around 150 million LibreOffice users on Windows. And when we say worldwide we mean worldwide, as according to the origin of downloads we have users in every continent including Antarctica.

As a consequence, we get a large amount of questions related to LibreOffice on Windows. Many of these questions are about the installation process, because there are several issues which prevent the user to get the expected positive user experience. Unfortunately, the majority of these questions are related to Windows issues and not to LibreOffice issues.

When a issue is related to Windows, the Microsoft operating system will show a specific message, under the form of either an error number (for instance, “Error 1303”) or a specific sentence (for instance, “The program can’t start because api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer”).

Of course, over the years we have built a small knowledge base on the subject, and we have published the results on one page on the wiki, in the area of frequently asked questions: https://wiki.documentfoundation.org/Faq/General/General_Installation_Issues_(Windows). Another useful resource is the Ask LibreOffice website (https://ask.libreoffice.org/en/questions/), where users can search for a solution.

The best resources, though, are provided by Microsoft, and are all multilingual, and are the Microsoft Support website (https://support.microsoft.com/) and the Microsoft Community website (https://answers.microsoft.com/en-us). For instance, a search for “Error 1303” provides around 20 answers, with comments, on the Ask LibreOffice website, and hundreds or even thousands of answers on the two Microsoft websites.


It’s now easier to check the status of your /libreoffice/online patches

Recently the CI (continuous integration) infrastructure for Online has been made accessible via the internet. Now developers from outside Collabora can directly check the status of their patches and builds.


Already for a while there was a Jenkins instance that checks patches on gerrit for the online-project (and our other projects), before they are submitted to cgit.freedesktop.org/libreoffice/online/
This service is now running on dedicated hardware, what allows us to make it accessible directly from the internet. Links pointing to this server in TDF gerrit will work from now on.


How to participate in the project

This growing  access to our development makes it easier to join the project. Which we of course encourage 🙂  Therefore… read more about participating in developing LibreOffice online here!

If you have any questions, please leave a message here.

The post Online development CI accessible via the internet appeared first on Collabora Productivity.

11 May, 2020

  • Planning call, E-mail left & right; pleased to see the nice Demo Servers to make it much easier for people to try out an integration using any server, with more easy integrations coming.
  • Plugged away at admin & E-mail much of the day until late; Mondays!


Thanks to SUSE who made this possible, now we have glow effect on objects in upcoming LibreOffice 7.0. Collabora Productivity engineers Tamás Bunth and myself together have implemented it for shapes and pictures.

Below are some screenshots of a PPTX slide with glow samples collected from the relevant bug report:

How it was in 6.4
How it looks like in master towards 7.0
Reference look

What puzzles me is why fontworks’ (right bottom) glow is not shown in the reference, although the effect is present in its properties. Somehow now LibreOffice seems to support glow in fontworks better 😉

Glow on pictures is only implemented in Impress and Draw. Glow on shapes is available in all modules.

10 May, 2020

  • Up late, relaxed, sung & had a sermon later, Pizza lunch, out for a walk around a nearby golf-course; Parks & Rec.

09 May, 2020

  • Lots of tidying, cleaning, chiseled tarmac out of the sideway threshold. Fitted brass slides turned by N. and M. to velux blind with new string, works like a charm. Walked with babes.

08 May, 2020

  • Partner call, staff call, TDF board call, finally a bit of hackery. Lock, Stock & 2 Smoking Barrels.


Draw/Impress now has support for exporting larger page sizes into PDF. The previous limit was 200 " (508 cm), and now practically there is no such limit.

First, thanks Vector who made this work by Collabora possible.


You can use Draw with a document which has a single page, which more or less acts as a canvas with unlimited size to handle vector graphics. The current limit of such a canvas in size is 600 x 600 cm. (And that can be increased further if there is demand without too large problems.)

Exporting such a document to PDF is a different matter, though. The specification (up to, and including version 1.5) says that the unit to specify sizes is points, and the maximum allowed value is 14 400. This means that there is no markup to describe that your page is 600 cm wide. PDF 1.6 (and newer versions) introduce a UserUnit markup to allow unlimited page size, and now Draw (and other apps) can use this to describe the increased size.

Another use-case can be a large sheet in Calc, exporting it to a single PDF page, so you can pan around easily on a touch device. If you have enough rows, then getting rid of this limit is helpful to deal with the large page height.

Results so far

Here is how a large page looks like now in Draw and then in Adobe Reader:

Figure 1. Export of 6m-wide.odg to PDF

You can see how both Draw and Adobe Reader show that the page width is larger than 200 ".

How is this implemented?

If you would like to know a bit more about how this works, continue reading… :-)

  • The PDF export already converts from an internal unit (e.g. Draw uses 100th millimeters, Writer uses twips) to PDF’s unit

  • The trick is that now PDF’s unit is no longer points all the time, but we can dynamically switch to a larger unit as needed.

Here is how the PDF markup looks like for a 600 cm wide page:

1 0 obj
<</Type/Page/Parent 4 0 R/Resources 11 0 R/MediaBox[0 0 8503.93700787402 396]
/UserUnit 2/Group<</S/Transparency/CS/DeviceRGB/I true>>/Contents 2 0 R>>

Notice how we still avoid values larger than 14 400, but now the UserUnit says that 1 unit means 2 points.

Want to start using this?

You can get a snapshot / demo of Collabora Office and try it out yourself right now: try unstable snapshot. Collabora is a major contributor to LibreOffice and all of this work will be available in TDF’s next release too (7.0).

07 May, 2020

  • Partner call, legal call, managed to get a good few fixes and improvements worked on until late.

06 May, 2020

  • Sales & Marketing call, visited a nearby house to inspect it. Lunch, call with Andras & Yunusemre, got cut & paste URLs sorted for proxy bits.

So, I just show you two screenshots with current view of LibreOffice's 7.0 windows installer:

Looks nice.

05 May, 2020

  • Sync with Eloy, mail chew, admin. Catch up with Kendy.

04 May, 2020

  • Mail chew, planning call, poked at various admin-console bugs.

03 May, 2020

  • Up late. Worship & sermon with the babes, lunch. Out for a longish walk, back to relax, large dinner, slugging, bed.

02 May, 2020

  • Mending: replaced bathroom extractor fan, coat-hook downstairs, taught M. and N. to use a lathe to turn up a replacement brass Velux blind slide. Played BosWars with E.
  • Out for a short walk with J. - met Mike & Thea in passing; shared their news. Watched Parks & Recreation together.

Older blog entries ->