Explain that some recent fonts have TTF files with hinting, and
OTF files without. Expand the comment in TTF-and-OTF-fonts to
explain why OTF should be preferred, and link to previous page
for why hinting can be undesirable or unusable.
Rework second fc-match example:
'fcmatch -a TYPE | less' is useless: -a functions similarly to
fc-list, any following parameter is ignored. So the example listed
all installed font-style-weight combinations for all three TYPEs.
Replace by plain fc-match TYPE.
Remove TYPE specification from introductory paragraph, it is only
used for the replacement command here. Use the same markup for the
command and in the explanations, so that a capital TYPE in the
explanations is replaced by a smaller slanted TYPE.
The command after this shows a fuller variant with the type, lang
and weight being specified.
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).
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.
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.
I know it is somewhat useless, but I don't like them for
two reasons: first they cannot be seen, and I do not like things I
cannot see. Second, git highlights them, and this is disturbing...
It's coming yet for a' that,
That ilka body the world o'er,
Can use Guid Fonts for a' that.
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@18211 af4574ff-66df-0310-9fd7-8a98e5e911e0
