The Document Foundation Planet

 

January 26, 2021

Official TDF Blog

The round-the-world trip to fix a bug

A little story: The beauty of planet-wide collaborative work in LibreOffice

Mrs. Vera Cavalcante (@veracape), from Brazil, a long-time contributor for the Portuguese documentation on LibreOffice, was reviewing the translation of the Calc Guide and double-checking the translated text, with respect to the current user interface and the Help pages. Vera noticed that the Help pages on conditional formatting were not correct any more, and reported in the Brazilian team Telegram group (Bugzilla is still very hard for non-native English speakers).

The message hit Olivier Hallot (@ohallot) from the LibreOffice documentation coordination team (and Brazilian community member), who reported the bug in LibreOffice’s Bugzilla, for later fixing. LibreOffice’s outstanding quality depends on good quality and numerous errors reports to be submitted properly, for improvements and fixing defects. There is no point leaving a bug unreported.

The topic was of special interest of Roman Kuznetsov (@kompilainenn) from Russia, who already wrote documentation about conditional formatting. Roman wrote the fix, and submitted a patch in Gerrit (the service that controls the code corrections in LibreOffice)…

…and Adolfo Jayme Barrientos (@fitojb) from Mexico reviewed and approved the patch for merging in the main Help code.

End result: LibreOffice’s Help page fixed!

by Olivier Hallot at January 26, 2021 01:06 PM

January 25, 2021

Official TDF Blog

Community Member Monday: Felipe Viggiano and Zhenghua Fong

Today we’re talking to two people who’ve recently decided to become members of The Document Foundation, the non-profit behind LibreOffice. First up, Felipe Viggiano…

Hey Felipe, tell us a bit about yourself!

Hello there! I’m writing from the state of São Paulo, in Brazil. I’m an electrical engineer and have been working with LibreOffice for several years. Despite all this time, I started to contribute only a few months ago.

What are you working on right now?

Right now I’m working with the Documentation Team, mainly on the update of the Calc Guide with the new features in LibreOffice 7.0. Working with the team has been a huge learning opportunity, and the other team members are always there for a little help when needed.

Why did you decide to become a member of TDF?

The reason I applied for membership is to try to contribute a little more to the project in other areas.

Anything else you plan to do in the future?

In the future, I would like to start contributing more with others teams, and with TDF in order to help increase LibreOffice’s success. In my opinion, LibreOffice needs to be better known – we have a great free office solution that attends the majority of the requirements of the general public, but, at least in Brazil, many people are not aware of this!


Next us is Zhenghua Fong, who works on improving LibreOffice’s compatibility with other office suites…

Tell us a bit about yourself!

I’m part of a team of three people from Fuzhou, a coastal city known for its hot springs, in the Fujian province in China. When we are not coding, we like jogging in the nearby park. Every year we have company-wide Half Marathon Run around the main campus. Around 7,000 employees compete in the run and other sporting events.

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

As we’re an education tech company, documents are at the core of our business. LibreOffice works great for us. Recently, we have add a whiteboard feature to our product with the help of LibreOffice Online.

What are you working on in the LibreOffice project right now?

Compatibility is the area we are working on. Because large parts of the population still use Microsoft Office-based document formats, it’s important to our users that they are able to open documents and get them right the first time.

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

Performance. We find the performance of our product has room for improvement, especially when compared against Microsoft Office and WPS from Kingsoft.

Thanks to Felipe and Fong for all their contributions! Our worldwide community is what makes LibreOffice strong – everyone is welcome to join and find out what they can do for LibreOffice!

by Mike Saunders at January 25, 2021 10:07 AM

January 24, 2021

Michael Meeks

2021-01-24 Saturday

  • Up lateish, back to slides, worked through the day. Put family to bed, catch up with Ash, reviewed & merged some patches. Listened to LCA talks, interesting.

January 24, 2021 12:17 AM

January 23, 2021

Michael Meeks

2021-01-23 Friday

  • Admin, sync with Eloy, and Kendy, mail catch-up. Poked at some calc profiles & fixed a couple of rather silly drop-offs. Plugged away at the next invalidation multiplexing issue. Worked late on slides for LCA.

January 23, 2021 09:00 PM

January 22, 2021

LibreOffice Design Blog

How to make a star with LibreOffice

Some time ago we asked the people how they use LibreOffice Draw. And while the expectation was that this module receives only low appreciation the opposite is true. LibreOffice Draw is used to create block diagrams for BPMN processes, mindmaps or technical drawings, to build complex vector drawing for network topology, electrical circuits, floor plans or UI mockups, as a desktop publishing tool to design posters, flyers, business cards, and as a tools to load PDFs for editing.…

by Heiko Tietze at January 22, 2021 10:23 AM

January 21, 2021

Tomaž Vajngerl

Built-in "Xray" like UNO object inspector – Part 1

When developing macros and extensions in LibreOffice it is very useful to have an object inspector. With that tool you inspect the object tree and the methods, properties and interfaces of individual objects to understand its structure. There are quite some different object inspectors available for LibreOffice as extension. Probably the best known is called “XrayTool”, but there were also others like MRI, which was build for a similar purpose and various other more simple object inspectors (for example one is provided as an code example in ODK).

As a tool like this is very valuable it makes sense that it would be provided out-of-the-box by LibreOffice without the need for the user to get it separately. Also the user could even be unaware the such a tool exists.  For this reasons The Document Foundation (TDF) put up a tender to create a built-in Xray like UNO object inspector, which was awarded to Collabora and we are now in the process of implementing it.

Thank you TDF and the donating users of LibreOffice to make the work on this tool possible.

The Plan

The major gripe with Xray and other tools is that the user needs to go into the macro editor and run a the script with the inspecting object as the parameter. 

For example to inspect the root UNO object:

Xray ThisComponent

or for example to inspect a specific (first) Calc sheet:

Document = ThisComponent
AllSheets = Document.getSheets()
MySheet = AllSheets.getByIndex(0)
Xray MySheet

Figure 1: Watch window in the macro editor

We can do much better than this. So the idea is to have a object inspector tool as a dockable bottom widget, very similar to “developer tools” that you can find in popular web browsers.

The left hand side of the tool will have a subset of the document model (DOM) presented as a tree and on the right hand side a object inspector view that will show the current UNO object’s properties, methods in a tree view that is taken from the Watch window in the LibreOffice macro editor (see Figure 1). When the user would select an UNO object in the DOM tree view (left-hand side), the object inspector (right-hand side) would show it.

An additional functionality that is present in developer tools in web browsers is the ability to point & click an object directly in the document, which can then be inspected in the developer tool. A similar functionality to this will be possible in LibreOffice, where you will be able to select an object in the document, that is then be shown in the object inspector (right-hand side).

Implementation so-far

The implementation has been divided into 4 parts:

  1. Introduce a new dockable window on the bottom of the UI.
  2. DOM tree view (left-hand side)
  3. Implement point&click functionality.
  4. Object inspector view (right-hand side)

Currently the 1. and 2. part have been implemented, so this blog post serves as a report of the work that has been done until now. For 3. and 4. part, a limited subset of the functionality has been  already implemented, but it is not yet expected to work correctly and may change a lot in the future.

Dockable window

Figure 2: Development Tool in the menu

The dockable window has been added to all components of LibreOffice, which can be enabled in the menu (see Figure 2) under Help / Development tool (this location and the name can still change). The development tool code is all contained under svx/source/devtools/ where the docking window is implemented in DevelopmentToolDockingWindow.cxx.

DOM tree view (Left-hand)

Figure 3: Development tool dockable window

The idea of the DOM tree view is to provide a useful subset of the DOM objects, that the user can quickly access and inspect. Without this, the users would have to traverse to the objects they are interested in inside the object inspector itself, which may not be as straight forward to the users that aren’t familiar with the DOM, and even if they are, the DOM subset still makes it easier.

The DOM tree view as currently implemented (see Figure 3), has a root “Document” element always available, which represents the root document UNO object, from where you can traverse to any other relevant UNO object in the DOM tree. Other available objects depend on the component.

In Writer the available objects are:

  • Paragraphs
  • Shapes
  • Tables
  • Frames
  • Graphic Objects
  • Embedded Objects (OLE)
  • Style Families & Styles

In Calc:

  • Sheets
  • Shapes (per sheet)
  • Charts (per sheet)
  • Pivot Tables (per sheet)
  • Style Families & Styles

In Impress and Draw:

  • Pages / Slides
  • Shapes (per page / slide)
  • Master Slides
  • Style Families & Styles

If there are other object(s) you would like to see in the DOM tree view, please let me know.

The main implementation file for the left-side DOM tree view is DocumentModelTreeHandler.cxx in the svx/source/devtools/ folder. For each node of the tree view, there is an object attached (subclass  DocumentModelTreeEntry) to the node, which is responsible to fill the child nodes and provide the UNO object of the current node. The whole DOM tree view is populated on-demand, when the tree is expanded. This makes sure that we don’t take a lot of time inserting the whole object tree before-hand and have a more up-to-date view of the UNO objects. 

All the code is present in the LibreOffice master repository. Please try out the development tools in a recent daily build. Any comments or suggestion are welcome. 

Next part - point&click functionality

Partial support for the point&click has already been added. There is a selection listener added, which remembers what the selected object in the document is. This object is the available in the DOM tree view under the name “Current Selection”. If the user clicks on the node in the tree view, then the right-hand object inspector shows the UNO object.

To be continued..

by Tomaž Vajngerl (noreply@blogger.com) at January 21, 2021 01:39 PM

January 20, 2021

Michael Meeks

2021-01-20 Wednesday

  • Mail chew, sync with Andras, monthly all-hands, slides, testing, TDF Advisory Board call. Recorded a collaboration dev-room talk for FOSDEM - fun.

January 20, 2021 09:00 PM

LibreOffice QA Blog

LibreOffice 7.1 RC2 is available for testing

LibreOffice 7.1 will be released as final at the beginning of February, 2021 ( Check the Release Plan for more information ) being LibreOffice 7.1 RC2 the fourth pre-release since the development of version 7.1 started at the end of May, 2020. Since the previous release, LibreOffice 7.1 RC1, 87 commits have been submitted to the code repository and 64 bugs have been fixed. Check the release notes to find the new features included in LibreOffice 7.1.

LibreOffice 7.1 RC2 can be downloaded from 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 as both channels are bridged to each other.

LibreOffice is a volunteer-driven community project and your help is much appreciated.

Download it now!

by x1sc0 at January 20, 2021 08:29 AM

January 19, 2021

Michael Meeks

