LibreOffice 26.8 and interoperability: preserving what cannot yet be read

LibreOffice 26.8 adds basic support for importing and exporting a range of chart types that Microsoft Office includes in OOXML files: box-and-whisker, funnel, Pareto, radial, treemap and waterfall charts. LibreOffice is unable to display or edit these charts, but it does recognise them, informs the user that the chart type is not yet supported, preserves the underlying definition unchanged, and rewrites it when the file is saved.

At first glance, this appears to be an admission of incompleteness, whereas it is actually an example of what implementing a proprietary format entails when the aim is interoperability – for the benefit of users, rather than a commercial strategy that treats users as mere tools.

What happened

Microsoft added these chart types to Office from 2016 onwards, storing them in a namespace generally referred to as ‘chartex’. The namespace is not part of the ISO/IEC 29500 text approved as an international standard, but is documented separately in Microsoft’s extension documentation.

This is entirely legal and perfectly normal commercial behaviour: a vendor improves its product and the file format evolves accordingly. The consequence, however, is that the format in everyday use is no longer the one that was standardised. The ISO number continues to be cited in tender documents and policy documents, but the files being exchanged are different.

For any implementer other than the vendor, this creates a permanent state of delay. This is not a one-off gap to be bridged with sufficient effort, but a structural delay, as the specifications are in the hands of a vendor that does not publish its release schedule, with priorities defined according to commercial criteria.

Three possible responses

An office suite that encounters a chart it does not recognise has three options:

  1. It can reject the file. This is an honest but pointless solution: the user is left with a document they cannot open and concludes that the software does not work.
  2. It can discard what it does not understand. The file opens, the chart disappears, and the user only realises this when the document is forwarded to a colleague and the chart is no longer present. This is the most damaging outcome, as the loss occurs silently and the blame falls on whoever opened the file last.
  3. They can retain what they are unable to display. The user is informed that this type of chart is not supported, so they see a placeholder rather than a blank space, and the underlying definition remains intact when the document is transferred from one application to another. The document is restored in full when returned to the source application.

LibreOffice 26.8 adopts the third option, the only one of the three that respects the fact that the document belongs to the user rather than to the software – or, indeed, to the company that develops the software.

Unfortunately, there is a limitation, and this is an exception. Charts with regional maps contain extensive geographical information that LibreOffice is unable to preserve. The chart type survives the import-export cycle, but very little of its content remains intact.

Why this is important beyond charts

The Chartex case is of limited scope. The model, however, is not.

All organisations whose documents are written in a format controlled by a single vendor accept a dependency they are unable to manage, because the specifications may change without notice, with the addition of features that are only understood by a single implementation.

Nothing untoward needs to happen for the organisation’s archives to become progressively more difficult to read by all other software.

The Open Document Format is not immune to change, but it changes differently. Revisions are proposed, discussed and approved by a technical committee at OASIS, whose work is public, and are published as version specifications that anyone is free to implement.

An implementer wishing to support ODF 1.4 can read the ODF 1.4 specification and put it into practice. This is the only difference, and it is sufficient.

The bidirectional preservation of unsupported features is what distinguishes a responsible implementation under current conditions, but it does not constitute an improvement on those conditions. LibreOffice is the only office suite to adopt this approach, in order to protect users and the content within their documents.

New “LibreOffice Expert 2026/2027” magazines available for schools and local communities

LibreOffice Expert magazines

A few weeks ago, Linux New Media released an updated version of its “LibreOffice Expert” magazine, which contains tutorials, tips and tricks about the office suite. And some articles were contributed by members of the LibreOffice community! The magazines come with DVDs that include LibreOffice for Linux, Windows and macOS, alongside extra templates, extensions, videos and guidebooks.

We have some copies to give away, for schools, universities, libraries and local communities. Ideally, we’d like to get these magazines out to places where internet connections aren’t always available – so that the users can really benefit from the DVDs.

So, if you can help us to distribute these magazines, drop us a line! Please note that we have 50 copies in total and can therefore only send a maximum of five copies to any one place, to make sure many communities get a chance. When you contact us, please include this information (any requests without information cannot be fulfilled and will be ignored):

  1. What you want to do with the magazines
  2. How many you want (1 – maximum 5 copies)
  3. The address to which we should post them

Include all of that that information in an email to us with subject line “LibreOffice Expert for communities” and let’s see what we can do!

(Note: if you want to buy the magazine directly from the publisher, you can do so here.)

LibreOffice 26.8 and the languages for which nobody is paid

