Welcome to The Document Foundation Planet

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

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


Monday
30 June, 2025


face

LibreOffice Conference 20205 logo

Registration is now open for the LibreOffice Conference 2025! Join us from 4 – 6 September in Budapest 😊 We’ll have technical talks, workshops, social events and more…

Click here to learn more, and register


Saturday
28 June, 2025


face

To write this article, I went beyond the limits of my technical knowledge, which is that of an advanced user who has studied standard formats and their characteristics in depth, to understand why standard formats – one of the pillars of digital sovereignty – and proprietary formats – their opposite, and one of the biggest obstacles to digital sovereignty – are not perceived as a problem by most PC users, who continue to use Microsoft’s proprietary formats and place the access and availability of their content in the hands of the US company.

To try to remedy this problem, I will try to explain as simply as possible, using non-technical language (which may shock developers, but this article is not aimed at them), some technical features of the Open Document Format (ODF), which make it the cornerstone of an open and vendor-independent ecosystem for office documents, defending the digital freedoms of all users and the governance of their content.

I will begin by explaining how to unpack an ODF file, which is nothing more than a set of XML files and other files (for images and videos) contained within a ZIP folder, in order to examine its internal components and, in particular, the content.xml file, which is the one that contains the body of the document (i.e., the user’s intellectual property).

The aim is not so much to assess conformity (compliance with specifications) and interoperability (the ability to exchange files consistently between tools), as these aspects will always be dealt with by specialists, but rather to understand the advantages for the user of the open and standard format over the closed and proprietary format (which is falsely standard, since it was approved by ISO/IEC in defiance of “their” definitions of standards).

For this reason, I will make a brief concluding digression on the characteristics of the OOXML (Office Open XML) format used by Microsoft Office and Microsoft 365, again to clarify to users the risks they face and the harm they do to themselves and other users when they use DOCX, XLSX and PPTX formats, as well as the ‘gift’ they are giving to Microsoft, to whom they are effectively entrusting the management and future of their content.

Analysing an ODF file

Take any document you have created with LibreOffice. For convenience, I recommend starting with a text document created with LibreOffice Writer, with the ODT extension. Before doing anything else, duplicate the file, because an error in the procedure could make it unreadable, and move the original to another folder.

Rename the copy, replacing the ODT extension with the ZIP extension, without deleting the dot. The file icon will become that of a compressed file. If it becomes white or empty, you have done something wrong or deleted the dot. Check all the steps until the icon becomes that of a compressed file.

At this point, right-click on the icon and select “unzip” or “expand” to extract the contents of the compressed file into a folder with the


Wednesday
25 June, 2025


[en] Michael Meeks: 2025-06-25 Wednesday

14:04 UTC

face
  • Catch up with H. with some great degree news, poke at M's data-sets briefly, sync with Dave, Pedro & Asja. Lunch.
  • Published the next strip around the excitement of setting up your own non-profit structure:
    The Open Road to Freedom - strip#23 - A solid foundation
  • Partner sales call.

Tuesday
24 June, 2025


[en] Michael Meeks: 2025-06-24 Tuesday

21:00 UTC

face
  • Tech planning call, sync with Laser, Stephan, catch up with Andras, partner call in the evening. Out for a walk with J. on the race-course in the sun. Catch up with M. now returned home.

face

T-shirts, hoodies, bags with LibreOffice icons

Get cool LibreOffice merchandise – and support our projects and community! We’ve updated our Spreadshirt shop with new designs, and part of the sales go to The Document Foundation, the non-profit organisation behind the suite.

Click here to visit the shop


Monday
23 June, 2025


[en] Michael Meeks: 2025-06-23 Monday

21:00 UTC

face
  • Mail chew, sync with Miklos, Thorsten, Collabora intro call for allotropians, sync with Pedro, some XWIKI'ites, and Eloy.
  • Extraordinary All Saints PCC meeting in the evening.

Sunday
22 June, 2025


[en] Michael Meeks: 2025-06-22 Sunday

21:00 UTC

face
  • All Saints in the morning, caught up with people, back for a fine BBQ lunch, E. out driving with J. improving rapidly it seems.
  • Catch up with M&D and T.

Saturday
21 June, 2025


[en] Michael Meeks: 2025-06-21 Saturday

21:00 UTC

