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.
libxkbcommon-1.6.0 removes some definitions that are unused.
These definitions are referenced in qtbase so we remove them
with a sed for both the full qt5 package and gt5-alternate.
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...
It now unconditionally runs gtk-update-icon-cache (or
gtk4-update-icon-cache) after installing the icons. As a result, we need
something to install gtk-update-icon-cache.
For the benefit of jhalfs, I've set gtk3 as a normal dependency, but
gtk4 as a nodep :)
Thanks goes to Joe Locash for the report.
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.
It's optional for the packages that use it, and they only use it to
provide additional support for profiling.
Sysprof now requires two more packages which are specific to it, so
let's archive it.
- make change from /usr to opt/xorg "nodump"
- make the removal of "-nolisten tcp" "nodump"
- narrow the change from none to on to the "Numlock" line: otehrwise
the comments about this option become incomprehensible:
(e.g. "option can be on, off, or on")
If xmlto is not installed and -Dgtk_doc=false, there will be no
documentation installed.
Also add a rm -rf command so we won't do things wrong reinstalling the
package.
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.
I had the Intel Media Driver installed on this system at some point in
the distant past, and it installed /etc/profile.d/intel-media.sh - which
overrode the libva-intel-driver, and caused gstvaapi.so to fail to load
correctly on Wayland... which then caused GDM to fail to start. Note
that X11 worked fine because of using a different code path.
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.
PRC contains mainland China, Hong Kong, Macao, and Taiwan. (In some
uses "mainland" also contains Hong Kong and Macao, but it depends on
the context).
In mainland China many users want TC and JP fonts alongside SC font
because once you know SC you can just read TC seamlessly, and many
Chinese Linux users (not including me) are Japanese cartoon or game
fans. IMO using the monolithic CJK .ttc font file is easier.
1. mention variable fonts (not generally useful for the desktop)
2. Cantarell is now at google fonts
3. The organization of Noto fonts has changed. Provide an example
for how to download, and working links for the CJK variants (now
just Noto Sans JP etc).
4. Oxygen Sans and Mono now at google fonts, but each is separate.
5. Comment the Noto Sans CJK item, the links are no longer useful
and the fonts have been renamed.
6. Fix the debian UMing link to point to the tarball.
One of the things I've been doing over the past week is building
packages that list &qt5-deps or &qt5-components with Qt Alternate and Qt
Components.
For each one I've been checking logs for relevant information to Qt. It
doesn't show up in my logs, so I checked the Configure script and didn't
notice anything in there either.
When checking the NEWS file, I found out that several backends have been
removed - including cogl, qt, and DirectFB.
With Mesa-23, all of the tests other than the ES2 tests will fail due to
minor differences in behavior between Mesa-22 and Mesa-23.
This doesn't seem to cause any problems at runtime, so we'll just
document the failures.
If setxkbmap is not installed, Xwayland will refuse to start.
In a "normal" build Xorg applications should be pulled in by Xorg fonts
-> xcursor-themes -> Xorg applications, but we are saying "only
font-util" for Xorg fonts and font-util does not need xcursor-themes.
1. Don't throw unspecified entries too early. Doing so caused various
rendering glitches. And we can now also check if an entry is
selected but it's parent not.
2. "menu"s in Kconfig can also have dependencies...
Some pre-existing .toml data files are found problematic after the
change, fix them and regenerate all rendered -kernel.xml files.
This is stupid and it will cause meaningless diffs in version control
(like this commit does :( ).
Remove the kernel version from the generated XML files. Add
kernel.version file into git to track the kernel version.
The kernel-config.py script takes a toml file containing a set of
kernel configuration key-value pairs. Then it parses the Kconfig files
in a kernel source tree and render the given configuration as a
LFS-style <screen> in a separate XML file. The XML file can be used in
the book with xinclude.
Some "features":
1. The lines are limited to 80 columns.
If the text of the configuration option is too long, it will be
trimmed; if the symbolic name of the option cannot fit in this line,
a separate line will be used for it.
2. If a configuration option is given but it does not exist in Kconfig
files, the script will abort immediately. This helps catching
removed options.
3. The script also aborts immediately if a configuration option is
illegal, for example setting an option to 'M' while it cannot be a
module.
4. The infrastructure is not wired into the main Makefile. It's because
not all editors have the latest kernel tree, and even if they do the
locations of the kernel tree are still different. To update the
generated XML files, use
"make -C kernel-config KERNEL_TREE=/sources/linux-x.y.z".
Backword incompatible change:
The script no longer outputs "CONFIG_" prefix for the symbolic name. It
really does not make too much sense to waste 7 characters here because
it's a common prefix for all options!
A limitation:
The script does not really validate the configuration. Generally
validating the configuration requires to solve the 3-CNF-SAT problem,
which is NP-complete.
1. Move the configuration file into /etc, to be consistent with other
configuration files created in BLFS.
2. We no longer need a separate "configure the graphic card" example
because the TearFree configuration file is already a good example.
3. Tearing issue is really not new after xf86-video-* removal. In some
xf86-video-* drivers a TearFree option is available but rarely
enabled by default (only the amdgpu driver when the output is rotated
or transformed). So this is actually the first time we document it
in BLFS.
4. It's really not difficult to observer the tearing by dragging a
window in twm, despite twm only renders the window border during
dragging.
With modesetting driver, $HOME/.local/share/xorg/Xorg.0.log contains:
[ 65817.713] (II) AIGLX: Loaded and initialized crocus
And there is no more "AIGLX error" messages.
