LibreOffice and Google Summer of Code 2025: The results

This year, LibreOffice was once again a mentoring organization in the Google Summer of Code (GSoC), a global program focused on bringing more developers into free and open source software development. Seven projects were finished successfully. Contributors and mentors enjoyed the time, and here we present some of the achievements, which should make their way into LibreOffice 26.2 in early February 2026! You can experiment with the new features by using daily builds and report any problems in our bug tracker. Import Markdown files into LibreOffice Writer by Ujjawal Kumar Chouhan Mentors: Thorsten Behrens (Collabora), Ilmari Lauhakangas (TDF) Requests to add support for the simple text formatting language known as Markdown to LibreOffice have been more and more frequent. These days Markdown is often encountered in forum posts, chat messages and readme files. In fact, the content of the website of The Document Foundation is written in Markdown. Thanks to this project, LibreOffice now supports importing Markdown files and pasting Markdown content into Writer as well as pasting Markdown tables into Calc. The supported dialect is CommonMark with GitHub-style table syntax and the library used is MD4C. Additionally, Collabora developers added support for exporting to Markdown from Writer. Learn more

The artificial complexity of OOXML files (the PPTX case)

This is the third and final post on the topic of the artificial complexity of the OOXML format. This complexity is the result of careful design aimed at preventing interoperability. Developers have to deal with a veritable “maze” of tags, even for the simplest content. This binds users to the Microsoft ecosystem, providing the first example of standard-based lock-in. The PPTX case To demonstrate the difference in complexity between Impress and PowerPoint XML schemas in ODF and OOXML formats, I created a simple eight-slide presentation summarising the most common types: title and subtitle, centred text, bulleted list, table, vector image, photo, colour graphics and video. I created the same file using both software programmes, starting from a basic template without a background to prevent interference with the slide format and, consequently, the XML schema. This is the PDF file of the presentation (the first seven slides are identical, while the video on the last slide is replaced by a static image): To perform the analysis, I duplicated and renamed the two files, replacing the original extension with ‘ZIP’, and then unzipped them to create two folders containing all the files from their respective XML schemas. The LibreOffice folder is very

The artificial complexity of OOXML files (the DOCX case)

The complexity of the OOXML format is linked to its design and was deliberately created to make the format more difficult for non-Microsoft software developers to implement. Compatibility issues are caused by a veritable “maze” of tags used even for the simplest content, which binds users to the Microsoft ecosystem in the first example of standard-based lock-in. The DOCX case To demonstrate the difference in complexity between the XML schemas of Writer and Word text documents in the ODF and OOXML formats, I used two classic English theatre plays: William Shakespeare’s Hamlet and Oscar Wilde’s The Importance of Being Earnest. I downloaded the text versions of these works from Project Gutenberg — a library of classic texts for which US copyright has expired — and deleted the introductions and conclusions added by Project Gutenberg, without making any other changes. I then repeated this process for both documents. I copied all the text and pasted it, without any formatting, into two newly created blank documents. For Writer, I used the template that I usually use for unstructured documents; for Word, I did not use a template. This means that, in Writer, the XML schema contains information about the template (margins, paragraph

TDF Annual Report 2024

The Annual Report of The Document Foundation describes the foundation’s activities and projects, especially in regard to LibreOffice and the Document Liberation Project. We’ve been posting sections of the 2024 report here on the blog, and now the full version is available in PDF format on TDF’s Nextcloud server in two different versions: low resolution (6.6MB) and high resolution (56.2MB). The Annual Report is based on the German version presented to the authorities. The document has been entirely created with free open source software: written contents have obviously been developed with LibreOffice Writer (desktop) and collaboratively modified with LibreOffice Writer (online), charts have been created with LibreOffice Calc and prepared for publishing with LibreOffice Draw, drawings and tables have been developed or modified (from legacy PDF originals) with LibreOffice Draw, images have been prepared for publishing with GIMP, and the layout has been created with Scribus based on the existing templates. We at The Document Foundation are very grateful to all contributors to our projects and communities in 2024 – none of this would be possible without you!

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

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): What you want to do with the magazines How many you want (1 – 5 copies) The address to which we should post them Include all of that that information in an email to us and let’s see

Best practices for creating and editing Open Document Format (ODF) files

Adhering to these guidelines can enhance productivity and guarantee that documents remain consistent, robust and accessible over time, irrespective of the platform. Firstly, use an editor such as LibreOffice that natively supports the format without conversion. This preserves the nuances of the ODF XML structure, supports all its features and reduces the risk of formatting issues or data loss. It also ensures that documents are fully compatible with the ISO standard. Secondly, use an up-to-date version of LibreOffice to benefit from continuous improvements in ODF feature management, avoid bugs that could cause file corruption (a rare event thanks to the robustness of the ODF format, but still possible) and enjoy the highest level of security in file management. Thirdly, use LibreOffice document templates and styles for all elements, such as headings, fonts, paragraphs, and tables, to ensure consistent formatting throughout the document. This allows you to make global changes quickly by changing the style rather than each individual element, and improves accessibility, as screen readers and other assistive technologies rely on a consistent structure. This also results in smaller, more robust ODF files. Creating and reusing LibreOffice templates is an excellent practice for companies that produce many similar documents (such