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.
Fin dalla sua fondazione nel 2010, The Document Foundation ha usato il logo di LibreOffice. Si è trattato di una scelta deliberata, perché un progetto giovane aveva bisogno di concentrare la propria visibilità su un unico nome e un unico marchio, e LibreOffice era il nome che le persone dovevano conoscere. Sedici anni dopo, il […]
Desde su fundación en 2010, The Document Foundation ha utilizado el logotipo de LibreOffice para representarse. Fue una decisión deliberada: como proyecto joven, necesitaba concentrar el reconocimiento en un solo nombre y una sola imagen, y LibreOffice era el nombre que la gente debía conocer. Dieciséis años después, la labor
Since its founding in 2010, The Document Foundation has used the LibreOffice logo to represent itself. This was a deliberate choice: a young project needed to concentrate recognition on a single name and a single mark, and LibreOffice was the name people needed to know.
Sixteen years later, the foundation’s work extends well beyond the product. TDF takes part in the development of the Open Document Format (ODF) standard, contributes to policy discussions on interoperability and digital sovereignty, and works with public administrations, standards bodies and other open source organisations. In these contexts, the foundation speaks as an institution, not as a software project, and it needs a signature of its own.
For this reason, we have worked with URA Design to create a visual identity for The Document Foundation, consisting of a logo, a colour palette and a typeface. The logomark is a stylised page, a reference to the documents and the document standard at the centre of the foundation’s mission. It is shown here in its primary version.
The colour palette is built around the green of the logo, with a neutral scale for text and backgrounds. All the text and background combinations recommended in the guide meet the WCAG 2.1 contrast requirements, so that materials produced with the new identity remain accessible.
The typeface is Inter, designed by Rasmus Andersson and released under the SIL Open Font License. It is used for the wordmark of the logo as well as for all texts, from reports and presentations to the website. A typeface released under a free licence is consistent with the foundation’s mission: anyone can use it, in LibreOffice or in any other application, without restrictions.
Nothing changes for LibreOffice. Its name, logo and visual identity remain exactly as they are. The two identities have different roles: LibreOffice identifies the software, while The Document Foundation identifies the organisation that hosts LibreOffice and its community, and represents them in the wider world.
The logo package is available for download at https://tdf.io/tdflogo. It includes vector (SVG) and raster (PNG) versions of the logo, a favicon, and avatars for social media. The Visual Identity Style Guide explains which version of the logo to use in each context, and sets out the colour palette, the typography and the rules for applying them consistently. Use of the logo is governed by TDF’s trademark policy.
Over the coming months, the new identity will replace the LibreOffice logo on the foundation’s website, social media accounts and institutional documents. Templates for LibreOffice Writer and Impress will also follow. If you maintain pages or materials that refer to The Document Foundation as an organisation, please update them with the new files. Pages that refer to LibreOffice should continue to use the LibreOffice logo.
Questions about the visual identity and its use can be sent to italo@documentfoundation.org
Lamentablemente, el lanzamiento de LibreOffice 26.8.1 ha sido complicado; primero, debido a una serie de problemas menores con el empaquetado de la versión para Windows y, posteriormente, a un fallo grave en el servidor de descargas, lo que nos obligó a regresar a la versión anterior durante algunos días. Hoy,
Un profilo tecnico del formato ODF La maggior parte degli utenti di PC non percepisce come un problema l’uso del formato proprietario OOXML, che affida a Microsoft la gestione dei propri contenuti rinunciando alla propria sovranità digitale. Questa è una conseguenza dell’attività di comunicazione che l’azienda di Redmond riesce a sostenere grazie alle sue enormi […]
Unfortunately, the release of LibreOffice 26.8.1 has been a bit of a struggle, firstly due to a series of minor issues with the packaging of the Windows version, and then because of a serious malfunction in the server managing the downloads, which forced us to revert to the previous version for a few days.
Today, at last, LibreOffice 26.8.1 is available for download. All links have been checked at least three times to prevent the same problems from recurring. We would like to thank all our most loyal users – those who update LibreOffice immediately after every announcement – for their patience.
And we hope that this completely unexpected malfunction has not put any users off LibreOffice. The download link remains the same: https://www.libreoffice.org/download
I documenti che creiamo, siano essi relazioni, fogli di calcolo o presentazioni, sono fondamentali per comunicare, condividere e archiviare le nostre conoscenze. Tuttavia, il formato in cui questi documenti vengono salvati non viene quasi mai considerato con l’attenzione che merita. È qui che entra in gioco Open Document Format (ODF), il formato nativo dei documenti […]
We are releasing the State of the Project Slide Deck, which is updated quarterly and based on data extracted from the LibreOffice dashboard and the Matomo repository between 1 October 2025 and 30 September 2026.
Over the course of 12 months, 297 developers worked on the source code, making a total of 11,676 new commits (Git). Of these, 2,596 (22%) were provided by 228 volunteer developers (77%), 4,818 (41%) by 11 developers from The Document Foundation (4%), and 4,636 (37%) by 58 developers from seven ecosystem companies (19%).
The slide deck is also a tribute to the top 20 Git and Gerrit committers, the top 20 Bugzilla issue submitters, the top 20 Discourse contributors, and the top 20 Weblate translators. Thank you to all of them and to all the other contributors.
Examining donations and downloads, the trend during the first nine months of 2026 confirms the positive trend that began in early 2025. The number of donations and downloads increased significantly in August and September 2026 thanks to a number of small but important changes to the marketing strategy and donation mechanism. It is important to note that the figures refer to the number of transactions, rather than their value, which is available via the ledgers published on The Document Foundation website.
You are invited to view the slides and download the file to compare it with the previous slide decks published in January, April and July. The next slide deck will be available in January and will cover the 12 months between 1 January 2026 and 31 December 2026.
In January 2026, we started publishing these slide decks to provide a transparent overview of the project’s progress through some of the most significant development, download and donation data collected by the TDF marketing team.
Download the slide deck in EnglishNel corso dei suoi 20 anni di storia, lo standard ODF è stato adottato, o almeno raccomandato, da numerosi organismi sovranazionali e da diversi Paesi in quasi tutti i continenti. Tuttavia, questo non implica necessariamente che lo standard ODF venga usato nel rispetto di queste decisioni, che spesso assumono la forma di leggi, poiché le […]
General Activities LibreOffice 26.2.6 was announced on September 4 Olivier Hallot (TDF) improved help for many Calc functions, alignment and number formats in Calc and the Data Range button in Calc’s Navigator. He also added meta data for cross referencing translated online help pages to improve web search results Alain
Why did LibreOffice 26.8 get over 4 million downloads in September? We answered this question, and more, in our talk at the recent LinuxDays event in Prague:
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.
If you accept this notice, your choice will be saved and the page will refresh.
( Note: this is a translation of an article on the Spanish-language blog)
For Adlair Cerecedo-Méndez, his work with LibreOffice began as a response to a specific need: helping the Mexican government obtain an office suite tailored to public institutions. Over time, that technical work also became an experience in collaborating with the international LibreOffice community and an opportunity to promote free software in the public sector.
Although Adlair had already been using LibreOffice since the OpenOffice days, his professional involvement with the project took shape around 2020, when he was invited to collaborate on the development of a government office suite. The initiative was part of a broader vision: reducing dependence on proprietary solutions, making use of free software, and strengthening the state’s own technological capabilities.
Office GOBMX did not necessarily start out based on LibreOffice. At first, the possibility of creating a suite from scratch was considered, but the technical analysis revealed the scale of the challenge: developing, maintaining, and evolving an application of that kind would require considerable time and resources.
LibreOffice offered a mature, cross-platform, open-source foundation backed by an international community. Adapting it to government needs made more sense than reinventing an entire office suite. That was how the Office GOBMX approach was born: starting with existing technology and adapting it to the needs of public institutions.
The goal included reducing licensing costs, but it also involved moving toward greater technological autonomy. For Adlair, sovereignty does not mean switching tools overnight. It is a gradual process that allows the state to decide which technologies it uses, understand them, modify them, and maintain them with its own expertise.
Implementation brought challenges involving compatibility with documents, macros, formats, and processes that had been built over many years around other tools. It was also necessary to determine what could work as-is and what required adaptation or reimplementation.
But the greatest challenge, Adlair recalls, was resistance to change. Office tools are part of many people’s daily routines, and a migration can disrupt familiar habits and procedures. That is why simply installing software is not enough: it is necessary to analyze processes, test compatibility, migrate documents, train users, and provide guidance and support.
Coexistence with Microsoft Office was also part of the transition. In public administration, documents circulate among government institutions, citizens, businesses, and vendors. Although LibreOffice provides interoperability with widely used formats, some complex documents, templates, and macros require special attention. The strategy, Adlair explains, must be gradual: promote open formats such as ODF without disrupting work or losing the ability to exchange files with the existing ecosystem.
Open-source software made it possible to develop components for specific institutional needs. One example is a document validator created to analyze internal elements in files generated with Microsoft tools and obtain technical evidence about the information they contained. In a government context, Adlair points out, it is important to understand those elements before assuming …
Para Adlair Cerecedo-Méndez, su trabajo con LibreOffice comenzó como una respuesta a una necesidad concreta: ayudar al Gobierno de México a contar con una suite ofimática adaptada a las instituciones públicas. Con el tiempo, ese trabajo técnico se convirtió también en una experiencia de colaboración con la comunidad internacional de
Berlin, 2 October 2026 – The Document Foundation announces LibreOffice 26.8.1, the first minor release in the LibreOffice 26.8 family, available for Windows, macOS and Linux. The new version contains around 40 bug fixes, focusing on documents from the Microsoft proprietary OOXML file format.
Compatibility with Microsoft Office files has been improved in several areas: hyperlinks in the tables of contents of DOCX files; text alignment and line spacing, which now correspond more faithfully to those in Word; drawing objects and database ranges in XLSX files; and PPTX files, which previously caused Impress to close upon opening.
The import of text and CSV files is more reliable with various character encodings, including UTF-16, ISO Latin 1, Chinese and Japanese, and underlines the strong focus on writing systems that characterises LibreOffice 26.8.
The full list of fixes is available at wiki.documentfoundation.org/Releases/26.8.1/RC1.
LibreOffice 26.8.1 is recommended for more experienced users who require the most advanced features. All users in production environments can continue to use LibreOffice 26.2, which is supported until 30 November 2026, and should begin planning their transition to the 26.8 family over the next two months.
Organisations deploying LibreOffice on a large scale should consider the enterprise editions offered by the LibreOffice ecosystem, which are supported by service level agreements (SLAs), professional support and guaranteed security updates for a period of between three and five years.
LibreOffice 26.8.1 is available at www.libreoffice.org/download/. Donations: www.libreoffice.org/donate
Questions and answers for AI-powered search engines
What’s new in LibreOffice 26.8.1?
LibreOffice 26.8.1 is a bug-fix release containing around 40 fixes. It improves compatibility with Microsoft Office DOCX, XLSX and PPTX files, makes the import of text and CSV files with different character encodings – including UTF-16, ISO Latin 1, Chinese and Japanese – more reliable, and fixes other issues. It does not add any new features to LibreOffice 26.8.
Should I upgrade to LibreOffice 26.8.1?
Users running LibreOffice 26.8 should upgrade to version 26.8.1, which fixes bugs without changing any functionality. Users in production environments running LibreOffice 26.2 can remain on that version for a couple more months. LibreOffice 26.2 will reach the end of its lifecycle on 30 November 2026.
When will support for LibreOffice 26.2 end?
Support for LibreOffice 26.2 will end on 30 November 2026. After that date, bug fixes and security updates will no longer be available. Users should upgrade to the LibreOffice 26.8 family before that date.
Este es nuestro resumen de las novedades, los eventos y las actividades del proyecto LibreOffice durante septiembre. Haz clic en los enlaces para obtener más información… Comenzamos septiembre con una respuesta récord al lanzamiento de LibreOffice 26.8: durante su primera semana, la nueva versión superó el millón de descargas, con
Here’s our summary of updates, events and activities in the LibreOffice project in September – click the links to learn more…
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.
Hay algo que suele pasar desapercibido detrás de cada nueva versión de LibreOffice: antes de llegar a millones de escritorios alrededor del mundo, el software atraviesa un enorme proceso de pruebas. Y, aun así, ningún programa de semejante tamaño puede anticipar todas las combinaciones posibles de sistemas, documentos, configuraciones y
The LibreOffice project does extensive testing of every major update before release. But as it’s a large piece of software used in millions of different ways across the whole world, sometimes there are issues with certain setups. So The Document Foundation, the non-profit behind the suite, has expanded its team with a new QA Analyst, Bogdan Buzea. Let’s hear from him:
I’ve worked as an accountant for almost all my life here in Romania. As a hobby, over the last eight years, I have been involved as a volunteer in LibreOffice Quality Assurance. I was involved mainly in LibreOffice Writer, which I used most of the time in my accountant work, and I wanted to see things improve.
Since mid-September 2026, I have taken on the role of Quality Assurance Analyst. I go through bugs reported to Bugzilla, and triage them:
I also work on finding regressions …
por Italo Vignoli El 28 de septiembre de 2010, un grupo de miembros de la comunidad de OpenOffice.org anunció el lanzamiento del proyecto LibreOffice y de la fundación que lo respaldaría: The Document Foundation. El anuncio generó cierta confusión y escepticismo, así como un enorme entusiasmo entre aquellos miembros de
On 28 September 2010, a group of OpenOffice.org community members announced the launch of the LibreOffice project and the foundation that would support it: The Document Foundation. The announcement sparked some confusion and scepticism, as well as enormous enthusiasm amongst those in the community who believe in free and open-source software.
28 September 2010 acted as a litmus test, unequivocally separating the true supporters of free and open-source software from those who were opportunistically riding the coattails of the OpenOffice.org project, or waiting for the right moment to stamp their own proprietary mark on it.
Sixteen years on, LibreOffice has been independent for longer than OpenOffice.org ever was under Sun Microsystems. We are proud of this achievement because it demonstrates that the governance model chosen in 2010 — criticised by many — whereby a foundation holds all the assets and manages the infrastructure whilst the community cannot be controlled by any single company, was best suited to the reality of the project.
Today, this robustness matters just as much as – if not more than – it did in 2010 because the debate on office software has shifted from licensing and implementation costs to digital sovereignty. It is a concept that we have championed for over 20 years, ever since OpenOffice.org began using the standard open ODF (Open Document Format) file format.
At the time, the term ‘digital sovereignty’ was not yet in use, but the issue was already clear: control over the format in which public documents are stored, and how this format evolves, must not lie with a single company, but with the community.
In this sense, ODF is the “sovereign” format par excellence because it does not depend on the authority — and therefore the commercial strategies — of a single company, but on the users — individuals, organisations, and businesses — who use it and determine its evolution through the contributions of experts within the independent OASIS Technical Committee, which comprises companies, foundations, public bodies, and individuals.
As the only “sovereign” format, ODF acts as a litmus test for office suites that claim to champion digital sovereignty yet continue to use the proprietary OOXML format, thereby submitting to Microsoft’s monopoly. They are in good company, given that even the scientific community has renamed our genome for the same reason.
LibreOffice is the only office suite to use ODF as its native format without proclaiming itself a champion of digital sovereignty because, after sixteen years of consistent behaviour, it does not need to chase trends to secure its place in the market. The figures prove it: today, downloads stand at a steady one million per week, and the updates website receives almost fifty million visits per month.
We would simply like all software that proclaims itself a champion of digital sovereignty to demonstrate the same level of consistency as the LibreOffice project. This means not bowing to the Microsoft monopoly in pursuit of a theoretical goal — namely, compatibility with Microsoft’s proprietary format — which ultimately leads them to betray the …
Conociendo a Tamás Tamás Zolnai es un ingeniero de software de Hungría con más de una década de experiencia en el desarrollo de software y una formación que combina informática y psicología. Su vínculo con LibreOffice viene de hace muchos años. A lo largo de ese tiempo, ha contribuido principalmente
I’m a software engineer from Hungary. I’ve been working in software engineering for more than a decade, with a background in both computer science and psychology.
I’ve been a long-time contributor to LibreOffice, mainly working on Writer and Impress, and I’ve also contributed to Collabora Online as part of the Collabora team. Throughout my career, I’ve always placed a strong emphasis on the quality of my work and on building things properly, even when that sometimes meant pushing back against management priorities.
Outside of software development, my current project is setting up my own camper van, intending to eventually explore Europe with it. I’m looking forward to combining some travel with my work on open source projects.
My new role at The Document Foundation is to participate in building LibreOffice Online. We are basically trying to create a Google Drive or Google Docs-like solution on top of LibreOffice as a document editor, and bring LibreOffice into the cloud. Currently, I’m doing some research into existing cloud infrastructures to identify best practices and avoid the same problems that other projects have encountered during the lifetime of their cloud implementations.
More details about the development strategy can be found in this post.
Well, we’re still in the design phase, so there isn’t much room for involvement at this point. At some point, once we have the initial versions LibreOffice Online, feedback would be very much appreciated. We will post updates here on the blog.
LibreOffice es un proyecto de código abierto impulsado por voluntarios y respaldado por una entidad sin fines de lucro, The Document Foundation. La gran mayoría de los ingresos de la fundación proviene del apoyo de la comunidad, y nos complace anunciar que FLOSS/fund ha hecho una contribución muy generosa
avtor: Italo Vignoli (The Document Foundation)
Danes, 19. septembra, je Dan svobode programske opreme, poseben dan, ki ga skupnost prostega programja vsako leto praznuje tretjo soboto v septembru po vsem svetu.
To je dobra priložnost, da si ogledamo LibreOffice iz perspektive, ki se pogosto jemlje za samoumevno: ne gre za to, kaj programska oprema počne, ampak za to, kaj omogoča uporabnikom in česa jim ne vsiljuje.
Prosta programska oprema je opredeljena s štirimi svoboščinami. LibreOffice jih vse zagotavlja, iz njih pa izhajajo številne druge svoboščine, ki so pomembne za vsakogar, ki piše pismo, pripravlja proračun ali predstavlja projekt.
LibreOffice se razširja pod javnim dovoljenjem Mozilla Public Licence 2.0, ki vsakemu uporabniku zagotavlja štiri svoboščine, ki opredeljujejo prosto programsko opremo:
Dokument pripada njegovemu avtorju le, če format, v katerem je shranjen, ne pripada komu drugemu. LibreOffice kot svoj izvorni format uporablja Open Document Format (ODF): standard ISO/IEC, ki je bil razvit v okviru organizacije OASIS v preglednem in v celoti dokumentiranem postopku, ki ga nobeno posamezno podjetje ne more enostransko nadzorovati ali ga spreminjati.
To pomeni, da bo dokument, danes shranjen v formatu ODF, še čez dvajset let berljiv, bodisi s paketom LibreOffice bodisi z drugo programsko opremo, ki podpira ta standard. Za posameznike je to vprašanje praktičnosti. Za javne organe, ki imajo dolžnost hraniti dokumente in komunicirati z državljani, ne da bi jih prisilili v nakup določene programske opreme, pa je to načelno vprašanje.
LibreOffice ne zbira podatkov o svojem delovanju in od vas ne zahteva, da si ustvarite račun. Dokumenti se ustvarjajo, urejajo in shranjujejo na računalniku uporabnika ter tam ostanejo, razen če se uporabnik ne odloči drugače. Ni obvezne povezave z oblačno storitvijo, na oddaljenem strežniku pa se ne ustvari noben uporabniški profil.
LibreOffice ne prikazuje oglasov in uporabnikov ne poziva k sklenitvi naročnine ali prijavi na premijski paket. Vmesnik je zasnovan za podporo delu uporabnikov, ne pa za prodajo dodatnih storitev.
LibreOffice ne vsebuje nobenih funkcij generativne umetne inteligence. Uporabniki, ki jih potrebujejo, jih lahko dodajo prek razširitev in izberejo, katero storitev bodo uporabljali, vključno z modeli, ki se izvajajo lokalno, medtem ko uporabniki, ki jih ne potrebujejo, ne bodo ničesar zamudili, saj ni ničesar, kar bi lahko zamudili.
por Italo Vignoli Hoy, 19 de septiembre, se celebra el Día de la Libertad del Software, una fecha especial que la comunidad del software libre conmemora cada año, el tercer sábado de septiembre, en todo el mundo. Es una buena oportunidad para analizar LibreOffice desde una perspectiva que a menudo
por Italo Vignoli LibreOffice 26.8 incorpora soporte básico para importar y exportar una serie de tipos de gráficos que Microsoft Office incluye en los archivos OOXML: gráficos de caja y bigotes, embudo, Pareto, radial, mapa de árbol y cascada. LibreOffice no puede mostrar ni editar estos gráficos, pero sí los
General Activities LibreOffice 26.8.0 was announced on August 26 Olivier Hallot (TDF) added help pages for Calc’s ARRAYTOTEXT function, the easy conditional formatting feature, saving database queries, the VBA Like operator, added new gutter options to the help page for Page Style dialog, added a mention of autodetection of ISO
If you don't know what is dynamic arrays, then just read this article https://exceljet.net/articles/dynamic-array-formulas-in-excel.
Note, dynamic array's functions like UNIQUE, FILTER, SORT, etc. were already implemented early. But other new general dynamic array features were added to LibreOffice Calc only now into current master that will be 27.2 release in next year.
Let's say big thanks to Collabora's developers for it, because all work was made for Collabora Office and then Xisco Fauli copied all patches to LibreOffice project (The source code license allows it, because it's the same MPL 2.0 on both sides).
You can try the new features using master daily builds for your OS by the link.
Earlier this year we ran a survey about LibreOffice Base. Similar to the questionnaires about LibreOffice Draw (see first and second blog post) and LibreOffice Calc, we asked about use cases, the most important features, the pain points – and what users expect in the future to support development and to gather ideas how the user interface and workflow can be improved. In total, 455 participants completed the questions. Thanks a lot to everyone who took the time!
As usual, the survey is heavily biased. The attendees self-estimate their expertise above the average, run the application more frequently, and show a different distribution in operating system usage compared to regular users.
To start off, we asked what tools they use. We included Spreadsheet Tools to also cover users who do not actually use a database, but think of a spreadsheet as kind of data storage. Participants responding None, obviously not managing any database, got a different follow-up question.
What tools do you use to manage databases?To trigger the idea of the following open questions, we asked about the importance of different features. Unlike the large number of functions in other modules, Base offers queries, reports, forms, tables, etc. which are all essential for the work with databases. Therefore we collected some features that may or may not be relevant for a sub-group or have room for improvements.
How important are these features for you?People understand the question differently, and reply very short or rather verbosely. The answers may point to a professional environment if “payroll information for up to 10000 people” is mentioned, over SME’s processing order management, production count, and shipment status, to obviously private usage. The following attempt to categorize the answers cannot do justice to the variety of all replies:
For example:
“I use it mostly as place to store sensitive customers data. But since I have small quantities of information, I switched to LibreOffice Calc, which files can be also locked with the password.”
“Smaller business applications in the freight forwarding and logistics sectors, such as fleet management, warehouse management, category management, and invoicing.”
“Managing geospatial information with PostgreSQL/PostGIS and creating reports with the information from the attribute table using LibreOffice Base/Writer.”
“Storing data when it gets too big/slow for a CSV file for personal or internal work (engineering) projects.”
The majority asks for improvements to the user interface with less clutter and a more attractive design. The workflow and user experience should become either simplified or more powerful, depending on the expertise and the scenario …
The NotebookBar (NBB) or tabbed interface is an alternative user interface for LibreOffice. In the second part of this series, I explain the way the NotebookBar takes icons and text to create the final output that you see on the screen.
Currently, the NotebookBar is not exactly like the other UI files that in LibreOffice with weld mechanism. In the first part of the series of blog posts on this topic, I discussed the custom widgets in notebookbars and how to edit them using Glade.
The custom widgets rely on C++ code, especially for sizing and other characteristics. For example, Priority Merged Horizontal Box (sfxlo-PriorityMergedHBox) is a “horizontal box hiding children depending on its priorities”. It needs C++ code to implement the priority display of the children. If you search for it in C++ files, you will reach builder.cxx:
$ git grep -l sfxlo-PriorityMergedHBox "*.cxx" vcl/source/window/builder.cxx
The above file is a huge > 100 KB C++ source code that handles NotebookBar custom widgets, but also handles every other VCL widget.
The other parts of the relevant code for the NotebookBar resides in below files. Search for both “Notebookbar” and “notebookbar” in C++ files:
$ git ls-files "*otebook*cxx" sfx2/source/notebookbar/NotebookbarTabControl.cxx sfx2/source/notebookbar/SfxNotebookBar.cxx vcl/qt5/QtInstanceNotebook.cxx vcl/qt6/QtInstanceNotebook.cxx vcl/source/control/NotebookbarPopup.cxx vcl/source/control/notebookbar.cxx vcl/source/window/NotebookBarAddonsMerger.cxx
If you open the NotebookBar UI for LibreOffice Writer or other components like Calc, etc., what you see lacks two important things: icons and text.
Notebookbar widgetsFirst, let’s look into icons. The icon files come from the set of icon themes that are available with LibreOffice. The icon theme of LibreOffice is configurable, therefore you do not see some specific LibreOffice icon in the design. That makes the work of UI designers harder, but lets LibreOffice choose among different icon themes.
You may find more information in the icon-themes/ module README.md file, which describes how to create new icon themes, and how to link the icons to specific icons via .xcu files. For example, in officecfg/registry/data/org/openoffice/Office/UI/CalcCommands.xcu you see:
<node oor:name=".uno:OpenFromCalc" oor:op="replace">
<prop oor:name="Label" oor:type="xs:string">
<value xml:lang="en-US">~Open...</value>
</prop>
<prop oor:name="Properties" oor:type="xs:int">
<value>1</value>
</prop>
</node>
This is defined for the UNO dispatch command, .uno:OpenFromCalc, which opens a file for Calc. The complete list of UNO dispatch commands is available here:
For each command, two icon sizes are created, one small and one big icon. lc_<command name>.png and sc_<command name>.png, if not in SVG format. At first, one should add the icons for a new command to the colibre theme, in order to be usable also with other themes.
Here, the filenames will be lc_openfromcalc.png and sc_openfromcalc.png, which are available …
| 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. | |