at-spi2-core allows building Qt5LinuxAccessibility, which is
required for kwin... Note that this is not new in 5.15.12, but
I found it while testing this version.
To do this I've created build_fixes-2.patch. This contains:
- Fix for shipped ffmpeg build failure
- Fixes for Python 3.11 changes
- Changes for ICU-74, but modified to allow building on previous
versions of BLFS and their versions of ICU
- The NINJAJOBS change
- Chunks from a patch from ArchLinux32 to prevent instantaneous crashes
in Falkon. Still causes issues with text rendering, so I've created a
note in the Falkon page. However, video playback and images display
perfectly. I will revisit this in February once we have the new glibc.
Unlike previous issues, it no longer crashes, so that's a good start!
This significantly brings down the count of instructions for this page
and should make it a lot easier to follow.
I've tested this on both x86_64 and i686. On i686 there's a major
improvement in that Falkon (and KDE System Monitor) actually start and
run, though in the case of Falkon there is still no text.
Update to plasma-wayland-protocols-1.12.0.
Update to plasma5-5.27.10.
Update to kde gear-23.08.4 including kate, kwave, and falkon.
Update to kf5-5.113.0.
This resulted in the currency script returning a new version, while also
being inconsistent (the title says 1.2.0, but we're offering 1.1.0 for
download)
TTF-and-OTF-fonts - make CJK fonts a section2 so that it is
slightly bigger than the other items. Everything after it, either
re languages or specific fonts, is logically part of CJK fonts.
No change in indexing (i.e. CJK fonts itself is not indexed).
I reworked the paragraph about Unicode coverage, but left the
original in place while working on it, and then forgot to remove
it, causing an almost duplicate paragraph.
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.
Note that at this time, it's backend is still considered experimental.
It also requires Google's shader compiler to build, which is available
from https://github.com/google/shaderc/blob/main/downloads.md. This is
also known as 'glslc'.
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.
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.