face
  • Poked at this & that in the morning, out after lunch to Holkham beach with J.&E. swum in the sea, admired the sky. Walked into Wells for dinner, bus back to the car, home.

Friday
20 June, 2025


[en] Michael Meeks: 2025-06-20 Friday

21:00 UTC

face
  • Up early; sync with Dave & Asja. Admin, caught part of an interesting WASM Tea Time Training.
  • Sync with Thorsten, merger status round.
  • Late lunch; customer/partner call, code-read an issue with Pranam: finally some code!
  • Out for a walk with J. in the evening, relaxed on the heath and watched the sky together, pub in Moulton, home, bed.

face

El Open Document Format (ODF) es un formato estándar abierto para documentos ofimáticos que permite codificar documentos de texto, hojas de cálculo, presentaciones, etc. de forma independiente y sin derechos de autor.

Sin embargo, para aprovechar todo su potencial, es …


face

The Open Document Format (ODF) is an open standard format for office documents, which offers a vendor-independent, royalty-free way to encode text documents, spreadsheets, presentations, and more.
However, to realise its potential, it is necessary to understand the concepts of compliance – the degree to which an implementation adheres to ODF specifications – and interoperability – the ability to exchange and view ODF files without loss of fidelity or functionality across different applications and platforms.

ODF is an XML-based file format that has been standardised by OASIS and ratified by ISO/IEC 26300. Milestones include:

  • ODF 1.0 (2006): the initial version defining the basic document types: text (.odt), spreadsheet (.ods) and presentation (.odp).
  • ODF 1.1 (2012): updates to formula specifications and accessibility improvements were made, but it was never submitted for standardisation.
  • ODF 1.2 (2015): introduces digital signatures, RDF metadata, and OpenFormula for standardising spreadsheet calculations.
  • ODF 1.3 (2020): an extension of security features, including improvements to encryption and import/export conventions, as well as a clarification of compliance clauses.

Each version has strengthened the role of ODF as a universal interchange format, ensuring that documents remain readable and editable in all programs, both now and in the future.

Definition of compliance

Compliance refers to the extent to which a given software implements the ODF standard. It comprises several levels:

  1. Structural compliance: ensures that file archives contain the expected XML files (e.g. content.xml, styles.xml and meta.xml), in accordance with the ODF Packaging specifications.
  2. Schema validation: verifies that the XML content matches the applicable ODF schemas (Relax NG or W3C XML Schema). This prevents a <draw:image> element, for example, from appearing where only text is permitted.
  3. FeatuSecurity profilesre compliance: supports the required features (styles, tables, charts and metadata) and the correct implementation of the optional features required by the application (digital signatures, encryption and change tracking).
  4. Formula compliance: for spreadsheets, adherence to OpenFormula specification ensures that formulas behave consistently across different applications.
  5. Compliance statements and profiles: applications often declare their compliance levels (e.g. ODF 1.2 Part 1: OpenDocument Schema). Some define profiles, which are subsets of the full standard tailored to specific industries or workflows.

Non-compliant files risk becoming unreadable or displaying incorrectly in other applications. Validating ODF schemas and integrating compliance tools enables developers and users to guarantee the longevity and accuracy of documents.

The interoperability landscape

Even when two applications claim ODF compliance, disparities can arise.

  • Rendering differences: variations in character substitution, line spacing or image placement can slightly alter the layout.
  • Functionality differences: for example, an editor may support digital signatures, but implement them in a way that causes signatures to be rejected when files are exchanged.
  • Use of extensions: some applications use proprietary extensions (e.g. custom XML blocks) that others do not recognise, which can result in data or content loss.
  • Metadata management: different handling of document properties, such as author, version history or custom metadata, can hinder workflows.

To achieve strong interoperability, systematic testing is required.

  1. Automated

Thursday
19 June, 2025


[en] Michael Meeks: 2025-06-19 Thursday

21:00 UTC

face
  • Up early, tech planning call in the morning, mail catch-up, admin and TORF pieces.
  • Really exited to see the team get the first COOL 25.04 release shipped, coming to a browser near you:
    COOL 25.04 released!

    Seems our videos are getting more polished over time too which is good.
  • Mail, admin, compiled some code too; bit patch review here & there.

Wednesday
18 June, 2025