2021-01-19 Tuesday

  • Slides, monthly management call, HDMI faceplate arrived & finally got the lounge into some shape. Sync with Kendy, worked on FOSDEM slides.

January 19, 2021 09:00 PM

January 18, 2021

Michael Meeks

2021-01-18 Monday

  • Planning call, catch up with Tor, Florian, Cor, poked ESC bits, admin.

January 18, 2021 09:00 PM

Official TDF Blog

Join the LibreOffice Team as a Development Mentor (m/f/d), 20-40h per week, remote (#202101-01)

The Document Foundation (TDF) is the non-profit entity behind the world’s leading open source office suite, LibreOffice. We are truly passionate about free software, the open source culture and about bringing new companies and people with fresh ideas into our community, especially as we are about to enter the second decade of our project.

To grow the LibreOffice community and to enlarge the associated ecosystem, together working on office productivity for over 200 million users around the globe �, we’re searching for a Development Mentor (m/f/d) to start work as soon as possible.

As our future development mentor, you work with a great team of currently eleven to:

  • Attract new contributors by promoting the LibreOffice project

  • Identify and onboard them, by building relationships between new coders and the community

  • Introduce them to our communication channels where they meet fellow co-hackers

  • Affirm and encourage everyone’s contribution and show community members ways to grow

  • Bring skilled contributors in contact with existing experts in the various fields for even deeper learning

To succeed in this new role, you ideally already have some of the following skills:

  • Previous experience in remote work

  • Self-driven and an excellent team player, who is interested in working as part of our team

  • Patience and kindness to work with potential contributors of various skill levels

  • Been a long-time contributor to one or more FLOSS communities, with coding experience in at least one FLOSS code base – ideally LibreOffice, of course! :)

  • Demonstrable C++ coding experience of at least five years, or a comparable language like C#, plus active knowledge of at least one more language used in LibreOffice, like Python or Java

  • Excellent communication abilities, that help you transport your enthusiasm for LibreOffice and our community

  • A quick learner with good self-starting capabilities (demonstrable quick learning is a good compensation for immediate lack of LibreOffice knowledge!)

  • Experience in web development and/or mobile technologies is a plus

  • When possible again, willingness to regularly travel to Hackfests and conferences in Europe and globally. In the meantime, you are excited to create virtual events on a regular basis, with the excellent infrastructure offered by TDF.

  • Fluent written English for e-mail and chat, with good speaking and comprehension is a mandatory requirement. Fluency in another widely-used language like e.g. Spanish or Mandarin would be considered an advantage.

Here’s how a typical day in your new role might look like:

You start your day by looking in Gerrit for unreviewed patches. There, you help to onboard new contributors, by positively reviewing their code contributions, which also involves syncing the coding style of their patches with LibreOffice’s. Your goal is to work with them and help them grow their skills where needed, like C++ programming, design and coding, and encourage them to bring up their own ideas how to implement a new feature or fix a bug in the codebase – in short, you are their guide to make their ideas become a reality. Especially for new contributors, you will introduce them not only to our community culture, but also to our variety of tools, which you regularly review and make proposals to improve or unify them.

One way to attract new contributors is to lower the entry barriers. You design and define easy tasks (“Easy Hacks�) for coders, that help them to learn about the code, our toolchain, the LibreOffice build system and leads them step by step into growing mature in the repository, so that they can ideally work on more advanced tasks.

Apart from the individual mentoring, an important part of your role is about knowledge sharing with the general public by writing and updating our technical documentation, like the developer guide, our wiki articles and also code comments. You master that thanks to your ability to write comprehensive texts for technical people.

The role you will fill gives you a lot of freedom and flexibility to shape our mentoring program. That requires you to work goals-oriented and with a laser-sharp focus to grow excellent LibreOffice core contributors. As our successful development mentor, you will come up with creative ways of finding and attracting volunteers who will stay in the community!

All jobs at The Document Foundation are remote jobs 🌟, where you can work from your home office or a coworking space. The work time ⌚ during the day is flexible, apart from very few fixed meetings. The role is offered both as part- or fulltime, with the option to grow the hours later, just as you grow into your role.

Are you interested? Get in touch! We aim to schedule the first interview within two weeks of your application. You can also approach us anytime for an informal chat to learn about the role or in case of questions – and you can directly join our virtual FOSDEM DevRoom on February 7 to see what’s going on in the community!

TDF welcomes applications from all suitably qualified persons regardless of their race, gender, disability, religion/belief, sexual orientation or age. Don’t be afraid to be different, and stay true to yourself. We like you that way!

We are looking forward to receiving your application, including information about you, when you are available for the job, and of course your salary expectations. Please send us an e-mail to mentor.application@documentfoundation.org by February 18, 2021. A final decision for the role will be made by March 18, 2021.

Note: We do not accept agency resumes. Please do not forward resumes to any recruiting alias or employee.

by Mike Saunders at January 18, 2021 05:02 PM

January 14, 2021

CIB News

CIB gründet allotropia software GmbH aus

CIB labs GmbH gründet neues Startup allotropia software GmbH München und Hamburg – 13. Januar 2021 Mit der zunehmenden Digitalisierung von Prozessen und Workflows werden datenschutzkonforme, universell einsetzbare und innovative Softwarelösungen immer wichtiger. CIB gründet passend dazu das Startup allotropia software GmbH aus, um an innovativen OpenSource-Lösungen für die digitale Zusammenarbeit zu arbeiten. Als einer … CIB gründet allotropia software GmbH aus weiterlesen

Der Beitrag CIB gründet allotropia software GmbH aus erschien zuerst auf CIB blog.

by CIB Marketing at January 14, 2021 01:47 PM

allotropia

CIB spins off new allotropia software GmbH

CIB labs creates startup company allotropia software GmbH.

Munich and Hamburg, Germany – January 13th, 2021

With digitalisation and IT process automation picking up speed significantly, CIB labs GmbH spins off startup company allotropia software GmbH to work on innovative opensource solutions for the digital collaboration age.

One of the leading companies behind the LibreOffice commercial ecosystem, as well as an established software vendor in the digital business process management domain (BPM) with billions of documents generated every year, CIB sees significant value-add in having state-of-the-art and industry-leading opensource productivity software available.

“With everyone from SMBs to governments now going fully digital, we see significant demand for integrated, secure, and GDPR-conforming digital document lifecycle solutions,” says Uli Brandner, CEO and owner of CIB labs. “We have continuously invested into LibreOffice to play an important role in our solution stack, and are now taking the next step by setting up a dedicated company with a laser-sharp focus on delivering fully cloud-based versions – in-line with our ongoing push for browser-based products.
Being able to build on the multi-decade value of existing OpenSource solutions, as well as the equally many years of experience of our LibreOffice engineering team there, gets us both a significant head start, and the confidence to deliver quality solutions.”

LibreOffice engineering consultancy and “LibreOffice powered by CIB” will remain an important part in CIB’s portfolio, now being served and further improved by allotropia software GmbH. “For our customers, this generates the win-win-win situation of having an established, rock-solid partner like CIB, delivering state-of-the-art opensource software, plus the agility of an innovative startup developing new solutions”, adds Uli Brandner.

“We are excited to be given the opportunity to focus on LibreOffice and related OpenSource productivity tools, and continue the 30 years journey this software has travelled – onwards to be even more ubiquituous, pluggable and portable. What has remained true since at least 20 years – is that OpenSource software market share keeps growing & companies innovating around and on top of it. We’ll happily ride that wave!” says Thorsten Behrens, CEO and owner of allotropia software GmbH.

About allotropia software GmbH

allotropia logo

The company allotropia software GmbH provides services, consulting and products around LibreOffice and related opensource projects. Founded in 2020 with 5 long-time developers of the project, its stated mission is to bring LibreOffice to shine – in as many different shape and form as necessary to serve modern needs towards office productivity software.
Allotropia software GmbH is headquartered in Hamburg, Germany at the birthplace of the OpenOffice/LibreOffice code and project. For more information, visit allotropia.de or follow @allotropiaEN on Twitter.

About CIB

The CIB group specializes in document lifecycle management applications. Renowned financial institutions and insurance companies, public administrations as well as international industrial companies are using CIB software to manage their correspondence on a daily basis. Over 500 million documents are produced per year using CIB technology. The company has 180 employees and locations in Munich, Karlsruhe, Münster, Hannover, Nuremberg, Hamburg, Las Palmas de Gran Canaria, Valencia, Santa Cruz de Tenerife and Minsk.
For more information, visit libreoffice.cib.de or follow @CIBsoftwareGmbH on Twitter.

by allotropiasoft at January 14, 2021 12:25 AM

CIB gründet allotropia software GmbH aus

CIB labs GmbH gründet neues Startup allotropia software GmbH

München und Hamburg – 13. Januar 2021

Mit der zunehmenden Digitalisierung von Prozessen und Workflows werden datenschutzkonforme, universell einsetzbare und innovative Softwarelösungen immer wichtiger. CIB gründet passend dazu das Startup allotropia software GmbH aus, um an innovativen OpenSource-Lösungen für die digitale Zusammenarbeit zu arbeiten.

Als einer der führenden Firmen hinter der Bürosuite LibreOffice, und als etabliertes Softwarehaus im Bereich Geschäftsprozessmanagement (BPM) – mit dessen Lösungen pro Jahr mehrere Milliarden Dokument generiert werden – sieht CIB erhebliche Mehrwerte, Standardsoftware vom Kaliber LibreOffice als Teil des Softwarebaukastens verfügbar zu haben.

“Mit der auch durch die Pandemie beschleunigten digitalen Transformation von Wirtschaft und öffentlichem Sektor sehen wir erhebliche Nachfrage nach integrierbaren, sicheren und DSGVO-konformen Digital Document Lifecycle-Lösungen,” sagt Uli Brandner, Inhaber der CIB Gruppe. “Wir investieren seit vielen Jahren in LibreOffice, als Baustein unserer Lösungen, und gehen nun den nächsten Schritt mit der Ausgründung einer dedizierten Firma, welche sich ausschließlich auf OpenSource-Cloudlösungen fokussieren kann.
Wir sind überzeugt, dass uns die Jahrzehnte Erfahrung des allotropia-Teams entscheidende Vorteile und einen Vorsprung verschafft, und vertrauen auf ihre Qualitätsarbeit.”

Das LibreOffice-Beratungsgeschäft sowie die Lösung “LibreOffice powered by CIB” werden wichtige Bausteine im Portfolio der CIB bleiben, wenn diese Leistungen in Zukunft durch die allotropia software GmbH erbracht werden. “Für unsere Kunden erzeugt dies eine win-win-win-Situation: mit einem verlässlichen Partner wie der CIB, der Verfügbarkeit von ständig verbesserter Standard-Software auf OpenSource-Basis, sowie der Agilität eines innovativen Startups in der Entwicklung neuer Lösungen”, fügt Uli Brandner hinzu.

