2026-06-08 07:05 UTC
Replies (18)
-
@josch@floss.social 2026-06-08 07:32
@libreoffice@fosstodon.org Hello libreoffice team! Thank you for your work! The PNG you uploaded has a transparent background. This means that when shown in interfaces with a dark background, only the white boxes (2006, 2015, 2024) will be visible because the rest is just black lines and letters on black background. In this case, an alt-text would even very much help the sighted people. Thank you! ❤️
-
@jmbmkn@mastodon.scot 2026-06-08 07:39
@libreoffice@fosstodon.org Thanks for the extra info about Euro Office. Is it known why they have chosen to default to OOXML, is there a limitation in ODF that they don't put the work in to implement? I understand that might be something only they can answer, but you seem to have done research on it.
-
@ckd@mas.to 2026-06-08 07:55
@libreoffice@fosstodon.org I'm not sure whether this is a problem of me using dark mode, but the text in the box is light black on a black background and impossible to read...
-
@dianshuo@mstdn.io 2026-06-08 08:12
@libreoffice@fosstodon.org I feel you need stronger advocacy in the Brussels bubble.
-
@phlogiston@mastodon.nz 2026-06-08 09:44
@libreoffice@fosstodon.org I hope/predict that the unfortunate and sucky choice of OOXML default format is just a legacy of having been forked from OmlyOffice. With moves in the EU to mandate ODF as a default, I do have hopes this will be flipped to an ODF default sooner rather than later. And that would support the ecosystem favouring LibreOffice as well.
-
@cairobraga@gts.cairobraga.com 2026-06-08 10:58
@libreoffice@fosstodon.org #Alt4You An image showing a simple horizontal timeline titled "Twenty Years of Open Document Formats", with the subtitle "a quiet infrastructure of digital democracy". It starts in 2006 with the ratification of ISO/IEC 26300; continues to 2008-2012 with the first national adoptions in Germany, the Netherlands, Brazil and Italy; goes on to 2015 when the UK government mandated the format; continues to 2020 with the EU open source strategy; comes closer to 2024 with the Schleswig-H. migration of 30 thousand workstations; and arrives in 2026 at the European digital sovereignty affairs and the Deutschland-Stack. At the bottom, the text reads: "Twenty years of an open standard.".
-
@cairobraga@gts.cairobraga.com 2026-06-08 11:36
@libreoffice@fosstodon.org can you please add #AltText? I wrote one for you in the replies, here: https://gts.cairobraga.com/@cairobraga/statuses/01KTKE3QVMKBKZR7HYPTQ8TEFQ
-
@wojtek@social.vivaldi.net 2026-06-08 14:31
@libreoffice@fosstodon.org using crappy pseudo-open Microslop format by default is a no no and is counterproductive...
-
@kaiserkiwi@corteximplant.com 2026-06-08 16:40
@libreoffice@fosstodon.org You should check on the contrast again.
-
@hobart@uwu.social 2026-06-08 17:19
@libreoffice@fosstodon.org https://www.explainxkcd.com/wiki/index.php/743:_Infrastructures
-
@dunklecat@mastodon.dunklecat.dev 2026-06-10 07:23
@libreoffice@fosstodon.org I thank you for your open letter, and I'm going to take advantage of it to ask you: are you going to abandon Github in the foreseeable future? If I'm not mistaken your official repositories are here: https://github.com/LibreOffice I'm wrong, they're at https://git.libreoffice.org/
-
@cloud42@noc.social 2026-06-08 09:26
@markusr@mastodon.social @jmbmkn@mastodon.scot @libreoffice@fosstodon.org At least for the Collabora-Integration, the default can be configured on an Nextcloud instance-wide basis.
-
@avuko@infosec.exchange 2026-06-08 09:11
@the_wub@mastodon.social @mr_harm@mastodon.social @libreoffice@fosstodon.org OOXML was specifically meant to frustrate and ideally block progress towards a non-Microsoft controlled standard. And even Microsoft doesn’t know how it actually works. None of this is hyperbole. It is all very extensively documented. Open standards are the antidote to vendor lock-in, bar none.
-
@sigjlr@mastodon.uno 2026-06-08 08:44
@mr_harm@mastodon.social @libreoffice@fosstodon.org file format is not a decision regarding performance. Is usually a decision regarding marketing: is the main lock-in feature of any commercial software. OOXML is a open format that MS keep actually closed by un-necessary complexity and backward-incompatible changes.
-
@richh@cupoftea.social 2026-06-08 08:51
@mr_harm@mastodon.social @libreoffice@fosstodon.org It puts you at the whim of MS. If MS change something in OOXML, everyone has to jump up and fix their implementation. Moreover, if MSOffice users send you a file which then doesn’t open properly in EuroOffice/OnlyOffice/LibreOffice then users will complain about “this new thing doesn’t work properly, why can’t we just use MSOffice like we always have?”. For sure, if ODF changes, everyone needs to update. But that’s the result of a public committee decision and there will be a standards document describing the spec - not reverse-engineering whatever Redmond have done unilaterally. If you default to a genuinely open spec like ODF, then in a couple of years when people are used to it, if an OOXML file doesn’t open, their instinct will be the at the sender is at fault, not them. And they’ll ask them to resend it in ODF. In 2026, there’s just no reason to use proprietary formats for things like standard productivity suites.
-
@richh@cupoftea.social 2026-06-08 12:14
@mr_harm@mastodon.social @libreoffice@fosstodon.org Yes, ind orgs can set defaults on their local install. It’s a human factor issue. Imagine you set ODF as default, everyone is happy with it but someone sends an OOXML file from MS Office which doesn’t render right in EO - it’s the sender’s problem. Save in ODF. If OOXML is “standard”, then people blame EO for not opening it right, mgmt get complaints, maybe even recant and go back to MS because “EuroOffice doesn’t work”. ODF *is* the native format for most office suites. Forcing MS users to use ODF (because the rest of us are on LO/EO/OO) makes MS treat ODF compatibility as a first class format. Allowing Redmond to dictate the terms on which other office suites interoperate is a bad idea and will stymie adoption. Obviously there are millions of old docs in MS format. EO needs to open them. Doesn’t mean new docs going forward need to make the issue worse.
-
@cairobraga@gts.cairobraga.com 2026-06-08 11:35
@karlggestd@mastodon.social @libreoffice@fosstodon.org from https://en.wikipedia.org/wiki/StarOffice: "5.2 was released 20 June 2000. Sun offered StarOffice 5.2 as a free download for personal use, and soon went through an exercise similar to Netscape's relicensing of Mozilla, by releasing most of the StarOffice source code under a free/open source license. The resultant free/open source software codebase fork continued development as older discontinued components, with contributions from both Sun and the wider OpenOffice.org community. Sun then took "snapshots" of the OpenOffice.org code base, integrated proprietary and third-party code modules, and marketed the package commercially. " going from that info, StarOffice was not the 1st european FOSS office suite since only a part of the code/some components were open-sourced and the full suite was never released as FOSS at any point. OpenOffice.org was built from those parts, and expanded as fully FOSS to become the actual 1st european FOSS office suite.
-
@cairobraga@gts.cairobraga.com 2026-06-08 11:56
@karlggestd@mastodon.social @libreoffice@fosstodon.org OK. have a nice week! 👋🏼