[en] Michael Meeks: 2025-06-18 Wednesday

21:00 UTC

face
  • Up too early, out for a run with J. Sync with Dave. Plugged away at calls, admin, partner call, sales call, catch up with Moritz, Philippe and Italo.
  • Birthday presents at lunch - new (identical) trousers, and a variable DC power supply for some electronics.
  • Published the next strip around the excitement of setting up your own non-profit structure:
    The Open Road to Freedom - strip#22 - Our own structure!
  • Fine steak dinner with the family in the evening.

face

Stefan Soyka, StarOffice developer in the early '90s

LibreOffice is the successor project to OpenOffice(.org), which in turn was based on StarOffice, a proprietary office suite developed in the 1990s. Learn more about the history here! And let’s hear from Stefan Soyka, who worked on StarOffice from 1990 – 1992…

When did you join Star Division, and what did you work on?

I came from Berlin to Hamburg to work for Marco Börries in his Star Lab in spring 1990, together with my friend and study mate Stefan. Both of us joined the project more or less at the same time and shared the same first name, which caused some confusion at first.

The situation in Hamburg needs some explaining if you are new to it. The Writer application that is the foundation of what we use today is not the first Star Writer – but thesedays it is often referred to as Star Writer 6 or Star Writer Graphic. Marco’s company Star Division, based in rural Lüneburg not far from Hamburg, had developed and sold with considerable success a text processing application with the same name, that was an MS-DOS application based on a home-grown graphics framework. A team of freelance programmers was working on it under the lead of Sven-Ola Tücke.

This was also the tool we used to write the first drafts for specifications, by the way.

The old Star Writer had a solid fanbase and sold quite well even after Star Lab started in Hamburg. So it is fair to say that the money we burned in Hamburg was earned in Lüneburg.

Marco, however, had the right feeling that graphical user interfaces were already around and taking up speed. The future (that is the time we live in now) would belong to applications running on the main graphical user interface platforms at this time, being Microsoft Windows, the X Window System and macOS. Of course there were voices that argued that graphical user interfaces were only hampering productivity and real pros would always use the command line. That may sound a bit funny today, but I took it all in my heart.

When I arrived there, development had pretty much advanced in the compatibility layer named Star View, that allowed portable programming of both operating system functions and graphical user interfaces. There was, however, no application yet. Because I had worked on a C++/X Window System project on the ODA standard (ISO 8613, Open Document Architecture), I had some background on this and formed with some others the core of the Star Writer project team.

Star Division logo

Tell us about the office location and team back then!

The offices of Star Lab at that time were at Heidenkampsweg, near Berliner Tor, in Hamburg in a quite modern building. I remember the adjacent gas station; many of us were heavy cigarette-smokers at that time, and I sometimes went there at night to get the next pack.

Dirk Bartels supervised the daily operations. He had a software company back in Berlin and


Tuesday
17 June, 2025


[en] Michael Meeks: 2025-06-17 Tuesday

21:00 UTC

face
  • Longish planning call, lunch, sync with Moritz & Eloy, Monthly mgmt meeting, sync with Andras, partner call late.
  • Out learner-driving with newly 17 years old E. Plugged through CofE child safeguarding foundations training on-line.

Monday
16 June, 2025


[en] Michael Meeks: 2025-06-16 Monday

21:00 UTC

face
  • Dropped car to garage with Laser, sync with Miklos, Thorsten, lunch with H. and M. Call with the marketing team, sync with Naomi, Eloy & more admin.

face

LibreOffice at the Linux Arena in Pordenone

Marco Marega writes:

Hi, I’m Marco, an Italian translator and Member of The Document Foundation. Twice a year I take part in an event in Pordenone to promote LibreOffice within the stand “Linux Arena” of the PNLUG Linux User Group. It’s inside a local fair, part of which is dedicated to technology, makers, electronics and so on.

For the event from April 25 – 27 we had a LibreOffice stand with a 32″ monitor, showing an Impress presentation about LibreOffice on a loop. At the stand I met different interested people – some of whom I already know since they visit the fair regularly, while others I saw for the first time.

There is always curiosity about LibreOffice, and this time I noticed an increasing demand about AI integration and related plugins. The LibreOffice coffee/beer mats were very much appreciated by visitors to the stand.

