Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.os.linux.misc
Subject: Re: font fallback issues
Date: Fri, 24 May 2024 05:51:57 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 12
Message-ID: <v2p9tt$26phi$1@dont-email.me>
References: <slrnv4vndp.3ag.candycanearter07@candydeb.host.invalid>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 24 May 2024 07:51:58 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="0cff0ba9dc44f1983d14765f610aa6bd";
	logging-data="2319922"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/tdLcy/jYEbTUiIjOHnNo/"
User-Agent: Pan/0.155 (Kherson; fc5a80b8)
Cancel-Lock: sha1:D7RCmRjdkSNAwlSaZSYBPTOs0Ik=
Bytes: 1514

On Fri, 24 May 2024 00:25:03 -0000 (UTC), candycanearter07 wrote:

> I wanted to set up a fallback bitmap-unicode font
> (https://www.kreativekorp.com/software/fonts/fairfax/) as backup,
> because all the normal text is very blurry, but I couldn't figure it
> out.

I think nowadays we use Google’s “Noto” outline fonts for this purpose, as 
the results look much better than bitmap fonts.

I think the fallback mechanism is internal to the different apps’ text-
rendering engines; they should just make use of this automatically.