“Wir freuen uns über die neue Herausforderung und die Gelegenheit, uns voll und ganz auf LibreOffice und verwandte OpenSource-Produkte konzentrieren zu können. Die Zukunft wird absolut spannend für diesen Code, der bereits 30 Jahre Entwicklung hinter sich hat und auf solch unterschiedliche Systeme wie Mainframes und Mobiltelefone portiert wurde. Darauf aufbauend entwickeln wir neue Lösungen, die noch allgegenwärtiger, wiederverwendbarer und portabler sein werden. OpenSource hat sich in vielen Bereichen der Softwareindustrie als Standard durchgesetzt, und wird es auch hier tun!” sagt Thorsten Behrens, Geschäftsführer und Eigentümer von allotropia software GmbH.

Über allotropia software GmbH

allotropia logo

Die Firma allotropia software GmbH bietet Dienstleistungen, Beratung und Produkte rund um LibreOffice und weiteren OpenSource-Technologien an. Gegründet in 2020 durch fünf langjährige Entwickler des Projekts, ist das erklärte Ziel der neuen Firma, LibreOffice zu neuem Glanz zu verhelfen – in jeder denkbaren Form und in jedem Anwendungsszenario, wo heutzutage Bedarf für Office Productivity Software besteht.

Der Firmensitz der allotropia software GmbH ist in Hamburg, am Geburtsort des OpenOffice/LibreOffice Codes und -Projekts. Für weitere Informationen besuchen Sie allotropia.de oder folgen Sie @allotropiaEN auf Twitter.

Über CIB

CIB, der Innovationsführer für Ausgabe- und Dokumentenmanagement, ist europaweit mit Niederlassungen in Deutschland und Spanien vertreten. Angesehene Firmen aus der Finanz- und Versicherungsbranche, der öffentlichen Verwaltung und der Wirtschaft setzen für den Dokumentenaustausch und das Korrespondenz- und Output-Management auf die Standardsoftware von CIB. Pro Jahr generieren sie damit über 500 Millionen Dokumente. Die CIB Gruppe beschäftigt 150 Mitarbeiter in den Standorten München, Karlsruhe, Münster, Hannover, Nürnberg, Hamburg, Las Palmas de Gran Canaria, Valencia, Santa Cruz de Tenerife und Minsk.
Für weitergehende Informationen besuchen Sie libreoffice.cib.de oder folgen Sie @CIBsoftwareGmbH auf Twitter.

by allotropiasoft at January 14, 2021 12:23 AM

January 13, 2021

Marius Popa Adrian

Firebird Embedded in a sandboxed MacOS App

For those who might not be aware, Firebird on MacOS is now relocatable, in that you don't necessarily have to install it as a Framework, this also means that you can create an embedded version out of the current installer.The rest of article is here on Paul's blog

by Popa Adrian Marius (noreply@blogger.com) at January 13, 2021 03:03 PM

January 08, 2021

LibreOffice QA Blog

QA/Dev Report: December 2020

General Activities

  1. LibreOffice 7.0.4 was released on December, 17
  2. Stanislav Horáček updated Help for using custom styles in chapter numbering
  3. Ayhan Yalçınsoy, Ilmari Lauhakangas (TDF) and Adolfo Jayme Barrientos made some cleanups in Help content
  4. Triveni Remany added a note on using optimal height with wrapping in XLS files in Help content
  5. Olivier Hallot (TDF) improved the readability of print selection and PDF accessibility Help content
  6. Ming Hua added information to Help about locking and unlocking toolbars
  7. Balaharipreetha Muthu added a Help page for Calc image anchoring, a section about data bars in Help for Calc conditional formatting and a note about Calc grouping and change tracking
  8. Seth Chaiklin made 26 changes to Help, with topics including menu item updates, date patterns, keyboard navigation with footnotes and endnotes, templates, crash reporting, renaming Calc sheets, Calc data validity criteria and creating styles
  9. Noel Grandin (Collabora) made XML parsing faster in various areas, fixed some automated tests and made many code cleanups and optimisations
  10. Caolán McNamara (Red Hat) continued on the last stretch of the massive UI backend work, fixed an old issue of extended tooltips not showing in menus, dropped many uses of deprecated GTK methods and made many cleanups and crash fixes
  11. Tamás Zolnai (Collabora) fixed a crash triggered by collaborative editing
  12. Jochen Nitschke made some code cleanups
  13. Kevin Suo improved the Fields dialog layout
  14. Vert D polished the template manager list view
  15. Laurent Balland-Poirier updated Math examples
  16. George Bateman improved the VBA automated tests
  17. Chris Sherlock refactored lots of bitmap handling code
  18. Lionel Elie Mamane made internal improvements to the PostgreSQL connector
  19. Georgy Litvinov made it so TIFF images are imported in full and fixed a problem with lost styles in Writer’s Insert – Text from file feature
  20. Tibor Nagy and Attila Szűcs (NISZ) fixed a problem with lost conditional formatting in XLSX import and issues with external links in XLSX export
  21. Tünde Tóth (NISZ) improved the presentation of data labels in pie charts
  22. Balázs Varga (NISZ) fixed OOXML chart issues with rotated shapes
  23. Marco Cecchetti (Collabora) fixed count variable not being substituted in Impress slideshows
  24. Christian Lohmaier (TDF) made connecting to OneDrive work again, added a VS Code workspace template and improved cross-compilation to catch problems better
  25. Szabolcs Tóth (NISZ) fixed the positioning of rotated shapes with XLSX export
  26. Balázs Regényi (NISZ) fixed importing of VML callout shapes in DOCX files
  27. Áron Budea (Collabora) fixed a crash when opening Sidebar in chart edit mode in Writer
  28. Samuel Mehrbrodt (CIB) removed a lag when opening documents over network
  29. Jan-Marek Glogowski improved the font replacement table and made internal improvements to clipboard handling
  30. Tomaž Vajngerl (Collabora) made internal improvements to graphics and PDF handling code
  31. Rene Engelhard removed the Thunderbird address book connector
  32. Rizal Muttaqin made updates to Colibre and elementary icon themes
  33. Jean-Pierre Ledure improved the ScriptForge Basic library
  34. Heiko Tietze (TDF) made Writer’s default type of anchoring optional
  35. Attila Bakos (NISZ) fixed some Writer textbox issues
  36. Bartosz Kosiorek fixed an issue with shifting EMF image position
  37. Szymon Kłos (Collabora) fixed a crash when closing docking window
  38. Jim Raykowski made it so Draw objects get a name upon creation and improved Navigator’s handling of shape names. He also made hyperlinks to shapes work in Writer, made the statusbar page number/bookmarks control tooltip show and added an option to treat outline sub-levels as content
  39. Björn Michaelsen continued internal improvements to Writer
  40. Regina Henschel made it so cell-anchored measure lines in Calc do not lose their orientation, fixed a rotation issue with custom shapes and a distortion issue with cell-anchored shapes
  41. Xisco Faulí (TDF) made nearly 30 improvements and additions to unit and UI tests
  42. Tor Lillqvist (Collabora) started working on the UNO object inspection tool, made improvements to the macOS build process and made code cleanups
  43. Dante Doménech worked on support for MathML custom entities and improved fastparser
  44. Eike Rathke (Red Hat) improved decimal rounding in Calc
  45. Julien Nabet fixed the image button in Base forms, field copying in tablecontrols of Base forms, dropped some uses of deprecated GTK methods and fixed several regressions
  46. Michael Stahl (CIB) improved the mariadb-connector and Writer frame handling
  47. Stephan Bergmann (Red Hat) replaced unowinreg.dll with execution of `reg QUERY` for reading Windows registry, adapted the remaining OUString functions to std::string_view and made many other cleanups as well as build and test fixes
  48. Gábor Kelemen (NISZ) made code cleanups
  49. Mike Kaganski (Collabora) fixed an issue with numpad decimal key and password dialogs, an issue with keyboard navigation in text with combined characters and made build fixes and code cleanups
  50. Luboš Luňák (Collabora) continued polishing the Skia graphics engine integration, made image loading lazy for PPTX files and removed the OpenGL VCL backend code
  51. Justin Luth (Collabora) fixed character highlight problems with Microsoft formats, removed Impress-related things from Draw UI, fixed a DOCX export issue producing huge footers, an issue in a DOCX file with pasting a bulleted list inserting a page break, some issues with Writer conditional styles, an issue preventing deletion of certain page breaks and made Writer table column proportionality work as expected
  52. László Németh (NISZ) fixed spell checking of words with tracked deletions, prevented the view from jumping to the cursor when activating change tracking, fixed the display of tracked deletions in tables of contents, made it so hidden text is not shown in tables of contents and made crash fixes
  53. Miklos Vajna (Collabora) made internal improvements to handling of inserted PDFs and fixed many regressions

Kudos to Ilmari Lauhakangas for helping to elaborate this list.

Reported Bugs

732 bugs, 85 of which are enhancements, have been reported by 370 people.

Top 10 Reporters

  1. Telesto ( 143 )
  2. NISZ LibreOffice Team ( 26 )
  3. sdc.blanco ( 20 )
  4. Xisco Faulí ( 17 )
  5. Robert Großkopf ( 11 )
  6. Ming Hua ( 10 )
  7. Rizal Muttaqin ( 10 )
  8. LeroyG ( 9 )
  9. paulystefan ( 8 )
  10. mwtjunkmail ( 8 )

Triaged Bugs

685 bugs have been triaged by 83 people.

Top 10 Triagers

  1. Xisco Faulí ( 90 )
  2. Heiko Tietze ( 63 )
  3. Dieter ( 50 )
  4. Justin L ( 44 )
  5. V Stuart Foote ( 39 )
  6. NISZ LibreOffice Team ( 35 )
  7. Julien Nabet ( 31 )
  8. Roman Kuznetsov ( 30 )
  9. Buovjaga ( 28 )
  10. Telesto ( 24 )

Resolution of resolved bugs

625 bugs have been set to RESOLVED.

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

Fixed Bugs

166 bugs have been fixed by 38 people.

Top 10 Fixers

  1. Caolán McNamara ( 23 )
  2. Seth Chaiklin ( 19 )
  3. László Németh ( 12 )
  4. Justin Luth ( 9 )
  5. Julien Nabet ( 6 )
  6. Miklos Vajna ( 5 )
  7. Luboš Luňák ( 4 )
  8. Heiko Tietze ( 4 )
  9. Balaharipreetha Muthu ( 3 )
  10. Tibor Nagy ( 3 )