LibreOffice at the Linux Arena in Pordenone

The Pordenone Linux User Group invited other associations to share the stand, so there were also:

  • Trieste Linux Users Group, with a nice game to learn bash commands while trying to deactivate a bomb
  • Odoo group, presenting the ERP/CRM/…
  • Bergamo Linux Users group presenting OpenWRT and some other projects (Emiliano Vavassori is one of them)
  • A Blender expert
  • Another member who uses openSUSE for multimedia production
  • A corner where volunteers helped visitors to install Linux on their PCs, or to solve little problems

The next edition of the event will be on 22 – 23 November.

LibreOffice at the Linux Arena in Pordenone


Sunday
15 June, 2025


[en] Michael Meeks: 2025-06-15 Sunday

21:00 UTC

face
  • Left sleeping babes in bed. All Saints in the morning, back for a fine Pizza lunch - with Fathers Day Baked Alaska special.
  • Prepped tunes for the evening service, and ran that with Christine; home for some applied rest.

Saturday
14 June, 2025


[en] Michael Meeks: 2025-06-14 Saturday

21:00 UTC

face
  • Up early, helped E. tidy up somewhat, present opening, out bowling together as a family: fun.
  • Home for lunch, sung songs, played games the babes variously - nice, BBQ in the evening together.

face

Over the course of its 20-year history, the ODF standard has been adopted, or at least recommended, by numerous supranational bodies and several countries on almost every continent. However, this does not necessarily mean that the ODF standard is used in accordance with these decisions, which are often laws in their own right, as Microsoft’s substantial lobbying and misinformation campaigns aimed at protecting its revenue of around $25 billion generated by the proprietary OOXML format (DOCX, XLSX and PPTX) encourage the use of the latter. This is despite the fact that the disadvantages for national systems, communities of citizens and individuals are very easy to demonstrate: loss of control over content, interoperability problems and dependence on the commercial strategies of a single vendor.

The information in this post is based on my research into sources relating to the adoption or recommendations for the use of ODF. I began compiling this collection of documents around 2010 and continue to update it annually. Over the last twelve months, I have also used artificial intelligence in my research, which has helped me find some articles.

Unfortunately, formal adoption or recommendation of ODF does not guarantee its actual use in accordance with the law. For example, the latest version of Italy’s Digital Administration Code explicitly prohibits the use of OOXML because it is not a standard, yet this decision is largely ignored by public bodies.

SOVEREIGN BODIES

NATO requires all 28 member countries to use ODF as the standard format for document exchange.

UN and NGOs: UN organisations favour standard and open formats to ensure that all documents remain accessible and do not depend on expensive or restricted tools. This is why ODF is used for reports, policy drafts, and collaborative documentation between teams.

European Commission: has taken a strong stance in favour of open standards and promotes the use of formats such as ODF in documents through its open source software strategy. The European Parliament, the European Commission and the EUIPO (European Union Intellectual Property Office) have integrated LibreOffice and ODF into their internal workflows to ensure greater transparency and language neutrality.

EUROPE

Belgium: Since September 2007, all Belgian federal government departments have been required to accept and read ODF documents, and a memorandum has established ODF as the standard for the exchange of office documents within the federal public administration.

Denmark: From 1 April 2011, the Danish Parliament has mandated the use of ODF by state authorities for the exchange and archiving of documents, whereas previously agencies were only required to accept ODF documents. In recent weeks, articles have claimed that the Danish government will formally migrate to open-source software and, therefore, to ODF. We are, of course, seeking confirmation of this project.

Finland: The Ministry of Justice and other ministries have adopted ODF as the main document format.

France: The Référentiel Général d’Interopérabilité (RGI) recommends ODF as the preferred format for office documents in public administrations. Agencies are therefore encouraged to use ODF


face

Autor: Italo Vignoli

A lo largo de sus 20 años de historia, el estándar ODF ha sido adoptado, o al menos recomendado, por numerosos organismos supranacionales y varios países de casi todos los continentes. Sin embargo, esto no significa necesariamente …


Friday
13 June, 2025


[en] Michael Meeks: 2025-06-13 Friday

21:00 UTC

