Libre Office ReleaseNotes 7.6
wiki.documentfoundation.org
wiki.documentfoundation.org
I really wish they'd fix their Options screen. It's 2023 and I still can't search for the options I want to change. Instead, they're arranged in an inscrutable order, and often have confusing names. Every time I use Libre Office on a new computer, I have go menu diving to turn off the god awful autocomplete. And as someone who writes in multiple languages, changing languages in a document is a huge pain (the language "For All Text"-option never seems to work).
For my part, though, I'm typically authoring print documents in LyX, since I don't have to exchange documents routinely. If I do have to share Word-compatible documents, I'll sometimes use LO Writer or else convert from a text format to .docx using pandoc.
GIF demo: https://www.omgubuntu.co.uk/2021/08/libreoffice-7-2-release-...
Documentation: https://help.libreoffice.org/latest/en-US/text/shared/option...
Closest I've seen is how it works on macOS.
/s
[0] Opale (Free Software) https://download.scenari.software/Opale@4.0.5/
[1] https://bugs.documentfoundation.org/show_bug.cgi?id=43671
All in all this is probably due to my stubbornness and all problems would be solved by reading a simple tutorial, am I right?
- highlighting for used Paragraph and Character styles - https://wiki.documentfoundation.org/File:Styles_highlighter_...
I'm using these alot, very welcome
I'll also take this opportunity to remind folks they offer torrent downloads so you can take some of the download pressure off their infra if you already have a torrent client installed
I write a line, something else has spacing issues. There is title on each section that gets around.
Markdown gave me the same text and I did not have to worry about output.
It's the most unreliable, poorly documented, full of footguns "tool" that I've ever had the misfortune of using.
Seems like everyone who made a commit highlighted by a screenshot made their own, instead of whoever wrote the patch notes made the screenshots on one single system
If the answer is platform X, you put off the users of platform Y and Z.
For different reasons in each case! Really: try substituting Linux, Mac, Windows for any of X, Y or Z and then work it through.
If you can't make the document for each system, I think it's probably better to document it as this more messy reality.
I maintain documentation for a niche cross-platform product. I ended up going with the 3x solution.
It looks like a high-contrast UI theme for people with vision impairment. In this context, what's wrong with it?