The most significant new features in LibreOffice 26.8 concern writing systems, and it is worth explaining what has been done and, above all, why it has been done, as there is an important decision behind the developers’ work.

What has been done

Writer now automatically detects the paragraph direction when opening or pasting documents or plain text, without requiring the user to set it manually.
Spaces at the end of a line are positioned according to the paragraph direction rather than that of neighbouring characters, which corrects a long-standing issue with how line breaks are handled in mixed Arabic and Latin texts.

Object resize handles now work correctly in right-to-left CJK documents and in vertical documents.

Bidirectional control characters are displayed alongside other formatting marks, so that invisible directional substitutions can be both viewed and edited.

The semantics of paragraph alignment have been revised. New documents use justified alignment by default rather than left-justified, and changing the paragraph direction no longer overrides the explicitly set alignment. This is a small change with a significant impact, as a document written in Arabic and one written in English can now share a template without conflicting.

In Calc, when typing text from right to left into an empty cell, the direction of that cell is now set automatically.

LibreOffice Math has gained functions and operators for the N’Ko and Adlam alphabets, along with left-pointing vector arrows and harpoons for right-to-left formulas, without which mathematical notation in these two alphabets cannot be composed correctly.

Finally, the names of fonts registered in languages other than the interface language are now recognised, so that a document created in a Japanese or Russian installation is displayed using the fonts chosen by the author rather than substitute ones.

Why this is unusual

N’Ko is a writing system devised in 1949 by Solomana Kanté for the Mandingo languages of West Africa. Adlam was devised in the late 1980s by two teenage brothers, Ibrahima and Abdoulaye Barry, for the Fulani language, which until then had been written using adapted Arabic or Latin scripts – an inadequate solution. Both scripts run from right to left, are used by populations numbering tens of millions of people, and have been added to Unicode over the last twenty years.

Neither language represents a market. The native speakers concerned do not, as a whole, constitute a customer base large enough to justify the time spent on development based on a commercial analysis. No tender process, anywhere in the world, has led to the completion of this work. No corporate client has requested it. No competitive pressure has made it necessary.

The contributor who added support for N’Ko and Adlam to LibreOffice Math is a volunteer.

Much of the work on bidirectional text was carried out by a developer employed by The Document Foundation, which is funded by donations.

The renaming of the CJK text grid option, so that it correctly referred to the genkō yōshi handwritten grid used in Japanese typesetting, was carried out by a member of TDF’s staff.

Native support for OpenType font variations – which is of enormous importance for alphabets whose typography cannot be approximated by modifying the dimensions of a Latin character – was provided by a type designer working independently of any company.

A fundamental difference

Every software vendor must decide which users are worth serving: if the software is a product, the decision is made on the basis of a business case, and languages that cannot pay for themselves fall by the wayside.

A foundation does not have this constraint, and does not need to ask itself whether an alphabet justifies its development costs, as there is no revenue stream against which to make this choice. The work is carried out because someone with the relevant expertise has deemed it worthwhile, and there are no reasons to prevent it.

This is the practical difference between software managed by a foundation and that managed by a vendor, and it is evident in the release notes. LibreOffice is available in 120 languages for this very reason: the number is a consequence of the governance model rather than a marketing objective.

This explains why the argument in favour of open-source software in public administration is not a question of cost, because a public body has obligations towards citizens who do not represent a commercial interest: users of minority languages, users of assistive technologies, and people living in regions that no vendor prioritises.

Software developed on the basis of a business case will only serve these citizens if doing so is profitable. Software developed without a business case can serve them, as a matter of course and in line with the principles of open-source software.

Day 2 of the LibreOffice Conference 2026 begins

Community dinner

Well, that’s a photo from last night’s community dinner, but now the second day talks are beginning!

As with yesterday, we will be live-streaming most sessions on the schedule (in track rooms 1 and 2) and making recordings of all. Find out more by following our communication channels, where we’ll post the streaming links as we go live:

Here’s LibreOffice’s Engineering Steering Committee having their session:

Engineering Steering Committee session

The LibreOffice Conference 2026 begins!

Registration booth

Yes, the LibreOffice Conference 2026 has started in Pordenone, northern Italy. If you’re attending in-person, we look forward to seeing you!

If you want to attend remotely, we will be live-streaming most sessions on the schedule (in track rooms 1 and 2) and making recordings of all. Find out more by following our communication channels, where we’ll post the streaming links as we go live:

Enjoy the conference, and a big thanks to the organisers for making it happen 😊

Auditorium