face
  • Sync with Dave in the morning, lots of back-to-back meetings, partner call, catch up & planning with Pedro, call with Philippe. H. home from Greece and N. too - lovely to have the family back together again!
  • Tidied the house somewhat for E's 17th birthday party, a mass of small(ish) girls over to the house dressed up variously, 22 girls + me - amusing. Chatted to larger babes.

face

LibreOffice 25.8 will be released as final at the end of August, 2025 ( Check the Release Plan ) being LibreOffice 25.8 Beta1 the second pre-release since the development of version 25.8 started at the beginning of December, 2024. Since the previous release, LibreOffice 25.8 Alpha1, 782 commits have been submitted to the code repository and 154 issues got fixed. Check the release notes to find the new features included in this version of LibreOffice.

LibreOffice 25.8 Beta1 can be downloaded 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 Matrix.

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

Happy testing!!

Download it now!


Thursday
12 June, 2025


[en] Michael Meeks: 2025-06-12 Thursday

21:00 UTC

face
  • Tech. planning call in the morning, great to have Thorsten & Stephan too, crush of meetings and allotropia merger fun to push on.
  • Sync with partners, Lily, Laser, counsel, Tracie. House-group in the evening; M. back home in the middle, lovely to have her back.

face

Screenshot of colour wheel being created in LibreOffice Calc

Regina Henschel writes:

Susanne Mohn asked on the German-language user’s mailing list how to create a colour wheel with LibreOffice. It was not about the colours themselves, but about the geometry. How do you create a circle or ring with equally sized sectors?

Very different solutions were proposed. Susanne Mohn, Harald Berger and I (Regina Henschel) have created a page in the LibreOffice Wiki so that these do not remain hidden in a thread. Due to the development process, some sample files are in German, but the page itself is in English.

Colour wheels can be used to create “doughnut charts” of data. Have fun exploring!

Colour wheel


Wednesday
11 June, 2025


[en] Michael Meeks: 2025-06-11 Wednesday

21:00 UTC

face
  • Up, mail chew, breakfast, to the OFE venue with Ludovic, met lots of interesting people, had a fine lunch together; encouraging talks about Poland and FLOSS.
  • Published the next strip around why Dammit did it: building open-roads. Back in the land of software strange things happen; eg. it was rumoured that the cost of the auxiliary Windows PCs, and Office licenses made it cheaper for Sun Microsystems to buy StarDivision and open-source OpenOffice.org than the alternative; thanks to Simon Phipps for the pointer.
    The Open Road to Freedom - strip#21 - why Dammit did it ?
  • To the airport, worked away on the plane.

face

The Document Foundation and LibreOffice support the international campaign @endof10 https://endof10.org/

The countdown has begun. On 14 October 2025, Microsoft will end support for Windows 10. This will leave millions of users and organisations with a difficult choice: should they upgrade to Windows 11, or completely rethink their work environment?

The good news? You don’t have to follow Microsoft’s upgrade path. There is a better option that puts control back in the hands of users, institutions, and public bodies: Linux and LibreOffice. Together, these two programmes offer a powerful, privacy-friendly and future-proof alternative to the Windows + Microsoft 365 ecosystem.

The real costs of switching to Windows 11

The move to Windows 11 isn’t just about security updates. It increases dependence on Microsoft through aggressive cloud integration, forcing users to adopt Microsoft accounts and services. It also leads to higher costs due to subscription and licensing models, and reduces control over how your computer works and how your data is managed. Furthermore, new hardware requirements will render millions of perfectly good PCs obsolete.

This is a turning point. It is not just a milestone in a product’s life cycle. It is a crossroads.

The new path: Linux + LibreOffice

These two programmes form the backbone of a free and open computing environment based on open standards. For individual users, public administrations, schools and businesses, this combination offers more than enough: it is mature and secure, and is already in use worldwide for mission-critical workloads. Furthermore, using open standards protects users against any attempts by software developers to control them.