List of critical bugs fixed

  1. tdf#138549 CRASH: Undoing comment hovering (steps in comment 11) ( Thanks to Caolán McNamara )

List of high severity bugs fixed

  1. tdf#133878 Slow performance in autofilter if the record contains many unique values (10 seconds after 5.4 vs. 2 seconds before) ( Thanks to Luboš Luňák )
  2. tdf#134754 Crash on macOS 10.13 opening local HSQLDB-based odb file in Base on LibreOffice 7 rc1 ( Thanks to Stephan Bergmann )
  3. tdf#135202 LO 6.4.6.1 and 7.0.1 fail with error 1045 when accessing MySQL database using native connector ( Thanks to Michael Stahl )
  4. tdf#138596 Applying Formatting Aids twice crashes the application ( Thanks to Caolán McNamara )
  5. tdf#138600 Vertical aligned text in nested table is hidden ( Thanks to Miklos Vajna )
  6. tdf#138605 CRASH: Undoing paragraph deletion ( track changes ) ( Thanks to László Németh )
  7. tdf#138612 LibreOffice not splitting table cells automatically for docx files ( Thanks to László Németh )
  8. tdf#138688 Pasting Calc data into Writer table hangs Writer CRASH (steps in comment 4) ( Thanks to László Németh )
  9. tdf#138710 Crash when deleting cell rows (multi_type_vector::position#1707: block position not found!) ( steps in comment 7 ) ( Thanks to Eike Rathke )
  10. tdf#138818 Some imported tif images are being truncated and thereby corrupted ( Thanks to Georgy Litvinov )

List of crashes fixed

  1. tdf#126492 Crash report service is not documented ( Thanks to Seth Chaiklin )
  2. tdf#134754 Crash on macOS 10.13 opening local HSQLDB-based odb file in Base on LibreOffice 7 rc1 ( Thanks to Stephan Bergmann )
  3. tdf#138417 Crash when customizing sidebar tab bar ( Thanks to Caolán McNamara )
  4. tdf#138549 CRASH: Undoing comment hovering (steps in comment 11) ( Thanks to Caolán McNamara )
  5. tdf#138596 Applying Formatting Aids twice crashes the application ( Thanks to Caolán McNamara )
  6. tdf#138605 CRASH: Undoing paragraph deletion ( track changes ) ( Thanks to László Németh )
  7. tdf#138688 Pasting Calc data into Writer table hangs Writer CRASH (steps in comment 4) ( Thanks to László Németh )
  8. tdf#138710 Crash when deleting cell rows (multi_type_vector::position#1707: block position not found!) ( steps in comment 7 ) ( Thanks to Eike Rathke )
  9. tdf#138741 FILESAVE XLSX Crash if Spreadsheet contain external reference that is not used in cells ( Thanks to Attila Szűcs )
  10. tdf#138762 Crash when opening chart properties after creation ( Thanks to Aron Budea )
  11. tdf#138834 Crash in table creation wizard when clicking next ( Thanks to Julien Nabet )
  12. tdf#138897 CRASH: undoing paste ( Thanks to Michael Stahl )
  13. tdf#138935 CRASH: Opening animation sidebar pane after inserting a shape ( Thanks to Caolán McNamara )
  14. tdf#138973 Sidebar Gallery deck crashing ( Thanks to Luboš Luňák )
  15. tdf#139063 Crash when add a new sheet to a RTL sheet ( Thanks to Caolán McNamara )
  16. tdf#139127 Crash when deleting page break and undo ( Thanks to László Németh )

List of performance issues fixed

  1. tdf#133878 Slow performance in autofilter if the record contains many unique values (10 seconds after 5.4 vs. 2 seconds before) ( Thanks to Luboš Luňák )

List of old bugs ( more than 4 years old ) fixed

  1. tdf#100691 If hidden characters exist in headings, they appear visible in the table of contents ( Thanks to László Németh )
  2. tdf#41466 VML Callout shapes are incorrectly imported for 2007 DOCX (OK if resaved in MSO to newer DOCX) ( Thanks to Regényi Balázs )
  3. tdf#46579 Form fields ‘Image Button’ do not work in Forms ( Thanks to Julien Nabet )
  4. tdf#61154 EDITING: Table of Content (ToC) doesn’t cross mark deleted text with Track changes Shown ( Thanks to László Németh )
  5. tdf#65991 Help on Endnotes (Inserting and Editing Footnotes or Endnotes – Writer) gives not information on shortcut to move between anchor and footnote/endnote. ( Thanks to Seth Chaiklin )
  6. tdf#66043 EDITING: Spellchecking tracked and shown changes – erratic underlining ( Thanks to László Németh )
  7. tdf#76644 extended tips missing for menu items ( Thanks to Caolán McNamara )
  8. tdf#82802 conditional style with no conditions is displayed as un-conditional style after reloading document ( Thanks to Justin Luth )
  9. tdf#84455 UI: HELP: Missing hint that {Edit ► Changes ► Record} will disable {Data ► Group and Outline ► Group} ( Thanks to Balaharipreetha Muthu )
  10. tdf#87973 XLSX:vlookup formula changed in path to external csv file after saved and re-opened ( Thanks to Attila Szűcs )
  11. tdf#95147 suggestion: warning that automatic wrapping text in LO Calc needs to be set Optimal in case of some xls import ( Thanks to gar Soul )
  12. tdf#99613 optional Paramaters for IF is optional ( Thanks to Seth Chaiklin )
  13. tdf#99646 Make default type of anchoring optional ( Thanks to Heiko Tietze )

WORKSFORME bugs

95 bugs have been retested by 40 people.

Top 10 testers

  1. Buovjaga ( 8 )
  2. Telesto ( 7 )
  3. Justin L ( 7 )
  4. Julien Nabet ( 7 )
  5. raal ( 6 )
  6. sdc.blanco ( 5 )
  7. Dieter ( 5 )
  8. Xisco Faulí ( 4 )
  9. V Stuart Foote ( 4 )
  10. Martin Srdoš ( 3 )

DUPLICATED bugs

154 bugs have been duplicated by 35 people.

