From da9b2d12e77263c6f280973551715a8b8a6513f6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20Ekl=C3=B6f?= Date: Thu, 29 Aug 2019 23:00:49 +0200 Subject: [PATCH] README: re-write font section --- README.md | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index 19998028..27ab6f5b 100644 --- a/README.md +++ b/README.md @@ -47,17 +47,18 @@ In addition to the dev variant of the packages above, you need: ## Fonts -**foot** supports all fonts that can be loaded by freetype, including -**bitmap** fonts and **color emoji** fonts. +**foot** supports all fonts that can be loaded by _freetype_, +including **bitmap** fonts and **color emoji** fonts. -Foot uses its own font fallback mechanism, rather than relying on -fontconfig's fallback. This is because fontconfig is quite bad at -selecting fallback fonts suitable for a terminal (i.e. monospaced -fonts). +Foot uses _fontconfig_ to locate and configure the font(s) to +use. Since fontconfig's fallback mechanism is imperfect, especially +for monospace fonts (it doesn't prefer monospace fonts even though the +requested font is one), foot allows you, the user, to configure the +fallback fonts to use. -Instead, foot allows you to specify a font fallback list, where _each_ -font can be configured independently (for example, you can configure -the size for each font individually). +This also means you can configure _each_ fallback font individually; +you want _that_ fallback font to use _this_ size, and you want that +_other_ fallback font to be _italic_? No problem! If a glyph cannot be found in _any_ of the user configured fallback fonts, _then_ fontconfig's list is used.