Here’s what this alternative offers:

  1. A modern, stable and unrestricted operating system, accessible to all users thanks to intuitive distributions that allow each user to choose the configuration that best suits their needs. It also offers regular updates, long-term support versions and communities where people can help each other and develop their digital knowledge together.
    Unlike Windows 11, Linux works with all personal computers that ran Windows 10, meaning there is no need to replace your old PC. Those with even older computers can also find a suitable version of Linux, extending their useful life and reducing electronic waste.
  2. LibreOffice is a complete office suite offering word processing, spreadsheets, presentations, drawing and database tools. It respects freedom and data because it is based on an open, standard document format (ODF), and is compatible with Microsoft’s proprietary formats (DOCX, XLSX and PPTX). This gives users control, as Microsoft cannot decide to end support at any time, as it is doing with Windows 10.
    LibreOffice is supported by a global community of volunteers, consultants, and companies who provide free and paid professional support, ensuring the ongoing development of the software and the prompt resolution of security and operational issues. There are no licence fees, telemetry or vendor lock-in.
  3. Both Linux and LibreOffice are based on transparency. This means that all documents saved in the standard format will always be available because the format is open, and all

face

The Document Foundation y LibreOffice apoyan la campaña internacional @endof10 https://endof10.org/

La cuenta atrás ha comenzado. El 14 de octubre de 2025, Microsoft dejará de dar asistencia a Windows 10. Esto dejará a millones de usuarios y organizaciones con una …


Tuesday
10 June, 2025


[en] Michael Meeks: 2025-06-10 Tuesday

21:00 UTC

face
  • Up earlyish, off to the venue - talks all day about various aspects of commercial open-source; encouraging.

face

General Activities

  1. LibreOffice 24.8.7 was announced on May 8
  2. Olivier Hallot (TDF) added a help page for Page Layout, expanded help for paragraph justification, updated menu paths in Help, added help pages for newly-added Calc functions and of-pie charts, updated help for Business cards and Labels, improved extended tooltips and error messages for Manage Names dialog, corrected an example spreadsheet used for Calc Data Statistics help and improved help for IsNull BASIC function among many other Help cleanups and updates
  3. Gábor Kelemen (allotropia) did many code cleanups
  4. Tomaž Vajngerl (Collabora) continued polishing support for embedded fonts in PowerPoint files and fixed unexpected changing of background images upon saving and reloading in Draw
  5. Darshan Upadhyay, Szymon Kłos, Michael Meeks and Jaume Pujantell (Collabora) worked on LOKit used by Collabora Online. Szymon also implemented saving checkbox state to XLSX files
  6. Gökay Şatır (Collabora) fixed an issue in Draw with connector text disappearing when “Adjust to contour” option was active
  7. Marco Cecchetti (Collabora) added a feature to select colour palettes for chart data series
  8. Pranam Lashkari (Collabora) fixed an issue with unwanted expansion of reference mark fields after insertion and typing
  9. Miklós Vajna (Collabora) continued improving the handling of tracked changes that depend on each other
  10. Xisco Faulí (TDF) implemented new Calc functions TEXTSPLIT, TEXTBEFORE and TEXTAFTER, made it so glue points in PowerPoint shapes are imported, fixed an issue with connectors in PPTX files becoming misaligned due to negative rotation, added some new automated tests, upgraded many dependencies, fixed crashes and did many code cleanups and optimisations
  11. Michael Stahl (allotropia) worked on multi-user editing based on a conflict-free replicated data type (CRDT) leveraging yrs, a Rust port of Yjs
  12. Mike Kaganski (Collabora) fixed an error when accessing cells via BASIC methods after deleting cells with the RemoveRange method, made it so BASIC’s Time() function returns a Date type, greatly improved the loading time of Writer documents with lots of bookmarks and lots of tables, made it so empty Writer paragraphs correctly follow proportional line spacing smaller than 100%, fixed an issue preventing the export of Draw / Impress documents to SVG from Basic IDE context, improved BASIC error messages, fixed incorrect width in SVG text with “fit-to-size” attribute, fixed an issue with macros not pausing for the duration of executing dialogs and helped Heiko with the new Welcome dialog
  13. Caolán McNamara (Collabora) fixed an issue with expanding the list of events in the Events tab of Customize dialog, fixed crashes and many issues found by static analysers and did code cleanups and optimisations
  14. Stephan Bergmann (allotropia) worked on the WASM build. He also adapted the code to compiler changes and did code cleanups
  15. Noel Grandin (Collabora) improved the loading speed of XLSX files with lots of customFormat attributes in rows, dramatically improved the rendering speed of documents with large page fills when hardware acceleration is used, greatly improved the loading speed of XLSX files with lots of formulas, conditional formatting and comments and improved

Older blog entries ->