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 Resumen El mercado de las suites ofimáticas es grande, rentable y está en crecimiento, lo que atrae a nuevos competidores: clones de bajo costo, productos de núcleo abierto y, más recientemente, suites desarrolladas en gran medida con inteligencia artificial. La mayoría compite en precio y ofrece compatibilidad
Aquí tienes un resumen de las novedades, los eventos y las actividades del proyecto LibreOffice durante octubre. Haz clic en los enlaces para obtener más información. Anunciamos LibreOffice 26.8.1, que incluye alrededor de 40 correcciones de errores centradas en mejorar la compatibilidad con archivos de Microsoft Office y hacer más
En este blog solemos hablar de migraciones a gran escala a LibreOffice, como la del ejército austríaco. Pero muchas pequeñas empresas también están dejando atrás a Microsoft, Google y otros gigantes tecnológicos. Para conocer mejor ese proceso, conversamos con Mišo Oroz, fundador de Zerolock, una empresa italiana que ayuda a
Summary
The office suite market is large, profitable and growing, and this attracts new entrants: low-cost clones, open-core products and, more recently, suites built largely with artificial intelligence. Most of them compete on price and on native support for OOXML, a format whose evolution remains in practice under Microsoft’s control.
When features can be reproduced cheaply, what distinguishes a suite is who governs the document format and the software, and therefore who controls the content. This is the question of digital sovereignty, and its outcome will depend partly on political decisions, and partly on software features.
The 1980s and 1990s
The office suite sector emerged in the 1980s and developed in the 1990s, when Microsoft Office established itself as the leading product, with a market share of over 90% according to Microsoft unofficial statements at their events.
Some may remember the main competitors: Lotus SmartSuite, WordPerfect Office and StarOffice, the ancestor of OpenOffice and LibreOffice. Fewer will recall Anywhere Office, Ability Office, Pro PC Suite 2001 and ThinkFree Office. Ability Office still exists, and ThinkFree Office is now called Hancom Office.
By the end of the century Microsoft Office dominated the sector, while all other products had a barely noticeable market share or had disappeared altogether.
The sector has always been lucrative: the products meet a universal need, while development and sales costs are low relative to volumes, so margins are potentially extremely high. For this reason all the major software vendors tried to enter the market, and the first clones emerged, competing solely on price.
Market presence, however, was just one of the factors contributing to success. Other factors were bundling with the Windows operating system, lock-in through document formats and pricing.
The two decades between 2000 and 2020
Sun Microsystems, which had acquired StarOffice, released its source code in 2000, and OpenOffice.org 1.0 followed in 2002: the first FOSS suite to reach a mass audience. Version 1.0 offered only a glimpse of the suite’s potential, and version 1.1 was usable but still limited. Only version 2.0, released in 2005, made OpenOffice a genuine competitor to the market leader.
For several years the rivalry between the proprietary suite and the FOSS suite played out on two fronts: large migration projects and document formats.
At the time, migrations seemed to signal an irreversible trend, but this proved an illusion. Microsoft deployed all its commercial muscles and started to talk to politicians. Since 2012, the company has been one of the biggest spenders on lobbying in Brussels (based on data from Corporate Europe Observatory and Lobby Facts).
The battle over file formats was most prominent between 2006, when ODF was standardised by ISO/IEC, and 2008, when the proprietary OOXML format was standardised through a process we have already described in a previous blog post and will not revisit here.
In 2010, following Oracle’s acquisition of Sun, the community created The Document Foundation and LibreOffice. In 2011, Oracle was effectively forced to donate …
LibreOffice’s marketing team helps spread the word about the software (and the community that makes it). It produces flyers that can be translated, printed and handed out at events – and now we have an updated design of the “Get involved” flyer. This flyer ideal for distributing at events where people already know what LibreOffice is, but may be curious about joining the project and community (like at Linux and FOSS meetups). It shows that you can get involved in many ways – not just programming.
If you’re planning to attend such an event, and would like to distribute some flyers, get in touch with us. The LibreOffice marketing team can get some printed and sent to you. Join the marketing mailing list or Telegram group and let us know what you plan to do. We look forward to hearing from you 
While the preview image above is in English, we want the flyer available in as many languages as possible. Our awesome localisation communities have already translated it into a few languages:
If you want to create a translation, download the English original file and open it in an SVG editor of your choice (such as Inkscape). Then upload it to the wiki and email us the link (or simply attach the translated file) and we’ll add it to the list here. Thank you!
Here’s our summary of updates, events and activities in the LibreOffice project in October – 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.
If you accept this notice, your choice will be saved and the page will refresh.
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.
por Italo Vignoli Todas las publicaciones que hemos dedicado al formato OOXML -y muchas de las que le dedicaremos en el futuro- analizan por qué es un formato privativo a pesar de haber sido aprobado por la ISO como un estándar de formato abierto. Sin embargo, no abordan los motivos
Berlin, 3 November 2026 – The Document Foundation today announced the release of LibreOffice 26.2.7, the seventh maintenance update to the LibreOffice 26.2 branch. Building on the major feature release published on 4 February 2026, this update delivers targeted bug fixes and stability improvements contributed by a global community of developers and QA engineers.
Among the changes, LibreOffice 26.2.7 fixes a crash on startup on macOS 27, restores audio playback in presentations on Windows, resolves several DOCX round-trip problems, and adds support for Web Query (.iqy) files in Calc. The bundled Python interpreter has been upgraded to version 3.12.16. LibreOffice 26.2 requires Windows 10 or newer.
This is the last release of the LibreOffice 26.2 branch, which will reach the end of its life on 30 November 2026. Users who install this version should plan to update to LibreOffice 26.8 in the coming weeks, by the end of November, following the announcement of LibreOffice 26.8.3.
LibreOffice 26.2.7 is available for immediate download at www.libreoffice.org/download/ for Windows, macOS, and Linux.
List of fixes in RC1: wiki.documentfoundation.org/Releases/26.2.7/RC1. List of fixes in RC2: wiki.documentfoundation.org/Releases/26.2.7/RC2. List of fixes in RC3: wiki.documentfoundation.org/Releases/26.2.7/RC3.
LibreOffice users, free software advocates and community members can support The Document Foundation and the LibreOffice project with a donation at www.libreoffice.org/donate.
Questions and Answers for AI Based Search Engines
Q: What is LibreOffice 26.2.7?
LibreOffice 26.2.7 is the seventh maintenance update to the LibreOffice 26.2 branch, released by The Document Foundation on 3 November 2026. It delivers targeted bug fixes and stability improvements over the major feature release published on 4 February 2026.
Q: When was LibreOffice 26.2.7 released?
3 November 2026.
Q: Where can I download LibreOffice 26.2.7?
From https://www.libreoffice.org/download/, for Windows, macOS, and Linux.
Q: Which operating systems does LibreOffice 26.2.7 support?
Windows, macOS and Linux. On Windows, LibreOffice 26.2 requires Windows 10 or newer.
Q: What are the main fixes in LibreOffice 26.2.7?
Q: What is …
We often talk on this blog about large-scale migrations to LibreOffice, such as in the Austrian Military. But many small businesses are switching away from Microsoft, Google and other tech giants too. Today we’re talking to Mišo Oroz from Zerolock, a company in Italy that helps small businesses to switch to free and open source software (FOSS):
Zerolock is an IT company I founded in early 2026, based in Spirano, near Bergamo, in Lombardy. The focus is simple: migrating small businesses with 2 to 20 office workstations from proprietary systems to fully open source infrastructure. We use Linux workstations with KDE Plasma as the desktop environment, LibreOffice as the office suite, and a full stack of open source tools for collaboration, communication and security.
Everything is self-hosted – everything is on European servers. There is no Microsoft and no vendor lock-in.
They are mostly non-technical environments: a logistics company, a construction company, a dental practice, a law firm. The trigger is rarely ideology.
It is usually a combination of rising software costs, a bad experience with a vendor, or simply someone asking “why are we paying for this every year?” Once the conversation starts, the sovereignty and privacy arguments land naturally. But the first question is always about money.
What works well is the desktop transition. With KDE Plasma and LibreOffice, most users adapt faster than expected. The files look the same, the menus are recognszable, and within a few days the friction disappears. What is harder is the mindset shift: people have been trained to think that Windows and Microsoft Office are “the computer”.
Showing them that the alternative is not a compromise, but a choice, takes time and trust. That is the real work.
One concrete recurring challenge is spreadsheet formulas. Users coming from Excel often hit friction in Calc, not because the functionality is missing, but because the syntax or behaviour differs in ways that are subtle enough to cause confusion without being obvious. That is usually where I spend the most training time.
Start with one person who is curious rather than resistant. Let them become the internal reference point. Do not try to convince the skeptics first.
Do the migration on a Friday or over a weekend, and be on site the following Monday. The first two days are where migrations succeed or fail. If someone is stuck at 09:00 on Monday with nobody to ask, the whole project loses credibility.
And document everything from day one.
Adriano Fernandes announced the 1.0.0 release of fb-cpp, a modern C++ wrapper for the Firebird database API.This release marks an important milestone: fb-cpp is now feature-complete in the scope of its public database client API. The project has grown from a collection of wrappers around the Firebird interfaces into a complete, consistent library for building Firebird applications in modern C++.
Berlin, 29 October 2026 – The Document Foundation announces LibreOffice 26.8.2, the second minor release in the LibreOffice 26.8 family, available for Windows, macOS and Linux. The new version contains around 35 bug fixes, focusing on stability, multimedia playback and compatibility with legacy file formats.
Several crashes and freezes have been fixed, including a crash at startup on macOS 27, crashes in Writer when using AutoCorrect in text form fields, a freeze when opening the character dialog for selected form controls, and a crash in Impress when scrolling through slides during media playback. Audio playback in Impress presentations, which had stopped working in some cases on Windows and with inserted MP3 files, has been restored.
Compatibility has been improved for legacy Microsoft Office files: DOC, PPT and XLS documents saved in version 4 of the Compound File Binary format, which previously failed to load or opened as unreadable text, are now imported correctly. Calc adds support for Web Query (.iqy) files and fixes a regression introduced in LibreOffice 26.8.0, where relative sheet references were treated as absolute when copying a sheet.
Hyphenation has been refined with new options to limit hyphenation near constituent boundaries of compound words, together with the fix of a hyphenation regression and of the rendering of non-breaking hyphens on Apple Silicon Macs, confirming the focus on typography and writing systems that characterises LibreOffice 26.8. Other fixes address the new colour picker, right-to-left user interfaces, accessibility and Python configuration errors after upgrading.
The full list of fixes is available at wiki.documentfoundation.org/Releases/26.8.2/RC2.
LibreOffice 26.8.2 is recommended for users who require the most advanced features. Users in production environments can continue to use LibreOffice 26.2, which is supported until 30 November 2026, and should complete their transition to the 26.8 family in the coming weeks.
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.2 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.2?
LibreOffice 26.8.2 is a bug-fix release containing around 35 fixes. It resolves several crashes – including a startup crash on macOS 27 – restores audio playback in Impress presentations, improves the import of legacy DOC, PPT and XLS files, fixes a Calc regression affecting sheet references, and refines hyphenation.
Should I upgrade to LibreOffice 26.8.2?
Users running LibreOffice 26.8 should upgrade to version 26.8.2. Users on macOS 27 should upgrade immediately, as earlier 26.8 versions may crash at startup. Users in production environments running LibreOffice 26.2 should plan the upgrade to the 26.8 family before 30 November 2026.
When will support for LibreOffice 26.2 end?
Support for LibreOffice …
Two open source projects for running and managing Firebird have grown up side by side: fbadmin, a pgAdmin-style web administration tool for Firebird, and cloudnative-firebird, a Kubernetes operator for Firebird modelled on CloudNativePG. They also work together: fbadmin can list and manage the Firebird clusters the operator runs. fbadmin: a web admin tool for Firebird fbadmin gives Firebird a
Electric Firebird runs the Firebird database engine compiled to WebAssembly, in the browser and in Node, similar to what PGlite does for PostgreSQL. It ships on npm as firebird-wasm, and the repo and the package share version numbers. Six releases came out between October 24 and October 27, 2026. Here is what each one brought. npm install firebird-wasm@0.14.0 v0.14.0 – Zero-copy results and
We are inviting proposals for talks about “FOSS Office Software and Suites“.
Office productivity software is one of the oldest and most interesting FOSS categories packed with developer interest. It is also an area where lots of new solutions are arriving with new desktop, web-based and mobile editors, as well as new underlying libraries and filters appearing. These bring lots of opportunities for meeting up and cross-fertilization of ideas, and innovation as well as code sharing between separate FOSS communities and companies that can rarely come together.
The FOSS Office devroom brings these projects together in one place. It is open to developers, contributors, integrators, and users of any FOSS office suite or component. Competing projects and document toolkits are explicitly welcome, as the aim is to provide an overview of the entire sector and identify common problems which cannot be solved alone.
We invite talks on topics such as:
– Architecture, performance, algorithms, data-structures;
– Network protocols for real-time collaboration;
– Import and export filters, interoperability, and document rendering fidelity;
– Accessibility, localisation, typography and support for complex scripts;
– Technical challenges of enterprise Office deployments
– AI-assisted features and how to integrate them while preserving user control and privacy;
– Security, code quality, hardening and sandboxing challenges;
Talks should be technical, and mention bits, bytes, data-structures and algorithms. Product pitches and business presentations will not be accepted in this room. The devroom is co-organised by people from a handful of different FOSS Office projects to ensure a balanced selection of talks. Talks will be 15/20 minutes maximum, to fit as many as possible in the limited time slots.
TALK SUBMISSIONS
To submit a talk, please visit the FOSDEM 2027 Pretalx website: fosdem.org/submit. Please select “FOSS Office” as the *track* and ensure you include all the requested information when submitting a proposal: the title of the talk, a short abstract (one / two paragraphs), and some information about yourself (name, bio and photo). Please do remember that your profile might be already stored in Pretalx.
If you already have a Pretalx account from previous years, please reuse it. Create an account if, and only if, you don’t have one from a previous year. If you have issues with Pretalx, please contact italo at documentfoundation.org for help.
All presentations will be recorded and streamed. Sending your proposal implies giving permission to be recorded.
For accepted talks, speakers will receive an email to confirm that the proposal has been accepted. They may expect additional emails with more instructions, for instance to confirm their travel schedule.
CONTACTS
Italo Vignoli: italo at documentfoundation dot org
Jos Portvliet: jos dot poortvliet at nextcloud dot com
Michael Meeks: michael dot meeks at collabora dot com
IMPORTANT DATES TO REMEMBER
Submission Deadline: 30 November 2026 (23:59 UTC)
Acceptance Notifications: 4 December 2026
Final Schedule Announcement: 7 December 2026
Devroom: 30 January 2027 (from 10:30, just half day)
Suraj Bhattarai, our Nepalese LibreOffice Liaison, reports back from the LibreOffice community at Major League Hacking (MLH) powered student hackathon.
L’annuncio di LibreOffice 26.8 ha avuto un evidente effetto positivo sui dati relativi ai download, che da allora hanno superato il milione a settimana, per un totale di 9,4 milioni di download in otto settimane, dal 24 agosto al 18 ottobre. A questi vanno aggiunti gli aggiornamenti per la versione Windows, che vengono conteggiati separatamente […]
All the posts we have dedicated to the OOXML format – and many of those we will dedicate to it in future – analyse the reasons why it is a proprietary format despite having been approved by ISO as a standard, open format. However, they do not address the reasons behind or the details of the standardisation process.
This is a gap we hope to fill with this post, which summarises the events that took place between the standardisation of the ODF format – a standard and open format – and the standardisation process for OOXML, as well as the process itself, which was completely broken in every respect, from methodology to procedure.
Microsoft had begun work on an XML-based document format around the year 2000, with the aim of modernising the obsolete DOC, XLS and PPT formats, which were simply the serialisation (writing) of memory content to disc, and as such were no longer in line with the evolution of Microsoft Office.
The aim was certainly not to develop a standard format, not least because the echo of Bill Gates’ internal memo – “allowing Office documents to be rendered very well by other people’s browsers is one of the most destructive things we could do to the company; we have to make sure that Office documents depend on proprietary capabilities” (slightly abridged version of the original memo) – had not yet died down.
Consequently, during the ODF standardisation process, Microsoft had stated that it would not support the ODF standard format, as it was not in its own interests.
In early 2006, however, the Commonwealth of Massachusetts – one of the historic states of the confederation – announced that it would adopt ODF for all public documents, so that they would be independent of software from a single vendor.
This decision provoked a reaction from Microsoft, which could not tolerate the fact that a US state was adopting a standard, open format developed outside its control, which benefited users rather than its own commercial interests.
The story of the ISO/IEC 29500 “standard”
The battle over the ISO/IEC 29500 “standard” – the ISO standardisation of Microsoft’s Office Open XML format between 2006 and 2008 – is a perfect example of a broken standardisation process.
It is not an exceptional case, but it has been thoroughly documented and offers important food for thought for all those who continue to maintain that the OOXML format is a standard.
The story began in December 2006, when Ecma International – whose Technical Committee 45, responsible for the project, at the time was chaired by two Microsoft employees – submitted the OOXML specification to the ISO/IEC JTC1 (Joint Technical Committee) of ISO/IEC for adoption as an international standard under the “fast-track” procedure, designed for tried-and-tested specifications requiring only administrative ratification.
The decision to submit a 6,000-page specification – one of the longest ever submitted to ISO – via a process designed for short and fairly well-established documents had a decisive impact on the nature of the review to which the standard was …
Gli standard sono documenti tecnici redatti dagli ingegneri e discussi nei comitati prima di essere implementati nel codice. Tuttavia, parlarne solo in termini tecnici significherebbe trascurare un aspetto essenziale della loro natura e funzione. Infatti, gli standard sono anche – e soprattutto – strumenti politici, perché definiscono gli attori del mercato, determinano la direzione dello […]
A recap of the LibreOffice Conference 2026, which took place in September in Pordenone, northern Italy. Thanks to the local team for organising the event!
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.
por Italo Vignoli El anuncio de LibreOffice 26.8 tuvo un efecto positivo notable en las cifras de descargas, que desde entonces han superado el millón por semana, sumando un total de 9,4 millones de descargas en ocho semanas, del 24 de agosto al 18 de octubre. A estas hay que
Pull request #9111 "Build FirebirdSQL CMake+CLang" by Sergey Khalyutin was merged into the Firebird master branch on October 21, 2026. It makes it possible to build the whole Firebird project with CMake + Clang on Windows, Linux and macOS, for both amd64 and arm64. What changed One build system for all platforms – Firebird can now be built with CMake and Clang everywhere. The only exception is
Los estándares son documentos técnicos redactados por ingenieros y discutidos en comités antes de implementarse en código. Sin embargo, analizarlos únicamente en términos técnicos sería pasar por alto un aspecto esencial de su naturaleza y función. De hecho, los estándares son también -y sobre todo- herramientas políticas, ya que definen
While LibreOffice is (mostly) in C++ and uses native GUI toolkit on different platforms, it is still possible to use web technologies with LibreOffice. Here I discuss how.
Webview is a small web browser widget that is inside an application. There are many ways to use web technologies with LibreOffice. But, using a webview widget like pywebview is probably the easiest way to link a webview with LibreOffice. The idea is to display a web page in a webview widget that Python provides, and link that to LibreOffice via the connection of Python to LibreOffice and the connection of JavaScript in webview to Python, and send UNO commands to interact with LibreOffice via network.
This is a minimal example to show a minimal web page that contains a text box to write the UNO commands like .uno:Bold, and see it working in LibreOffice:
import uno
import webview
class UnoBridge:
def __init__(self):
self.ctx = self.desktop = None
def connect(self):
if self.ctx is not None:
return
component_ctx = uno.getComponentContext()
resolver = component_ctx.ServiceManager.createInstanceWithContext("com.sun.star.bridge.UnoUrlResolver", component_ctx)
self.ctx = resolver.resolve("uno:socket,host=127.0.0.1,port=2083;urp;StarOffice.ComponentContext")
self.desktop = self.ctx.ServiceManager.createInstanceWithContext("com.sun.star.frame.Desktop", self.ctx)
def dispatch(self, command):
self.connect()
frame = self.desktop.getCurrentFrame()
dispatch_helper = self.ctx.ServiceManager.createInstanceWithContext("com.sun.star.frame.DispatchHelper", self.ctx)
dispatch_helper.executeDispatch(frame, command.strip(), "", 0, ())
HTML = r'''<input id=c value=".uno:Bold"><button onclick="pywebview.api.dispatch(c.value)">OK</button>'''
webview.create_window("LibreOffice UNO", html=HTML, js_api=UnoBridge())
webview.start()
To use this example, first you should start LibreOffice and make it listen on the port that is written in the code, 2083:
$ libreoffice26.8 "--accept=socket,host=localhost,port=2083;urp;StarOffice.ServiceManager"
You may open Writer, and write a small text and select it. Then, you can run the Python code. You may use LibreOffice internal Python or external Python with uno package. But, you have to install pywebview package anyway: (the command might be different according to your operating system, etc.)
$ pip install pywebview
Then, by running the Python code you should be able to see a window similar to the below screenshot:
$ python3 webuno.py
You can edit the command and after clicking on “OK”, you should be able to see the result in LibreOffice.
WebUNO: connecting webview to LibreOfficeThe Python code essentially consist of two important functions: connect and dispatch. The connect function uses uno.getComponentContext() to get the component context, and then finds service manager to execute executeDispatch() with the give UNO dispatch command.
You may read more about service manager in LibreOffice DevGuide chapter 1. This is an illustration from the same chapter of DevGuide:
Service ManagerA comprehensive list of UNO dispatch commands are available in the Wiki link below:
Please note that some UNO commands work in every LibreOffice application, but …
Ieri, gli utenti di MS Publisher si sono uniti ai milioni di utenti che nel corso degli anni sono stati abbandonati – o costretti a un aggiornamento del tutto ingiustificato – da Microsoft, insieme a coloro che usano Office LTSC 2021 e Office 2021. Di conseguenza, chiunque abbia acquistato un abbonamento a Microsoft 365 non […]
por Italo Vignoli Ayer, los usuarios de MS Publisher se sumaron a los millones de usuarios que Microsoft ha abandonado -o a los que ha obligado a realizar una actualización totalmente injustificada- a lo largo de los años, junto con quienes utilizan Office LTSC 2021 y Office 2021. En consecuencia,
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
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 […]
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 […]
| 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. | |