Top 10 testers

  1. V Stuart Foote ( 22 )
  2. NISZ LibreOffice Team ( 16 )
  3. Telesto ( 14 )
  4. Justin L ( 13 )
  5. Xisco Faulí (

by x1sc0 at January 08, 2021 05:40 PM

Miklos Vajna

Shadow for tables from PPTX in Impress

Impress now has much better support for the shadow of table shapes: not only shape styles can result in table shadows, but it’s also possible to add this as direct formatting. Also the shadow result is PowerPoint-compatible in the direct formatting case.

First, thanks to our partner SUSE for working with Collabora to make this possible.

Motivation

We got a PPTX document, which has a table shape with blurry shadow. The shadow was completely missing in Impress. It was discovered that in case you configure the default shape style to have shadow, then there is some initial table shadow support in Impress, but that was not used in the PPTX case.

The request was to improve the shadow rendering to be PowerPoint-compatible and in general support table shadows as direct formatting as a new feature.

Results so far

The table shadow now looks like this:

https://share.vmiklos.hu/blog/sd-table-shadow/new.png
Figure 1. New render result in Impress

Matching the reference rendering:

https://share.vmiklos.hu/blog/sd-table-shadow/ref.png
Figure 2. Reference render result

While shadow was just missing previously:

https://share.vmiklos.hu/blog/sd-table-shadow/old.png
Figure 3. Old render result in Impress

You can see that not only the shadow is there, but also the cell backgrounds and the blurry shadow is rendered properly.

How is this implemented?

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

As usual, the high-level problem was addressed by a series of small fixes:

With these, it’s now possible to add, edit, render and delete these table shadows, while preserving them during ODP and PPTX import/export.

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 intends to continue supporting and contributing to LibreOffice, the code is merged so we expect all of this work will be available in TDF’s next release too (7.2).

by Miklos Vajna at January 08, 2021 08:41 AM

January 07, 2021

Official TDF Blog

New Year, New Calc Guide for Brazilians and Portuguese-speaking Users

(Translation from this post)

Click to download the “Guia do Calc 7.0”

2020 was an terrible year.

We started the year with the expectation of an intense activity in LibreOffice but we were caught by the worst pandemic in centuries.

Nevertheless, doing nothing was not an option for our small team of Brazilians LibreOffice translators and Authors. Against adversity, we fought with the resilience of the winners.

We proudly announce the immediate availability of the Calc Guide 7.0 in Brazilian Portuguese.

The Calc Guide is the most demanded Guide by LibreOffice users and aficionados. It is a 500 pages detailing all Calc operation, from styles, printing, formulas to advanced techniques using pivot tables, filtering, databases and multiples operations, to name a few.

The “Guia do Calc 7.0” is a combined effort of Felipe Viggiano, Raul Pacheco da Silva, Túlio Macedo and Olivier Hallot, the resilient Brazilian LibreOffice documentation team as a gift for all LibreOffice users in the Portuguese language.

Brazilian Team

Happy 2021!

by Olivier Hallot at January 07, 2021 02:35 PM

January 05, 2021

Official TDF Blog

Czech translation of LibreOffice Calc Guide 6.4

Zdeněk Crhonek (aka “raal”) from the Czech LibreOffice community writes:

It’s a bit late for the Christmas gift , but we finished translation of the Calc guide 6.4. As usual it was team work, namely:

Translations: Petr Kuběj, Zdeněk Crhonek and Zuzana Pitříková

Text corrections: Marcela Tomešová and Vendula Crhonková

Localised pictures: Roman Roman

Technical support: Miloš Šrámek.

Thanks to all the team, and especially Petr for his amazing amount of translation work, Marcela for her patience with our mistakes, and Roman for his continuous support. The Czech translation of the Calc guide 6.4 is available for download here.

Zdeněk adds that the Czech team is continuing with the translation of the Writer Guide, and is always looking for new translators. Join them, or indeed teams in other languages!

by Mike Saunders at January 05, 2021 10:42 AM

January 01, 2021

Tamas Zolnai

Cypress How-To: different logging mechanisms for debugging.

Introduction

As I wrote earlier in a blogpost now we have the cypress.io test framework integrated into Collabora Online codebase. We use this test framework to run automatic tests against the code base as part of the CI process. When a test fails it's crucial to have proper logging to make it easier to find out, why a test fails. Also, we need a way to add additional logging messages for debugging a test case in detail. In this post, I'll try to summarize the different loggings available for cypress tests.

Cypress log

Cypress itself has a logging capability, which is used to record the steps made by a test case. For all commands that a cypress test runs, we will have a line in the cypress log. This log is the first thing we can see in case of a test failure. From this log, we can find out at which step the test failure occurred. This log is displayed, in one hand, in the command line (see below), but it also saved under cypress_test/cypress/logs folder:

The cypress command log above shows, on one hand, the cause of the failure: Expected to find element: `#fontnamecomboboxs`, but never found it.. It seems we don't have the DOM element with the ID of fontnamecomboboxs. The log also shows that at which step we get that failure. In this specific test case we do the following steps before the failure: 1) load the test document, 2) switch to editing mode (mobile), 3) select all text in the document, 4) open the mobile wizard. After the fourth step we try to push an item on the mobile wizard, that is missing, so the test fails.

By default, this cypress log contains logging for cypress commands. However, we can add additional logging to the test code. We can use cy.log() method for that. Anything we print out with this method will be shown in the cypress log. For example, we use this logging function in helper methods to display the beginning and the end of the method, so it's easier to understand the log. See openMobileWizard() method for example:

It is diplayed in cypress log like this:

loolwsd log

We also save the loolwsd log during a test run. In this log, we can find information about the messages sent between the client and the server. It's the same log file, what we have for the actual Collabora Online under the /tmp/ folder with the name loolwsd.log. In case of cypress tests, we put this log file under /cypress_test/workdir folder. This file always contains the log of the last test run. This "last run" can mean all the tests (e.g. make check), can be only one test suite (make check-mobile spec=writer/apply_font_spec.js) or even only one test. It depends on the command we last run. This log is very verbose, so in most cases, it's best to filter for specific messages to get useful information from it. An example loolwsd.log is shown below:

To add additional debugging information to this log you can use the LOG_DBG(), LOG_TRC(), LOG_INF() methods.

loolwsd's command line output

Besides these logs, we also record the command line output of the running loolwsd server. It's the same output that we get for top-level make run command. This output first displays the details related to the started loolwsd (e.g. browser links for hello word files or admin console). On the other hand, the same output can be used to debug LO core code behind Collabora Online. We can use SAL_DEBUG() to write out anything to this output, called from core code and also crash traces are printed here. This output file can be found at cypress_test/workdir/loolwsd_ouput.log. This output looks like the below example:

by Tamás Zolnai (noreply@blogger.com) at January 01, 2021 03:27 PM

December 23, 2020

LibreOffice QA Blog

LibreOffice 7.1 RC1 is available for testing

LibreOffice 7.1 will be released as final at the beginning of February, 2021 ( Check the Release Plan for more information ) being LibreOffice 7.1 RC1 the third pre-release since the development of version 7.1 started at the end of May, 2020. Since the previous release, LibreOffice 7.1 Beta1, 234 commits have been submitted to the code repository and 132 bugs have been fixed. Check the release notes to find the new features included in LibreOffice 7.1.

LibreOffice 7.1 RC1 can be downloaded from 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.

LibreOffice is a volunteer-driven community project and your help is much appreciated.

Happy testing, merry Christmas and happy new year!!

Download it now!

by x1sc0 at December 23, 2020 08:12 PM

Marius Popa Adrian

Firebird php driver status for Firebird Advent 2020 ⛄

Firebird php driver status for Firebird Advent 2020 ⛄https://qiita.com/advent-calendar/2020/firebirdA new version of the Firebird PHP driver was recently released. This version supports booleans values. Precompiled binaries for PHP 7.3 , 7.4 and 8.0 are available at the download section.The driver is marked as 1.1.0 stable . Please report any problems to the tracker at https://github.com/

by Popa Adrian Marius (noreply@blogger.com) at December 23, 2020 11:43 AM

Firebird LibreOffice status

Firebird LibreOffice status for Firebird Advent 2020 ⛄https://qiita.com/advent-calendar/2020/firebirdThis year Firebird was updated to 3.0.7 in master branch (LibreOffice 7.2),  patches related are in external/firebird , interesting to note is build patch for macOS on arm64.Firebird driver related changelog with fixes is located in connectivity/source/drivers/firebirdThe list of new bugs can be

by Popa Adrian Marius (noreply@blogger.com) at December 23, 2020 11:32 AM

December 19, 2020

Marius Popa Adrian

Firebird Rust driver status

Firebird rust driver status for Firebird Advent 2020 ⛄https://qiita.com/advent-calendar/2020/firebirdLast version released is 0.13.0 with a few changes.Rust firebird github repository is located here https://github.com/fernandobatels/rsfbclientCrates page is here https://crates.io/crates/rsfbclientDocs are located here https://docs.rs/rsfbclient/0.13.0/rsfbclient/More examples in the github

by Popa Adrian Marius (noreply@blogger.com) at December 19, 2020 04:49 PM

December 17, 2020

Marius Popa Adrian

Firebird SQLAlchemy support

Firebird SQLAlchemy status for Firebird Advent 2020 https://qiita.com/advent-calendar/2020/firebirdCurrent SQLAlchemy release 1.3.20 supports firebird out of the box https://docs.sqlalchemy.org/en/13/dialects/firebird.htmlIn the future the driver is moved outside of SQLAlchemy repository in this place https://github.com/pauldex/sqlalchemy-firebirdso it will be installed in the future releases

by Popa Adrian Marius (noreply@blogger.com) at December 17, 2020 05:29 PM

December 11, 2020

Miklos Vajna

Better PDF signature verification in Draw

Draw now has much better support for detecting unsigned incremental updates between signatures at the end of PDF documents. We now also make sure that incremental updates introduced for adding signatures really just add annotations and don’t change the actual content.

Motivation

There has been a recent evaluation of PDF signature verification, which included Draw. While we got a checkmark on their Shadow Hide test, their Shadow Replace test found conditional problems and their Shadow Hide-and-Replace test was not happy, either.

So time to look at what are those corner-cases and how the situation can be improved, so people keep trusting that if Draw says a signature is valid, it’s indeed valid.

Results so far

There were 4 incremental improvements in this area:

These were enough so that talking to the authors of that evaluation now confirmed that these problems are all gone.

How is this implemented?

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

PDF signature verification works by using a custom PDF tokenizer. You can read about that code in the PDF tokenizer section of this post. The bottom line is that we now have both PDFium and this custom tokenizer, somewhat duplicating the functionality.

After talking to the PDFium developers (see the relevant mailing list thread), there were open regarding adding all the high level API to allow PDF signature verification based on PDFium, and not via our own tokenizer. See this header file for the set of relevant APIs added. A combinations of those allowed to adapt the code on our side and use PDFium for signature verification, not the own tokanizer.

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 intends to continue supporting and contributing to LibreOffice, the code is merged so we expect all of this work will be available in TDF’s next release too (7.1).

by Miklos Vajna at December 11, 2020 08:31 AM

December 04, 2020

LibreOffice QA Blog

QA/Dev Report: November 2020

General Activities

  1. LibreOffice 7.1 Beta1 was released on November, 24
  2. Chris Mayo optimised icon installation on Linux and cleaned up obsolete mime type files
  3. Rizal Muttaqin made updates to Colibre, Sukapura and Elementary icon themes
  4. Björn Michaelsen continued internal improvements to Writer
  5. Tor Lillqvist (Collabora) worked on the iOS app and worked on build support related to macOS arm64 and Windows Subsystem for Linux. He also added support for displaying multiple code point emojis
  6. Noel Grandin (Collabora) made XML parsing faster in various areas, worked on tools::Long to mitigate the harmful effect of the ‘long’ type bitness difference between Windows and Linux and made many code cleanups
  7. Heiko Tietze (TDF) fixed Status bar indication for selected PDF objects, made it so application colours are respected in the font preview of character properties and redesigned the Paste Special dialog
  8. Sven Lüppken fixed an issue with border padding in exported DOCX files and improved the Bullets and Numbering dialog in the context of Draw
  9. Muhammet Kara gave lectures in Hacettepe University and many students completed their first easy hack
  10. Deb Barkley-Yeung made it so wildcards on the command line are handled on Windows
  11. Pranam Lashkari (Collabora) added a new parameter UseCurrentDocument to Calc’s uno:Move
  12. Diwanshu Mittal made it so the Undock command is disabled for locked toolbars and added shortcuts for full page-up and page-down commands in Writer
  13. Justin Luth (Collabora/SIL) fixed a text box Z-order issue with DOCX import, missing page breaks with DOCX export, a Calc issue with clicking to set formula references while having split rows/columns, a Writer cursor focus issue related to comments, added the ability to modify character highlight using paragraph style dialog’s new Highlight tab and improved character highlighting DOCX compatibility
  14. René Engelhard (Debian) made build fixes and improvements
  15. Björn Kirchhoff fixed a problem where changing system locale multiple times would influence number conversion
  16. Ouyang Leyan fixed a chart-related crash and made it so cells that are hidden or part of a collapsed group are included in Chart data series labeling
  17. Vert D. added a list view to Template manager and fixed an icon refreshing issue in the manager
  18. Samuel Mehrbrodt (CIB) improved the printing API and fixed Single print jobs function in the Print dialog
  19. Thomas Viehmann made it so top-level menus added by extensions work with Linux GTK3 VCL backend
  20. Mark Hung fixed an issue preventing opening RTF files with text frames and improved handling of CJK and CTL scripts in RTF files
  21. Rafael Lima added a Reset All button to Calc Solver dialog
  22. David Gilbert fixed problems with DOCX export of complex polygon shapes
  23. Anshu Khare made it so creating a table with a large number of columns in Writer shows a warning about performance impact
  24. Martin van Zijl added an option in Calc to disable pasting with enter key
  25. Attila Bakos (NISZ) fixed some Writer textbox issues
  26. Jan Holešovský made chart titles editable from the Sidebar
  27. Bartosz Kosiorek added support for MapMode Text and PS_COSMETIC line style in CREATEPEN in EMF graphic files
  28. Áron Budea (Collabora) made Style inspector categories translatable
  29. Tünde Tóth (NISZ) fixed some issues with pie charts in OOXML files and wrapping of labels in rotated chart labels in XLSX files
  30. Thorsten Behrens (CIB) made it possible to create scrollable tab pages in the UI
  31. Luboš Luňák (Collabora) continued polishing the Skia graphics engine integration, disabled Vulkan on Windows 7 and made code cleanups
  32. Szymon Kłos (Collabora) made chart background gradients display correctly in the Sidebar
  33. Szabolcs Tóth and Balázs Regényi (NISZ) added support for A6 paper format in imported XLSX files
  34. Daniel Arato (NISZ) fixed some Writer textbox issues
  35. Jim Raykowski made keyboard zoom work in Calc, fixed keyboard navigation in Navigator, fixed an undo-related crash, made Navigator able to track form controls and fixed a content focusing issue related to Navigator selections
  36. Philipp Hofer made dozens of commits formatting source files with clang-format
  37. Tibor Nagy (NISZ) and Regina Henschel fixed an issue with Mark Invalid Data and merged cells in Calc
  38. Tibor Nagy and Attila Szűcs (NISZ) fixed some Calc validation issues
  39. Balázs Varga (NISZ) fixed OOXML chart issues with custom shapes and TimeIncrement of Date axis
  40. Arnaud Versini made internal improvements to accessibility code
  41. Attila Szűcs and Tibor Nagy (NISZ) continued fixing Calc autofill issues
  42. Michael Weghorn fixed the display of Calc’s formula bar after internal UI rework, fixed an issue with opening a URL twice when clicking UNO hyperlink control and made it possible to restore saved window position with GTK3 and X11
  43. Jean-Pierre Ledure added the ScriptForge Basic library
  44. Ivan Stefanenko (Collabora) added more checks to the Accessibility Check feature
  45. Andras Timar improved some automated tests
  46. Dante Doménech made many improvements to Math: he added hexadecimal number and colour support, added command for frac and evaluate, renovated examples and greatly improved colour support (also with MathML)
  47. Tomoyuki Kubota made Style Inspector smarter regarding CJK and CTL properties
  48. Ming Hua added some glyphs to OpenSymbol font
  49. Tomaž Vajngerl (Collabora) made internal improvements to PDF exporting code and made code cleanups
  50. Xisco Faulí (TDF) made nearly 40 improvements or additions to unit and UI tests
  51. László Németh (NISZ) made many change tracking fixes
  52. Jan-Marek Glogowski made a couple of Firebird-related build fixes and made Qt5 report the current input method language
  53. Julien Nabet improved MySQL native connector’s authentication support, updated FirebirdSQL to version 3.0.7, fixed several Firebird-related issues and made code cleanups
  54. Miklos Vajna (Collabora) fixed a DOCX import issues with throwing away cached values of fields, added conditional fields support for DOCX export, made many internal improvements to pdfium-related code, fixed several regressions and made code cleanups
  55. Mike Kaganski (Collabora) made build fixes, code cleanups and helped Noel with the tools::Long project
  56. Michael Stahl (CIB) made many internal improvements to the handling of showing and hiding tracked changes and made build fixes and code cleanups
  57. Stephan Bergmann (Red Hat) made many cleanups as well as build and test fixes
  58. Gülşah Köse (Collabora) improved table’s row height in Impress
  59. Andreas Kainz improved the alignment and positioning of Print, Cell formatting and 3D Effects dialogs as well as Notebookbar interfaces
  60. Caolán McNamara (Red Hat) is now on the last stretch of the massive user interface backend work as can be seen from his 2020 conference presentation. In addition to the UI work, Caolán optimised autofilter search, dropped custom Indic grapheme rules in favour of ICU defaults and made many cleanups and crash fixes
  61. Regina Henschel fixed an issue with hidden rows/columns messing up shape position upon saving an ODS file, improved Calc’s ”resize with cell” functionality
  62. Eike Rathke (Red Hat) made updating of linked files more consistent, improved decimal rounding accuracy and string representation of rounded values
  63. Google Season of Docs projects for ”Calc Functions Reference and User Guide” and ”LibreOffice E-Learning Calc” were completed
  64. Ayhan Yalçınsoy improved menu item label distinction and dialog naming while also updating the Help files
  65. Stanislav Horacek updated Help regarding background colour
  66. Ilmari Lauhakangas (TDF) fixed a macro example in Help (thanks to Ubi) and updated Help for form control elements
  67. Olivier Hallot (TDF) renovated the Help page for Outline Content Visibility and did some cleanups
  68. Seth Chaiklin continued his very productive work on Help, totalling over 40 changes. The topics included menu item updates, Page line-spacing, Links to External Files, customizing menus, Navigator, printing, columns, borders, loading styles, Hanging Indent, Number Recognition, hyperlink autocorrection, Save Preview Image and the View and Languages sections of the options dialog.
  69. Henrik Karlsson improved the Help system URL redirection

Kudos to Ilmari Lauhakangas for helping to elaborate this list.

Reported Bugs

660 bugs, 80 of which are enhancements, have been reported by 396 people.

Top 10 Reporters

  1. Telesto ( 53 )
  2. NISZ LibreOffice Team ( 31 )
  3. Xisco Faulí ( 16 )
  4. Kevin Suo ( 14 )
  5. Heiko Tietze ( 11 )
  6. Colin ( 8 )
  7. sdc.blanco ( 7 )
  8. Ming Hua ( 7 )
  9. TorrAB ( 6 )
  10. Richard Demattio ( 6 )

Triaged Bugs

690 bugs have been triaged by 95 people.

Top 10 Triagers

  1. Xisco Faulí ( 113 )
  2. Buovjaga ( 57 )
  3. Heiko Tietze ( 53 )
  4. Dieter ( 47 )
  5. Timur ( 43 )
  6. Ming Hua ( 23 )
  7. Julien Nabet ( 22 )
  8. Kevin Suo ( 20 )
  9. Aron Budea ( 17 )
  10. srdosm ( 16 )

Resolution of resolved bugs

637 bugs have been set to RESOLVED.

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

Fixed Bugs

221 bugs have been fixed by 48 people.

Top 10 Fixers

  1. Caolán McNamara ( 34 )
  2. Seth Chaiklin ( 19 )
  3. László Németh ( 10 )
  4. Luboš Luňák ( 9 )
  5. Miklos Vajna ( 6 )
  6. Noel Grandin ( 5 )
  7. Bartosz Kosiorek ( 4 )
  8. Julien Nabet ( 4 )
  9. Xisco Fauli ( 4 )
  10. Heiko Tietze ( 4 )

List of critical bugs fixed

  1. tdf#133630 CRASH: Chart: Changing properties in different objects ( Thanks to Ouyang Leyan )
  2. tdf#138183 Failed to copy and paste in calc ( Thanks to Caolán McNamara )
  3. tdf#138229 Crash when starting any editor with certain formatted clipboard content ( Thanks to Mike Kaganski )
  4. tdf#138428 CRASH: Undoing paste after editing comment ( Thanks to Caolán McNamara )

List of high severity bugs fixed

  1. tdf#122419 AutoFilter Search Freezes Calc if the column contains many unique values ( Thanks to Caolán McNamara )
  2. tdf#127086 PPT: FILESAVE: Crop image is gone after RT ( Thanks to Miklos Vajna )
  3. tdf#134161 CPU at 100% after opening a particular spreadsheet ( Thanks to Xisco Fauli )
  4. tdf#137908 Exceptions for auto correct disappear lost after restart ( Thanks to Noel Grandin )
  5. tdf#137974 Forms have no borders ( Thanks to Luboš Luňák )
  6. tdf#138271 FORMS: Some values are not saved (gen) ( Thanks to Caolán McNamara )
  7. tdf#138466 Crash when creating different scenarios ( steps in comment 4 ) ( Thanks to Noel Grandin )
  8. tdf#83419 EDITING: Autocorrect doesn’t work correctly with visible tracked changes ( Thanks to László Németh )

List of crashes fixed

  1. tdf#129410 CRASH: Corrupted spreadsheet, unable to open in Linux ( Thanks to Caolán McNamara )
  2. tdf#133630 CRASH: Chart: Changing properties in different objects ( Thanks to Ouyang Leyan )
  3. tdf#136611 Crash: Change Corner Style on sidebar with selecting Data Series. ( Thanks to Caolán McNamara )
  4. tdf#137181 Basic macro: CRASH when running a macro in Impress ( Thanks to Caolán McNamara )
  5. tdf#137745 LO Base Firebird: crash, when deleting tables and changed relationship isn’t changed in database file ( Thanks to Julien Nabet )
  6. tdf#137769 ChangesInMargin: Crash on Undo of characters deleted by pressing Delete ( part 2 ) ( Thanks to László Németh )
  7. tdf#137786 Crash swlo!SwNodeIndex::~SwNodeIndex+0x18 ( Thanks to Caolán McNamara )
  8. tdf#137802 CRASH When deleting shape+textframe anchored to page ( Thanks to Attila Bakos (NISZ) )
  9. tdf#137982 CRASH: closing table preview. mail merge ( Thanks to Caolán McNamara )
  10. tdf#137993 Crash after closing one window and pressing enter in the other window with search bar focused (GTK3) ( Thanks to Caolán McNamara )
  11. tdf#138022 LibreOffice exits/crashes when minimizing start center after closing a document (SKIA) ( Thanks to Jan-Marek Glogowski )
  12. tdf#138108 LO base with Firebird: crash during FORMS design, when entering Groups and exiting (gtk3 only?) ( Thanks to Caolán McNamara )
  13. tdf#138130 Crash in: swlo.dll ( Thanks to Tibor Nagy )
  14. tdf#138229 Crash when starting any editor with certain formatted clipboard content ( Thanks to Mike Kaganski )
  15. tdf#138240 ODBC: Crash when trying to connect to Edit → Database → Properties (gtk3) ( Thanks to Caolán McNamara )
  16. tdf#138253 Crash swlo!SwNodeIndex::~SwNodeIndex+0x18 (gen) ( Thanks to Miklos Vajna )
  17. tdf#138335 XSidebar::requestLayout() crashing when called via UNO ( Thanks to Thorsten Behrens )
  18. tdf#138373 Crash when not setting Horiz/Vert scrollbars in UnoTabpageModel’s insertByIndex() ( Thanks to Thorsten Behrens )
  19. tdf#138428 CRASH: Undoing paste after editing comment ( Thanks to Caolán McNamara )
  20. tdf#138466 Crash when creating different scenarios ( steps in comment 4 ) ( Thanks to Noel Grandin )

List of performance issues fixed

  1. tdf#122419 AutoFilter Search Freezes Calc if the

by x1sc0 at December 04, 2020 11:51 AM

November 27, 2020

Collabora Community

Collabora Online Community Roundup #7

On October 1st, Collabora Online moved to its new home on GitHub, and started settling in the new infrastructure, expanding its fantastic community, and continuing the work to deliver the latest and greatest developments in productivity and collaboration together. Check our new community website for all the details! 😉

Collabora developers also keep fixing and improving our lovely mother project LibreOffice. As all the good work requires some appreciation, let’s take a look at what the seasoned developers of the Collabora team and the volunteer contributors from our community have been doing during the last week.

Week in Numbers

On the Collabora Online code repository in the last week, 29 authors have pushed 102 commits to master and 193 commits to all branches. On master, 150 files have changed and there have been 2,357 additions and 1,480 deletions.

Screenshot of GitHub Pulse for Collabora Online
Development Activity on Collabora Online GitHub Repository from November 13, 2020 to November 20, 2020

New Contributors

Congratulations to SaschaT667, JensTheCoder, BernhardGehl, accolon and Gabriel Filion for reporting their first issues and improvement requests on our GitHub repository!

  • Thanks to SaschaT667 for opening an enhancement request for adding editable and dynamically-calculated formulas support to Writer documents.
  • Thanks to JensTheCoder for reporting an issue about frozen lines in Calc documents.
  • Thanks to BernhardGehl for letting us know about some unexpected log messages from COOL, integrated with Nextcloud.
  • Thanks to accolon for reporting an issue about zoom factors of spreadsheets on macOS Big Sur.
  • Thanks to Gabriel Filion for reporting a bug which caused COOL packages for some distros to fail to start, and thanks to Andras Timar for fixing it quickly.

Thank you all, and welcome aboard! 🙂

Join the fun!

You can also join the fun, and be part of our next list of new contributors! 🙂

Just go to our GitHub repo, fork it, build it (on Linux or on any platform), grab one of our newcomer-friendly easy hacks, and send your first pull request. And if you get stuck at any point, just drop by one of our communication channels. 😉

Highlights

Collabora Online Weekly Meeting #3

COOL Weekly Meeting #3 has taken place on Thursday, November 26, 2020 at 11:00:00 am (UTC) with participants both from the community contributors and the Collabora team. We have got a quick update on what’s going on and discussed matters raised by the contributors, as well as having the chance to say hi to fellow members of the community. Topics discussed in the meeting include:

  • Contextual toolbars for COOL (suggested by Andreas Kainz) got a new patch merged to master with some initial bits of implementation. Andreas Kainz will test it and give feedback.
  • Icon theming for COOL leveraging SVG files (suggested by Andreas Kainz) has been decided to be turned into an issue on GitHub to keep track of the initial work of defining the class names. Below is a proof of concept screenshot by Andreas Kainz demonstrating how two different sets of icons can be obtained just by using two different SVG classes.

    A proof of concept screenshot by Andreas Kainz demonstrating two different sets of icons with two different SVG classes
  • The blog post about iOS app upgrade (suggested by Nicolas Christener) is planned to be written/published when the new upgrade is out. It was also mentioned that new beta testers should ask Kendy for access to the testing versions.
  • Regarding Mobile / iOS versions, Pedro Silva has reported that the Notebookbar for iPad has been improved, and many fixes and improvements have already been included in 6.4 for a more clutter-free notebookbar with better user experience for iOS users. He has also touched up the community website to add a prominent link to the forum.
  • Gökay Åžatır has shared some update about his work on CanvasTileLayer
  • Gabriel Masei asked about the ways to avoid duplicated effort, and was suggested to keep in touch with the team in the #cool-dev channel on Freenode, and also participate in the following sessions of the COOL Weekly Meeting. He is interested in contributing to COOL to make it possible to dynamically change between the classic toolbar and the new notebookbar views.

Check out the meeting minutes for the details of the meeting, make your own suggestions for the next meeting, and join us on Thursday, December 03, 2020, at 11:00 am (UTC) to stay in touch with the rest of the community. We’re looking forward to hearing from you live. 😉

Collabora Online (COOL)

Collabora Office on Android & iOS

  • Thanks to Tor Lillqvist for fixing an issue which caused the on-screen keyboard not coming back after being dismissed once in a session in the iOS app. He has also made sure that no auto-scrolling of a page on a Writer document happens if user is making a selection by dragging the selection handles in the iOS app.
  • Thanks to Jan Holesovsky for making sure that plain text content copied from browser is properly pasted without additional characters in the Android app.

Collabora Online Integrations

  • Thanks to Roeland Jago Douma for improving performance of Collabora Online’s Nextcloud integration by making sure extra queries and steps are avoided by obtaining the appdata folder in one go. He has also improved handling of empty files to avoid possible issues.
  • Thanks to Julius Härtl and Andras Timar for reviewing and merging pull requests on Collabora Online’s Nextcloud integration.
  • Thanks to Phil Davis for upgrading phan version on Collabora Online’s ownCloud integration, thus helping to maintain a high PHP code-quality for the project.
  • Thanks to Semih Serhat Karakaya for making Collabora Online’s ownCloud integration future-proof by changing the code to use the path from the appManager instead of a static one.
  • Thanks to Jan Ackermann for helping Collabora Online’s ownCloud integration stay up-to-date by replacing some deprecated functions with current ones, as well as making sure the integration app has the correct default name.

Honorable Mentions

  • Thanks to Marc Rodrigues for continuing to keep us updated on various news around Collabora Online and related FOSS projects, and creating a lot of yummy content to read!
  • Thanks to Andras Timar for keeping us organized, maintaining our translation project on Weblate, and delivering hot new releases of our software!
  • Thanks to Cor Nouws for leading the marketing team, and not stopping there but continuing with testing & reporting bugs, attending to community events, and keeping us all informed about what’s going on. He also attends LibreOffice Design meetings from time to time to help COOL’s mother project LibreOffice have a better UI & UX.
  • Thanks to Jan Holesovsky for doing a lot of research on different topics, and providing mentoring/patch-reviewing/hand-holding/wisdom within the team, in our communication channels, and also on various channels of our lovely mother project LibreOffice.
  • Thanks to Eloy Crespo for his efforts to help the project well-funded as always.
  • Your friendly community mentor, Muhammet Kara, is also creating & improving easy hacks, running workshops, helping new contributors solving their setup & build issues and reviewing their pull requests, working on easing the build procedure, improving our GitHub presence bit by bit based on its community guidelines, compiling/composing these community updates…

Translators

Last but not least, we can’t thank enough to our translators who constantly help COOL and its friends talk many languages on this earth. Collabora Online speaks many languages, thanks to all of our translators in our translation project, and all of those who previously contributed and keeps contributing to our mother project, LibreOffice.

We’re continuing to work to find good ways to credit translators’ hard work in the product. Please see a list of those involved, and please get in touch if you’re not listed. Many thanks to all those who have worked on translating Online, you rock!

If you would like to help COOL speak your language, you can just go to our translation project on weblate, and start contributing! 😉

Collabora Online translation project on Weblate
Collabora Online translation project on Weblate

Collabora loves LibreOffice!

We’re still contributing to LibreOffice and encourage you too to do so because LibreOffice rocks. 😉

  • Thanks to GülÅŸah Köse for making sure documents with text camera z rotation are properly opened and saved for PPTX files, thus improving interoperability with other office suites.
  • Thanks to Miklos Vajna for fixing a bug that caused LibreOffice to not update all preview images on an ODT file after issuing the UpdateAll command, as well as various other fixes for issues encountered while opening certain DOCX files,[0][1] and also for improving PPT support by resolving an issue which caused some images being lost after opening a PPTX file and saving it as PPT.
  • Thanks to Noel Grandin for doing various code-quality improvements and modernization all around the LibreOffice code-base.

The post Collabora Online Community Roundup #7 appeared first on Collabora Office and Collabora Online.

by Muhammet Kara at November 27, 2020 10:55 PM

Miklos Vajna

Better handling of cached field results in Writer

Writer now has much better support for preserving the cached result of fields in documents. This is especially beneficial for Word formats where the input document may have a field result which is not only a cache, but re-calculating the formula would yield a different result, even in Word.

Motivation

A Collabora Office customer gave us a DOCX document, which is essentially a calendar for planned IT maintenance windows at some organization. These calendars are tables with fields in it. The document is halfway through towards changing it to a newer year: the formulas are already changed to calculate a newer year, but all the cached field results are still for the old year.

The request was to keep showing these results and not throw them away during save, either. Their primary workflow is to fill the calendar with manual entries, not to tweak the calendar layout itself.

Results so far

The calendar now looks like this:

https://lh3.googleusercontent.com/6o7pvix-dJ9QhCX65FUkWeQZ60B89sHqDpBvd7WVRLtAzBW1323odrQ13aV_CgEFvgh7Iee-ePq95oPOf1Q-jMxvX1MBsz9FhgKd9vymyrdMBIZbF459hNKE1dM4XLcwXkGYh8ksmok=w1920
Figure 1. New render result in Writer

Matching the reference rendering:

https://lh3.googleusercontent.com/GJd2zcnspXDb7Wa2p32TInf9C8MAgt92h3G6PYuUwUvpQi5f3AdRbl5yGq8FN7kUPMcZwuFpohTKmX33s8u-AxFSO9rZFgH4X-fwrg8jShtJoA1KyGws_-ymUvINmK-5xo2_hd7YmLI=w1920
Figure 2. Reference render result

While it looked like a broken calendar previously:

https://lh3.googleusercontent.com/bpOVqcZX2CcKouuADNyPx1PMyI3I6CyjIDIAnUbylsT-ZimxSkPcUaRbMDd8MzHlG3Uqw2d-TunD4m7U4DUlm_O_esJt6CAY-H7Z5tdQxZ6q_MYxgJphutr_-JRVYh8uLmspiiI532U=w1920
Figure 3. Old render result in Writer

You can see that the day numbers were broken previously and now they line up properly.

How is this implemented?

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

As usual, the high-level problem was addressed by a series of small fixes:

With these, it’s now possible to edit these calendars, without breaking the fields which provide the day numbers.

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 intends to continue supporting and contributing to LibreOffice, the code is merged so we expect all of this work will be available in TDF’s next release too (7.1).

by Miklos Vajna at November 27, 2020 08:08 AM

November 24, 2020

LibreOffice QA Blog

LibreOffice 7.1 Beta1 is available for testing

The LibreOffice Quality Assurance ( QA ) Team is happy to announce LibreOffice 7.1 Beta1 is available for testing!

LibreOffice 7.1 will be released as final at the beginning of February, 2021 ( Check the Release Plan for more information ) being LibreOffice 7.1 Beta1 the second pre-release since the development of version 7.1 started at the end of May, 2020. Since the previous release, LibreOffice 7.1 Alpha1, 1131 commits have been submitted to the code repository and 245 issues got fixed. Check the release notes to find the new features included in this version of LibreOffice.

LibreOffice 7.1 Beta1 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 and your help is much appreciated.

Happy testing!!

Download it now!

by x1sc0 at November 24, 2020 05:48 PM

November 21, 2020

Jean Hollis Weber

Help for people still using Apache OpenOffice

Do you know someone who is still using Apache OpenOffice? Have they recently tried to open a .odt, .ods or .odp file and received this error message? “This document was created by a newer version of OpenOffice. It may contain features not supported by your current version.

AOO error message
The notice (pictured) that pops up in Apache OpenOffice doesn’t say so, but even the latest version of AOO (4.1.8, which was released earlier this month) does NOT support features like ODF 1.3, so updating to it won’t help. AOO users would need to “update” to LibreOffice. (LibreOffice users can avoid the problem for OO users by continuing to save files in ODF 1.2.)

Note: other features are lacking in AOO, for example the ability to save files in DOCX format, even though AOO can open DOCX files. LibreOffice can do both. Wouldn’t it be nice (helpful) if the “Update Now” button in AOO took a user to the LO download page?

See also this blog post at LibreOffice.

by Jean at November 21, 2020 03:18 AM

LibreOffice 6.4 and 7.0 User Guides

I am way behind updating this blog, including mentioning the LibreOffice 6.4 user guides that have been published in 2020. These include Getting Started Guide, Writer Guide, Base Guide, Calc Guide, Draw Guide, and Math Guide.

Calc Guide 7.0 coverTwo volumes of the v7.x series of books have been published recently: Math Guide and Calc Guide.

You can download free PDFs of these books or buy printed copies of the v6.4 volumes (v7.0 print copies may be available later). See this page for links.

by Jean at November 21, 2020 03:12 AM

LibreOffice 7.0

LibreOffice 7.0 was announced on 5 August 2020. Since then three minor releases have appeared. Significant new features include support for OpenDocument Format (ODF) 1.3; better performance; and improved compatibility with DOCX, XLSX and PPTX files. For details, see the blog post linked above.

LibreOffice produced a visual timeline of derivatives from OpenOffice.org, as shown below. (Click for a larger image.)
Timeline of OO/AOO/LO major releases

by Jean at November 21, 2020 02:55 AM

November 17, 2020

Collabora Community

Update on LibreOffice support for ARM-Based Macs

It is always an exciting time to see freshly minted ARM based silicon arriving in the form of Apple’s massive shift to the ARM based M1. This of course means work for Collabora’s LibreOffice team too. The code needs to be prepared for M1, step by step. Here we update you on the status of the work, and what needs to be done.

With the launch of the new Apple devices nearing, it is important that suitable software arrives around the same time as new hardware. Apple ensures this by a translation layer, so that software for Intel Macs can be used, using Rosetta translation.

Nevertheless, given the code size of LibreOffice, for the best performance it makes most sense to have a pre-optimized native binary. As such Collabora joined the Universal App Quickstart Programme back in July and has been doing work on enabling LibreOffice for M1 since then.

This effort is made possible by the kind support of those who buy LibreOffice Vanilla in the Mac app store. Thank you! And thanks too to Tor Lillqvist for his patience and hard work here.

The status of the work

All of these changes are in master, or in the gerrit queue getting past our CI automation:

  • Configuration changes (mostly there). It should now possible to configure and build a native LibreOffice on a Apple Silicon, as well as cross-compiling to x86_64.
  • Patching and fixing of lots of bundled libraries to make them build cleanly.
  • Then there is a first attempt at a new C++/UNO ABI bridge – we need to match Apple’s ABI by tweaking Linux’s ARM64 support to match. This allows UNO scripting to work (in theory).
  • We still have some failing unit tests, that need investigation, as well as some other bits, described below.
All of this means that LibreOffice should start and work on M1! So far it has had only very basic Writer & Calc testing. The more exciting, complex features are not yet tested.

What’s next .. want to get involved?

Post-launch, if you can get an M1 Mac, then help is always most welcome! We have several missing pieces that will require further work, with some unusual low-level bits.

  • The new C++/UNO ABI bridge requires more testing, to ensure the UNO scripting support works smoothly.
  • Enabling bits we didn’t compile in yet: Firebird, Java (when there is a JDK).
  • Scripts to combine builds for arm64 and x86_64 into one universal app (i.e. one where binaries are “fat,” consisting of separate parts for each architecture)
  • Adaptation to whatever new checks are added for universal apps in the App Store. This is an ongoing unpredictable part of our work: adapting 8 million lines of code to the latest updated rules, keeping our builds compiling and signing with the latest tool chains.
Of course we’ll continue to work to bring the best LibreOffice possible to Apple Silicon as time permits, and we are confident that even if we don’t make it in the next month or two, Rosetta 2 will fill the gap using dynamic instruction set translation. And when all is done, our open source desktop productivity tools will benefit the full power of the new Macs!

The post Update on LibreOffice support for ARM-Based Macs appeared first on Collabora Office and Collabora Online.

by Cor Nouws at November 17, 2020 01:03 PM

November 14, 2020

Roman Kuznetsov

If you updated your mac to macOS Big Sur then you have problems with LibreOffice

First problem - only LibreOffice 7.0 and newer works on macOS 11 Big Sur. Nobody knows why. So if you use older version you should update your LibreOffice to 7.0.3

Second problem - if you have a Retina screen (HiDPI), then you can't use LibreOffice, because all text will be blured. There is a bug 138122

So, Apple, thank you!

by Roman Kuznetsov (noreply@blogger.com) at November 14, 2020 10:30 PM

November 13, 2020

Miklos Vajna

Detecting 0-byte files based on extension in Impress and elsewhere

Impress (and Writer and Calc) now has support for detecting 0-byte files on open/import based on their extension. This builds on top of the previous language-independent template improvements. This means that e.g. a 0-byte PPTX file will open as an empty Impress presentation, not in Writer.

Motivation

We regularly see customers wanting minimal templates, which are language independent and have no content. Such files are handy if your workflow is to first name an empty document (create it) and only then edit it (and not the other way around: first create the document, then save it by giving it a name). This is easy for .txt files: if it’s zero bytes, it’s empty. But then this approach is also expected to work for other file formats as well, where our original approach was more technical: if it’s an empty file, that that can be only plain text, so we (almost) always opened it in Writer, not matching the user expectations.

Instead of explaining the problem to people again and again (that a literally empty PPTX file is not a PPTX template), there is value in just adapting the code instead to "do what I mean".

Results so far

An empty PPTX file is now handled like this:

https://lh3.googleusercontent.com/zk3b0f2Rx3t5vFVuKiimujSJWYwPNH05PCf5Indih3OwMDeBrOUH1X7N22PO46kIbxTVzI0V3IV-bE0sMycTHGj2eRqKT6K7eQkZ0Py9QVCPIhV0pdKdGPLGH08xpw72wFQ-3eGyX4k=w1920
Figure 1. Empty PPTX file opening in Impress

You can see this is no longer opening in Writer as plain text but in Impress, which is clearly a less surprising behavior.

Here is what happens if you open an empty DOTX (template):

https://lh3.googleusercontent.com/cVB_kK2wDyNIJjLt9v9UcNS4AagRCifwBofp70mHfNVzopvrN1cxcsVLhWfEArhab_PwSFkAvLlMUS1witevRcKeEn9UXYtw5o4VeGSztvnNUi6YMtR3t2DUIu1k2LLOUhnpckAnrwQ=w1920
Figure 2. Empty DOTX file creates a new Writer document

You can see that it is even recognized that this is a template format, so a new document is created, not the template itself is opened for editing.

How is this implemented?

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

You can see the code change in this commit. First, we restrict this trick to file URLs, and also to empty files.

Second, we look at the extension of the file and try to match an import filter that usually handles that extension. This helps, because then nominally the correct filter will be used for the import, so save will not ask for a filename (as it happens for new documents), but it will know what target filename and export filter to use.

Finally we need to avoid actually invoking the import filter, because no file content is not something an import filter has to handle if its filter detection would reject the file. (E.g. PPTX is expected to be a valid ZIP file.) This is important, because we want to avoid touching each & every file filter to not fail for empty file content — instead we want to handle this centrally, at a single place.

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 intends to continue supporting and contributing to LibreOffice, the code is merged so we expect all of this work will be available in TDF’s next release too (7.1).

by Miklos Vajna at November 13, 2020 07:50 AM

November 09, 2020

Gülşah Köse

Table row height improvement in Impress - LibreOffice / Collabora Office

In Impress while importing a table, there could be some situation that we have to shrink or scale table to fit in area. We have to decide how to change row heights while fitting in area. There were a problematic case that when we have text in row. Bug report is here:

How it should look: Row heights are equal and images seems in their cell

 

How was it looking before the fix: First two rows are smaller and empty rows seems bigger than actual. Total table height is bigger tan actual.

 



 

 

 

How it looks after the fix:


 




Patch link is here: https://git.libreoffice.org/core/+/b7b05dd36403af50b20fe06cbf8a10d8defb28a9%5E%21


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 intends to continue supporting and contributing to LibreOffice, the code is merged so we expect all of this work will be available in TDF’s next release too (7.1).

by Gülşah Köse (noreply@blogger.com) at November 09, 2020 02:58 PM

October 30, 2020

Andreas Kainz

Layout updates

You know the LibreOffice community work hard on the LibreOffice 7.1 Christmas release. Did you know that LibreOffice has 7 different UI Layouts? With the next release, our uses will be informed after the installation. Thanks to Heiko for the new dialog.

As all users get informed about the different UI layouts don’t forget to write a bug report, that everybody will have the best Office Suite. If you like my work become a

downloads_wordmark_white_on_coral2x.jpg

by kdeonlinux at October 30, 2020 08:23 PM

October 29, 2020

Roman Kuznetsov

Your typical errors when creating presentation templates. Part 1

So, let's continue to dissect these nice presentation templates from our Indonesian community. Download the same template as in previous article. Open it in LibreOffice Impress and look at first slide:

 

Try click somewhere on slide in area with rectangles. You can select any from these rectangles include the largest grey rectangle that author used as background for all composition. Its all are just shapes! This is an absolutely wrong way when you create a presentation template!

First, user shouldn't have an opportunity to select any slide background elements. This will interfere with and distract him from creating the presentation. User should understand clear that he can change only heading text on first slide of his future presentation. 

And second problem with these many shapes is its size. Every shape is an different object with own parameters, like position on page/slide, z-order, weight and height, area color/gradient, etc. and therefore every shape has a not small size.

The best way here is to create a background for your slide in another graphic software, like LibreOffice Draw in our case (or GIMP or Inkscape). Note, your image should have the same size as your future presentation template, like 16:9 or 4:3, or A4. Then save that image as PNG with the best quality somewhere on your PC.

A next step is to set up your image as background for a slide. There are several methods for it. Simpliest method is follow: open a Properties section in Sidebar. Press a "Insert image" button. Find and select your image in "Set background image" dialog and press "Open" button there. Voila! You have a slide background (I used another image and I before deleted all these shapes just for visibility):