Quote:
Originally Posted by Quoth
There is always something new to learn!
Actually many of the fonts I have the Features button in Styles simply lists the font name, but I see on junicode it does show loads.
|
Yeah, OpenType features also depend on high-quality fonts.
And it's also a difference between professionally designed/purchased fonts (like from InDesign), and those you get from certain free websites. The fonts may have similar names, but who knows what functionality was potentially distorted/stripped.
Anyway, I don't know much about fonts themselves. (Hitch/others know a hell of a lot more about the font minutiae.)
Personally, I never embed and really only stick to a handful. And since I usually need accents, rare characters (polytonic Greek), and most importantly: Maths—this really cuts down on my selection.
Quote:
Originally Posted by Jellby
For the record, my version (6.0.7.3) does not have a "Features" button, but it supports manual method.
|
Yeah, I only noticed it as I was writing instructions for Quoth.
Turns out it was added in 6.2:
https://wiki.documentfoundation.org/ReleaseNotes/6.2
Quote:
GUI > Dialogs
Added Font Features dialog to access font features, which is available via Feature button in the Character dialog, or the Format cell dialog of Calc (Tomaž Vajngerl) tdf#58941
|
And definitely update to 7.1. They've been adding a ton of enhancements lately (
Style Inspector +
fantastic TOC navigation).
The upcoming 7.2 is building up to be a great one too. Tons of performance gains + the long-awaited
"Command Popup" (aka: search through menus).
Quote:
Originally Posted by Quoth
If you open and edit a docx in Writer, it messes up a bit, so I only edit/save in odt and save as an extra copy as docx.
|
Yeah, if you're working in LibreOffice, it's always best to work from ODT as your source, then export to DOCX as a last step if needed.
ODT supports all the latest functionality (like 7.2's upcoming support for "page gutters").
Quote:
Originally Posted by Quoth
I do find that if you Save As Docx, and import to Calibre the Style to CSS class mapping is good on conversion to epub2. Oddly direct odt import doesn't work so well. [...]
|
Yep. Calibre's ODT conversion isn't the greatest, but a simple:
1. LibreOffice: ODT -> Save As DOCX.
2. Calibre: DOCX -> Whatever format conversion.
works well.
Note: Calibre DOCX import carries over your Styles too, whereas the ODT import mangles them.
I believe Kovid's explanation over the years is that the ODT SDK/backend tools aren't the greatest... so he doesn't want to spend all that time+effort fixing it when the "DOCX middleman" currently works so well.
Quote:
Originally Posted by Quoth
I recently upgraded from 64 bit Linux Mint 18.3 to 20.1, via 19.0, 19.3 and 20.0, (in one day) unlike historic Windows upgrades rather than re-installs, that worked.
[...]
LO upgraded to 6.4.7.2 by the end of the OS upgrade procedure.
|
LibreOffice 7.0 and 7.1 are currently the latest versions.
What you may want to do is install the latest LibreOffice using their official ppa.
If you run these 3 commands:
Code:
sudo add-apt-repository ppa:libreoffice/ppa
sudo apt update
sudo apt upgrade
that'll keep you nice and up to date (v7.1.3 as of today).
(For easier instructions, see
libre-software.net: "How to install LibreOffice 7.1 on Linux Mint, Ubuntu, MX Linux, Debian...". For more technical (and older versions), see
Launchpad.net: "LibreOffice Fresh".)