Big new update to #LibreOffice, the free and private office suite.

[proteus@troet.cafe]

@libreoffice

Cool,
but it's all too big for me.
I'll stick with my version 9.x on my notebook.
That's perfectly adequate for presentations...

[libreoffice@fosstodon.org]

@Proteus We never made a LibreOffice version 9.x, but of course, use what works for you! 😊 Just bear in mind that older versions are unsupported and missing security fixes...

[proteus@troet.cafe]

@libreoffice

That's right, it's even worse than version 9.
It's 7.6. 😂
But I mainly use it offline.

[lahdoja@mastodon.social]

@libreoffice Are you going to add a spellchecker soon? Is there one already?

[libreoffice@fosstodon.org]

@Lahdoja Yes, LibreOffice has had a spellchecker for 15 years 😉

[ramkay@mastodon.social]

@libreoffice

This is thrilling, I am looking forward to seeing what the markdown feature brings

I use markdown everyday from writing to note taking, to minutes - so knowing it will now be readily usable in LibreOffice is big

[ramkay@mastodon.social]

@Proteus @libreoffice wow

[troed@swecyb.com]

@libreoffice Oh that Markdown support needs to be checked out

[sassinake@mastodon.social]

@libreoffice

Linux Mint here:

am I better to install the 'system' version, of the 'Flatpack' one?

[cos@fosstodon.org]

@RGBes @libreoffice why? If I open a markdown file, I would like to make sure I don't use features it can't represent. Of course saving the file in ODT should lift the restrictions.

[rzeta0@mathstodon.xyz]

@libreoffice

do you happen to know why the "check update" says there's no update?

[libreoffice@fosstodon.org]

@rzeta0 It's our new stable branch (in that it won't change, with random new features in 26.2.1, 26.2.2 etc.) It will only receive bug and security fixes. The update checker will recommend it for all users after the first or second point release, but you can always get it directly from the website. Thanks!

[mrmanor@social.data.coop]

@altim
+1 looking forward to try it out!
@libreoffice

[rgbes@mastodon.social]

@cos @libreoffice When loading a non-native file format, LibO translate it into its own internal representation, you never really work on the non-native format, you always import/export it, which means that after a few rounds you can get a messy file. On any program, it's always better to work with the native format. Also, using Writer to write a markup file is like using a sledgehammer to crack a nut 😉 Better use a lean, quick markup editor and only at the end import it for the final touches.