Typos, rewordings, put the conf file edits in <screen> blocks to
stand out, add details re GNOME Tweaks and Thunderbird.
I think I made a slight change to one of the wordings, but I now
forget which.
Outstanding item: 'fc-match -a Type | less' wording made me unsure
of exactly which variants of Sans Sasn-serif would be accepted.
Trying to test this (I have far too many fonts on current system)
appeared to act as if hte Type was being ignored. Need to think
about this.
We use <application> in the markup for all package names. Do that
consistently for rendered text on these pages, except when referring
to a version of a package.
Italic is a style, not a face - make the fontconfg page match
the TTF-and-OTF-fonts page.
Do not use caps for 'variable', it is not a proper noun.
Typos.
Change one or two 'normal' to other words: too many uses of normal
throughout the page. Mozilla's CSS doc describes weight 400 as
'Normal (Regular)', so for weights normal is the correct word
(Regular only applies to non-book non-oblique non-slant styles).
Rework GNU Freefonts text, Noto 'Latin' fonts include all recent
latin and cyrillic glyphs, the Freefonts only have minority glyphs
which were in Unicode in 2012. Noto is now preferred, so can
provide thos uncommon glyphs if it has been installed.
tuning-fontconfig - link directly to the Samples PDFs of my website
for viewing the aliases, as was already done under the Liberation
fonts in the TTF-and-OTF page.
Remove infromation about hinting from TTF-and-OTF-fonts page,
adding a comment to clarify that infromation about fontconfig
is on the previous page (in case anyone decides to install a
font and lands on the TTF-and-~OTF page).
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.
