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.
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.
This module fails to build on i686 due to an issue with the bundled
version of the PhysX SDK.
Since we're already disabling Qt3D due to a problem with the bundled
copy of assimp, let's just skip the Qt Quick bindings as well.
This is a rough version of the new Qt6 page. The installation
instructions should be OK, but the Dependencies, Contents, and
Short Descriptions need to be checked.
The instructions have not yet been checked on a systemd system.
There is no ChangeLog entry yet. It will be added when the page
has been validated.
Fix up libadwaita to build with it. Update the command explanation to
allow building it with Qt-5. Also fix the errors detected in
org.linuxfromscratch.lfs.xml reported by "appstreamcli validate".
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.
