Explain about font weights, and how installing only one or two may
let you slightly darken (or lighten) the text.
Comment about static fonts in files which also include variable
fotns - variable fonts are mentioned on the TTF-and-OTF page but
the data fits better in tuning-fontconfig.
Details eventually found (from 2020), with a very ugly set of bug
responses.
Note: Putting the commented link to the bug on a new line adds a
blank line to the rendered file, and there is already a blank line.
Moving the comment to the same line as the text fixes that.
Many older fonts, and even some currently-developed fonts such as
Junicode, lack hints. Before exploring hinting options it makes
sens to check that the font being used does indeed have hints.
Placed in 'Useful Commands' ahead of the Pango example, because
it is a plain fontconfig command.
In talking about hinting, mention dots per inch - some people can
detect colour fringing if the actual DPI is a little different from
96 dpi, and general recommentations for High DPI screens are to
disable hinting because it is not required when the font is increased
in size to have the expected size, i.e. more pixels are used for
the glyph so they can be either off or on rather than shades of grey.
A lot of the information which shows up in google, particularly from
Arch users, is for using the Infinality True Type interpreter. Let
people read the history from FreeType.
Also confirm, from a posting this month, that medium hinting is broken.
As a consequence, simplify 'other non-latin alphabets' to
'other alphabets' rather than 'other non-Latin alphabets'.
Correct the link to my own 'Substitute latin fonts' item, which
remains lowercase, to go directly to it and therefore make a
separate link for the font pages of that site as a whole.
To stop people thinking that every website's choice of font can be
easily overridden (firefox can do that, not sure about other
browsers).
This is about halfway through the commits from my initial private
branch.
Explain what 'latin' means in this context.
Detail all the font types mapped there.
Mention that 49-sansserif is where an unrecognized font is assumed
to be Sans.
I had a setup like this on one of my machines, now that I'm
looking at the detail of fontconfig in a local branch I discovered
that there were certain problems with the example:
1. I'm in an en locale, for pages that do not specify a locale
(or in vim/view, e.g. in mutt) the Japanese fonts were being
preferred.
2. Fontconfig does not consider UMing suitable for zh-sc so it
was hardly ever used - and it does not really belong in local.conf.
3, Really prefer a Japanese font for Sans Serif and monospace, but
no point listing two of them.
3. Comment where WenQuanYi Zen Hei is regarded as adequate and
therefore do not include it in these preferences, since it will
be picked up after them.
neither firefox nor epiphany can download them, and they are not
well maintained, because rarely tested.
This is WIP because the "(HTTP)" part of "Download (HTTP)" will
need to be removed too.
But let's see what users think first...
When the patch can be converted to a not-so-long sed, we prefer the sed
because it tells people "what this command is doing" more explicitly and
also reduces an additional download. And for patch or sed we need a
<para> describing "what it fixes".
It's also a bad idea to fold the patch/sed command just before "meson"
in the same <screen> because it'd be too easy to overread it.
We recommend using the /usr prefix for xorg, but the instructins
for putting it in /opt/xorg do work. For jhalfs, having optional
instructions is confusing, so we mark the /opt/xorg "nodump" so
they will be ignored when automating BLFS.
If we had the Xorg Drivers section still with xf86-video-nouveau there,
this probably would've gone over there originally, but this place fits
well.
The original plan was to put this into LFS, but I decided against it
since it works fine until you start using programs such as Epiphany or
KDE Plasma.
1. Remove redundant paragraph for Cantarell, left over from when it
was at gnome (latest gnome versions do not ship the fonts, only
the source - prepared TTF fonts are at Google fonts).
2. Reword the old KDE comment in Noto fonts, replace by mentioning
that Noto fonts are preferred for everything in KDE Plasma and
applications, except for monospace - and add link to Hack for that.
3. Comment Oxygen fonts.
I'm pretty sure most desktop apps can use variable fonts today (even
Xterm renders variable fonts fine). But there is indeed something not
working, notably xelatex.
