Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index

I've attempted to upload my shell script using the More button; it is very
heavily commented (as much for my own benefit as anything). As a quick trial
you can make it executable and then type, for instance:

FindFont thai greek
FindFont hindi persian hebrew

The first will list all the fonts that contain characters for both Thai and
Greek, and list enough information to see which of those fonts correctly
report the needed support. That helps when choosing a font that Writer
(hopefully) won't mysteriously replace. Even with the ability to set a CTL
language and font, it will be ignored and replaced if the font isn't
reporting what it has correctly. With trying to intermingle more than one
language/script in a document, CTL hurts far more than it helps.

The second command - giving three arguments - probably won't list anything
unless you're have some really beefy fonts, although both FreeFontSerif and
its bold counterpart support all three. FindFont.FindFont

The bad news is that the list of languages/scripts is not comprehensive
(just ones I've happened to look into); the good news is that they're
defined in a "case" statement, so adding some others should be relatively


View this message in context:
Sent from the Users mailing list archive at

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, 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 (MPLv2). "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.