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.
por Italo Vignoli Algunos pensaron que el último artículo era solo una crítica a Microsoft por usar OOXML, pero no era solo eso. También quería alertar sobre programas que parecen libres, como OnlyOffice, que en realidad se alían con Microsoft y ayudan a mantener a la gente atrapada en sus
Everyone loves having shiny new features in LibreOffice. But how do we get them? Many are developed by volunteers and people in the ecosystem. But another great source of new features is the Google Summer of Code (GSoC), a global, online program focused on bringing new contributors into open source
Berlin, 19 February 2026 – LibreOffice 25.8.5, the fifth update to the FOSS office suite [1] developed by volunteers for personal productivity in office environments on Windows, MacOS and Linux, has landed at www.libreoffice.org/download. LibreOffice 25.8.5 is based on the highly robust LibreOffice technology platform, which supports the development of
Nos enorgullece compartir que LibreOffice ha sido reconocido oficialmente como líder en valor (mejor relación calidad-precio) para 2026 por Capterra. En un entorno digital cada vez más dominado por modelos de suscripción y costos crecientes, este reconocimiento reafirma nuestra misión de ofrecer una suite ofimática potente, de nivel profesional y
El gobierno del estado de Schleswig-Holstein, en Alemania, está consolidando uno de los proyectos de soberanía digital más relevantes de Europa: la migración de 30.000 estaciones de trabajo a LibreOffice. Más que un simple cambio de software, esta iniciativa ofrece valiosas lecciones sobre viabilidad operativa y eficiencia tanto para organismos
We are incredibly proud to share that LibreOffice has been officially recognized as a leader in value for 2026 by Capterra. As the digital landscape becomes increasingly defined by subscription models and rising costs, this recognition reinforces our mission to provide a powerful, professional-grade office suite that remains accessible to
The LibreOffice community was at FOSDEM 2026, to talk to users, answer questions, and encourage people to join the project. And we had merch: Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party.
Implementing Firebird 4 Protocol Versions 16 and 17 is crucial for utilizing the advanced features, security enhancements, and performance improvements introduced in Firebird 4.0 and 4.0.1. Using updated clients that support these protocols prevents performance degradation and ensures access to modern functionalities. Key Features Supported by Protocol 16 (Firebird 4.0)Wire Protocol Encryption:&
El 17 de febrero de 2026 celebramos 14 años desde que The Document Foundation fue reconocida oficialmente como organización sin fines de lucro en Alemania. Desde el primer día, nuestra misión ha sido clara: impulsar el desarrollo de software libre y de código abierto que potencie la productividad y la
17 February 2026 marks the 14th anniversary of The Document Foundation’s recognition as a non-profit organisation under German law. The foundation is focused on developing free and open-source software for individual productivity. This focus has guided the development of LibreOffice and the software tools for liberating proprietary formats released by
Many interpreted the last article in this series as an attack on Microsoft for using the OOXML format against users’ interests. However, this was only one of my objectives, as I also wanted to raise users’ awareness of fake open-source software, such as OnlyOffice, which partners with Microsoft in a
LibreOffice es software libre, pero “libre” significa mucho más que simplemente no tener costo. Se trata de otorgar a los usuarios libertades fundamentales sobre cómo ejecutar, compartir, estudiar y mejorar su software y sus computadoras, devolviéndoles el control. Por ejemplo, el código fuente de LibreOffice —es decir, la “receta” legible
LibreOffice is free software – but “free” is about way more than just being zero-cost. It’s about giving users fundamental freedoms in how they run, share, study and improve their software and computers – giving control back to them. For example, the source code for LibreOffice – that is, the
La comunidad del proyecto ODF Toolkit ha anunciado oficialmente el lanzamiento de la versión 0.13.0. Este lanzamiento marca un punto de transición significativo en la historia del proyecto, ya que es la última versión que ofrece compatibilidad con JDK 11. A partir de ahora, la atención se centrará en las
General Activities Olivier Hallot (TDF) improved Writer help for hyphenation zones and controlling section visibility, fixed the help example for Calc’s SUMIF function, clarified the topic of fixed colours in the help for document themes, expanded the help for Calc’s sort options, explained in help the option for removing cross-document
BERLIN, Germany — The ODF Toolkit community is proud to announce the official release of version 0.13.0. This release marks a significant transition point in the project’s history, representing the last release to support JDK 11, with the project pivoting toward modern Java long-term support (LTS) releases. Release Highlights: Stability
Here’s our summary of updates, events and activities in the LibreOffice project in the last four weeks – click the links to learn more… We started January with some news about The Document Foundation’s governance: an updated Conflict of Interest Policy for the Board of Directors. Later in the month,
LibreOffice 26.2 se osredotoča na izboljšave, ki pomembno vplivajo na vsakodnevno delo in prinašajo boljšo zmogljivost, bolj tekoče delovanje s kompleksnimi dokumenti in izboljšano združljivost z vsemi datotekami, ustvarjenimi v drugih pisarniških paketih. Ne glede na to, ali pišete poročila, upravljate s preglednicami ali pripravljate predstavitve, je delo bolj odzivno in zanesljivo.
LibreOffice je vedno omogočal uporabnikom nadzor. LibreOffice 26.2 nadaljuje to tradicijo s krepitvijo podpore za odprte standarde za dokumente in zagotavljanjem dolgoročnega dostopa do vaših datotek brez naročnin, licenčnih omejitev ali zbiranja podatkov. Vaši dokumenti ostanejo vaši, za vedno.
Za to izdajo stoji svetovna skupnost sodelavcev. Razvijalci, oblikovalci, prevajalci, preizkuševalci kakovosti in prostovoljci iz vsega sveta so sodelovali pri pripravi več sto popravkov in izboljšav. Rezultat njihovih prizadevanj je paket, ki ne le dodaja nove funkcije, ampak iz izdaje v izdajo izboljšuje tudi kakovost, doslednost in stabilnost.
Not too long ago, a change landed, that brought Biff12 clipboard format support in Calc v.26.2 – thanks Laurent!
It was an easyhack that I authored some time ago; and Laurent volunteered to implement that long-standing missing feature. The small detail was, that the feature was Windows-specific (it is trivial to get the wanted clipboard content there, simply copying from Excel), while Laurent developed on another platform.
Laurent had made the majority of work, before he was stuck, without being able to test / debug further changes. Then, he asked me, if there a way to continue on the platform he used.
At that time, I answered, that no, one would need Windows (and Excel) to continue the implementation. So I jumped in, and added the rest, and in the end, we have created the change in co-authorship.
But later, when part of my code turned out problematic, and I needed to fix it and create a unit test for it, I discovered a trick, that could put Biff12 data into system clipboard on any platform, without Excel – allowing then just paste, and debug everything that’s going on there. It relies on UNO API, and can be implemented e.g. in Basic:
function XTransferable_getTransferData(aFlavor as com.sun.star.datatransfer.DataFlavor) as variant
if (not XTransferable_isDataFlavorSupported(aFlavor)) then exit function
oUcb = CreateUnoService("com.sun.star.ucb.SimpleFileAccess")
oFile = oUcb.openFileRead(ConvertToURL("/path/to/biff12.clipboard.xlsb"))
dim sequence() as byte
oFile.readBytes(sequence, oFile.available()) ' changes value type of 'sequence' to integer
XTransferable_getTransferData = CreateUnoValue("[]byte", sequence)
end function
function XTransferable_getTransferDataFlavors() as variant
aFlavor = new com.sun.star.datatransfer.DataFlavor
aFlavor.MimeType = "application/x-openoffice-biff-12;windows_formatname=""Biff12"""
XTransferable_getTransferDataFlavors = array(aFlavor)
end function
function XTransferable_isDataFlavorSupported(aFlavor as com.sun.star.datatransfer.DataFlavor) as boolean
XTransferable_isDataFlavorSupported = (aFlavor.MimeType = "application/x-openoffice-biff-12;windows_formatname=""Biff12""")
end function
sub setClipboardContent
oClip = CreateUNOService("com.sun.star.datatransfer.clipboard.SystemClipboard")
oClip.setContents(CreateUNOListener("XTransferable_", "com.sun.star.datatransfer.XTransferable"), nothing)
end subThe first three functions are Basic implementation of XTransferable interface.
Running setClipboardContent will prepare the system clipboard on any platform, using a trick of implementing arbitrary UNO interface using CreateUNOListener; and after that, pasting into Calc would allow to see if things work (if content of /path/to/biff12.clipboard.xlsb is pasted, as expected), and make improvements. If I knew this trick back then, I would of course share it with Laurent; but I thought I’d put it here now, so maybe it helps me or someone else in the future. (Note that application/x-openoffice-biff-12;windows_formatname="Biff12" there in the code was the name introduced by Laurent in the discussed commit; indeed, that, and the actual data in the file, would depend on the exact format that you work with.)
Here’s a selection of new features in LibreOffice 26.2, which we released on Wednesday. (This video is also available on PeerTube.) Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party. YouTube privacy policy
Desafortunadamente, sigo leyendo sobre defensores del software de código abierto que utilizan alegremente los formatos propietarios DOCX, XLSX y PPTX de Microsoft para sus documentos y, por lo tanto, prefieren software propietario como OnlyOffice a LibreOffice. Otros escriben cosas escandalosas como: «OOXML es un formato estándar y tenemos que aceptarlo».
La suite ofimática más rápida, más perfeccionada y bajo su total control. Nos complace anunciar el lanzamiento de LibreOffice 26.2, la última versión del paquete ofimático gratuito y de código abierto en el que confían millones de usuarios en todo el mundo. Esta versión hace que sea más fácil que
If you have a commented text range, which gets deleted while track changes is on and you later save and load this with Writer's DOCX filter, that works now correctly.
This work is primarily for Collabora Online, but the feature is available in desktop Writer as well.
It was already possible to comment on text ranges. Comments were also supported inside deletes when track changes is enabled. These could be already exported to and imported from DOCX in Writer. But you could not combine these.
With the increasing popularity of commenting text ranges (rather than just inserting a comment with an anchor), not being able to combine these was annoying.
Here is how a commented text range inside a delete from DOCX now looks like, note the semi-transparent comment hinting it's deleted:
Commented text range, inside a tracked delete, in DOCX, Collabora Online
As a side effect, this also fixes the behavior in desktop Writer, which crosses out deleted comments:
Commented text range, inside a tracked delete, in DOCX, desktop
In the past, the "is this deleted" property was not visible in the render result:
Commented text range, inside a tracked delete, in DOCX, Collabora Online, old bad state
And it was also bad in desktop Writer:
Commented text range, inside a tracked delete, in DOCX, desktop, old bad state
This required changes to both DOCX import and export: a comment could be deleted or could have an anchor which is a text range, but you couldn't have both.
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 changes. Core side:
You can get a development edition of Collabora Online 25.04 and try it out yourself right now: try the development edition. 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 (26.8).
El camino hacia el lanzamiento oficial de LibreOffice 26.2 entra en su etapa final. Acabamos de publicar RC2 (Release Candidate 2), la segunda versión “candidata” a convertirse en la versión oficial. ¿Qué ha cambiado? Desde la primera versión de prueba (RC1), la comunidad ha trabajado intensamente: se incorporaron 137 mejoras
FOSDEM es el mayor evento europeo de software libre y de código abierto (FOSS), y se celebrará los días 31 de enero y 1 de febrero en Bruselas, Bélgica. El proyecto y la comunidad de LibreOffice estarán presentes. Visita nuestro stand, conversa con nosotros y llévate material promocional (adhesivos, folletos
In LibreOffice development, there are many cases where you want to validate some documents against standards: either Open Document Format (ODF) or MS Office Open XML (OOXML). Here I discuss how to do that.
Update: Article updated to reflect that odfvalidator 0.13.0 has just released.
ODF is the native document file format that LibreOffice and many other open source applications use. It is basically set of XML files that are zipped together, and can describe various aspects of the document, from the content itself to the way it should be displayed. These XML files have to conform to ODF standard, which is presented in XML schemas. The latest version of ODF is 1.4, which is yet to be implemented in LibreOffice.
You can find more about ODF in these links:
There are various tools to do the validation, but the preferred one is the ODF Toolkit Validator:
Compiled binaries of ODF Toolkit can be downloaded from the above Github project:
Then, you can use the ODF validator this way:
$ java -jar odfvalidator-0.13.0-jar-with-dependencies.jar test.odt
You may also use the online validator, odfvalidator.org, to do a validation.
Online odfvalidator toolPlease read this disclaimer before using:
This service does not cover all conformance criteria of the OpenDocument Format specification. It is not applicable for formal validation proof. Problems reported by this service only indicate that a document may not conform to the specification. It must not be concluded from errors that are reported that the document does not conform to the specification without further investigation of the error report, and it must not be concluded from the absence of error reports that the OpenDocument Format document conforms to the OpenDocument Format specification.
MS Office Open XML (OOXML) is the native standard for Microsoft documents format. It is also a set of XML files zipped together, and conform to some XML schemas.
You can find out more about OOXML here:
There are tools to do the validation, and the one is used in LibreOffice is Office-o-tron. One can use it with below command to validate an example file, test.docx:
$ java -jar officeotron-0.8.8.jar ~/test.docx
Office-o-tron can be downloaded from dev-www.libreoffice.org server of LibreOffice, and this is currently the latest version:
It is worth noting that Office-o-tron can be also used to validate ODT files.
To go beyond the current ODF standard, new features are sometimes introduced as “ODF extensions”, then are gradually added to the standard. You can read more in TDF Wiki:
In these cases, you may see validation errors for such extensions. For example:
test.odt/styles.xml[2 …
LibreOffice 26.2 will be released as final at the beginning of February, 2026 (check the Release Plan). LibreOffice 26.2 Release Candidate 2 (RC2) brings us closer to the final version, which will be preceded by Release Candidate 3 (RC3). Since the previous release, LibreOffice 26.2 RC1, 137 commits have been
Happy new year 2026! I hope that this year will be great for you, and the global LibreOffice community, and the software itself! I hereby discuss the past year 2025, and the outlook for 2026 in the development blog.
At The Document Foundation (TDF), our aim is to improve LibreOffice, the leading free/open source office suite that has millions of users around the world. Our work is community-driven, and the software needs your contribution to become better, and work in a way that you like.
My goal here, is to help people understand LibreOffice code easier via EasyHacks and tutorials, and eventually participate in LibreOffice core development to make LibreOffice better for everyone. In 2025, I wrote 14 posts around LibreOffice development in the dev blog (4 of them are unpublished drafts).
Focus of the development blog for 2026 in this blog will be:
You can provide feedback simply by leaving a comment here, or sending me an email to hossein AT libreoffice DOT org.
We provide mentoring support to the individuals who want to start LibreOffice development. You are welcome to contact me if you need help to build LibreOffice and do some EasyHacks via the above email address. You may also refer to our Getting Involved Wiki page:
Let’s hope a better year for LibreOffice (and the world) in 2026.
General Activities LibreOffice 25.8.4 was announced on December 18 Olivier Hallot (TDF) added a help page for Markdown in Writer, JSON in Calc, updated or improved help for View and Appearance options, accessibility options, sort criteria in Calc, file conversion filters, ODF versions, handling of empty cells in Calc, Data
The bullet support in Impress got a couple of improvements recently, some of this is PPTX support and others are general UI improvements.
This work is primarily for Collabora Online, but the feature is available in desktop Impress as well.
Probably the most simple presentations are just a couple of slides, each slide having a title shape and an outliner shape, containing some bullets, perhaps with some additional images. Images are just bitmaps, so let's focus on outliner shapes and their outliner / bullet styles.
What happens if you save these to PPTX and load it back? Can you toggle between a numbering and a bullet? Can you return to an outliner style after you had direct formatting for your bullet?
The first case was about bullet editing of this document:
Outliner shape with 3 outliner styles
If you pressed enter at the end of 'First level', then pressed <tab> to promote the current
paragraph to the second level, nothing happened. The reason for this was that our PPTX export was
missing the list styles of shapes, except for the very first list style. And the same was missing on
the import side, too. With this, not only the rendering of the bullets are OK, but also adding new
paragraphs and using promoting / demoting to change levels work as expected.
The second case was about this document, where the second level had a numbering, not a bullet:
Outliner shape with a numbering on the second level
We only had UI to first toggle off a numbering to no numbering, then you could toggle on bullets. Now it's possible to do this change in one step.
The last case was about styles. Imagine that you had a master page with an outline shape and some reasonably looking configuration for the first and second levels as outline styles:
Outliner shape with two outline styles
Notice how the last paragraph has a slightly inconsistent formatting, due to direct formatting. Let's fix this.
Go to the end of the last bullet, which is currently not connected to an outline style, toggle bullets off and then toggle it on again. Now we clear direct formatting when we turn off the bullet, so next time you turn bullets on, it'll be again connected to the outline style's bullet configuration and the content will look better.
Note how this even improves consistency: Writer was behaving the same way already, when toggling bullets off and then toggle on again resulted in getting rid of previously applied unwanted direct formatting.
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 changes. Core side:
| Imprint Privacy Policy | |
|
The Document Foundation is not responsible for the content on planet.documentfoundation.org. However - if you have any concerns about content please contact act Mike Saunders for moderation. Copyright information: Unless otherwise specified in the author's blog, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the "Mozilla Public License v2.0". "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy. |
 |
| this site runs a modified version of planet.opensuse (https://github.com/openSUSE/planet.opensuse.org) © 2010 Pascal Bleser and the openSUSE Community. | |