https://bugzilla.redhat.com/show_bug.cgi?id=2021366
Bug ID: 2021366
Summary: Nimbus Mono PS font should not fc-match Courier, as
certain letter combinations are not monospaced
Product: Fedora
Version: 35
Hardware: x86_64
OS: Linux
Status: NEW
Component: Fonts
Assignee: i18n-bugs(a)lists.fedoraproject.org
Reporter: info(a)skierpage.com
QA Contact: fonts-bugs(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Created attachment 1840789
--> https://bugzilla.redhat.com/attachment.cgi?id=1840789&action=edit
look at "affiliation"
Description of problem:
I visited https://schema.org/Person in Firefox in Fedora 35 KDE spin and
noticed the monospace text "affiliation" was not monospaced; the letters "ffi"
were on top of each other as if replaced by the ligature ffi.
The page CSS is styling the <code> tag "font-family: Courier, monospace;", and
in Fedora 35 KDE Spin `fc-match Courier` returns
NimbusMonoPS-Regular.otf: "Nimbus Mono PS" "Regular"
indeed, if I set font-family to "Nimbus Mono PS" in some simple HTML
https://www.skierpage.com/bugs/nimbusmono_not_monospaced.html , other ff
combinations are also "ligature-ized".
I tried these two URLs in the chromium-browser package and in the Epiphany and
Konqueror browser flatpaks. These did not use "Nimbus Mono PS" as the fallback
font for font-family "Courier" so did not display "affiliation" badly on the
Person web page, but if you specify font-family "Nimbus Mono PS", you get the
ligature.
Version-Release number of selected component (if applicable):
Mozilla Firefox 94.0
urw-base35-fonts-20200910-9.fc35.src.rpm
How reproducible:
Always.
Steps to Reproduce:
1. Visit https://schema.org/Person and
https://www.skierpage.com/bugs/nimbusmono_not_monospaced.html in Firefox and
other browsers.
2. Note how "ffi" appears.
Actual results:
Firefox uses "Nimbus Mono PS" as the fallback for font-family Courier; all
these browsers replace "ffi" and such with the ligature character in "Nimbus
Mono PS", destroying the desired monospace effect.
Expected results:
Monospaced fonts should appear... monospaced, so every character should occupy
the same amount of horizontal space. However, if a font provides ligature
glyphs for "ffi" and such, then it's unclear if it's wrong for the browser to
use them; (l33t developers now explicitly use monospaced coding fonts that do
wacky substitutions.)
So the fix could be for Firefox and/or fc-match to _not_ use Nimbus Mono PS
when text handling requests Courier. The other browsers on my system don't,
I'm not sure why. Another could be to remove the ligatures from Nimbus Mono PS.
Additional info:
The rendering of code on that page (see attachment) is pretty terrible, note
the oversized 'd's in "address". Another reason to have Courier match some
other monospaced font than Nimbus Mono PS.
You can use the Fontmatrix program to enable OpenType features; checking latn >
dflt > liga changes the display of "ff" combinations.
Firefox using ligatures in monospaced fonts is
https://bugzilla.mozilla.org/show_bug.cgi?id=384395 , was closed WONTFIX "We
can't really do anything about it -- the underlying text system is doing the
ligaturization, not us".
ArchLinux users discussed the problem in
https://bbs.archlinux.org/viewtopic.php?id=238832
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2021366
https://bugzilla.redhat.com/show_bug.cgi?id=2054680
Bug ID: 2054680
Summary: workaround gtk4 preferring ibus-gtk4 to Wayland input
protocol
Product: Fedora
Version: rawhide
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: petersen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Currently in Fedora WS Wayland Gnome, gtk4 prefers ibus-gtk4
to the Wayland protocol - which causes the candidate window
to be badly placed. (However we need ibus-gtk4 for Xorg sessions.)
Seems a workaround might be to patch:
--- ibus-1.5.24/client/gtk4/ibusim.c.orig 2021-07-30 23:12:21.747541875
+0900
+++ ibus-1.5.24/client/gtk4/ibusim.c 2021-07-31 01:55:43.785097447 +0900
@@ -34,10 +34,13 @@ g_io_im_ibus_load (GTypeModule *type_mod
if (!inited) {
ibus_init ();
ibus_im_context_register_type (type_module);
+ /* "wayand" prority is 0 and "gtk-im-context-simple" one is G_MININT,
+ * "ibus" one is -100 here.
+ */
g_io_extension_point_implement ("gtk-im-module",
IBUS_TYPE_IM_CONTEXT,
"ibus",
- 50);
+ -100);
inited = TRUE;
}
/* make module resident */
But does this cause some problems?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2054680
https://bugzilla.redhat.com/show_bug.cgi?id=2015628
Bug ID: 2015628
Summary: No entry /sys/class/leds for Fn 5 key that toggles
keyboard backlight
Product: Fedora
Version: 34
Hardware: x86_64
OS: Linux
Status: NEW
Component: xkeyboard-config
Severity: medium
Assignee: peter.hutterer(a)redhat.com
Reporter: eb30750(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org,
negativo17(a)gmail.com, peter.hutterer(a)redhat.com,
rhughes(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem: Keyboard backlight worked until upgrading to FC34. The
Fn 5 key toggled the keyboard backlight on and off. In researching the new
method to expose the Fn keys to the user I found that there is no input/input5.
The input/input3 is configured.
lrwxrwxrwx 1 root root 0 Jul 10 16:30 input3::capslock ->
../../devices/platform/i8042/serio0/input/input3/input3::capslock
lrwxrwxrwx 1 root root 0 Jul 10 16:30 input3::numlock ->
../../devices/platform/i8042/serio0/input/input3/input3::numlock
lrwxrwxrwx 1 root root 0 Jul 10 16:30 input3::scrolllock ->
../../devices/platform/i8042/serio0/input/input3/input3::scrolllock
lrwxrwxrwx 1 root root 0 Jul 10 16:30 phy0-led ->
../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/leds/phy0-led
Version-Release number of selected component (if applicable):
5.14.11-200.fc34.x86_64
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
A script or kernel option that builds the /sys/class/leds/input/input5
hierarchy.
Additional info:
If the input5 exists then simply changing the brightness value should turn on
the keyboard backlight.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2015628
https://bugzilla.redhat.com/show_bug.cgi?id=1903877
Bug ID: 1903877
Summary: kde-l10n-pa missing translated file
Product: Fedora
Version: 33
Status: NEW
Component: kde-l10n
Keywords: i18n
Assignee: than(a)redhat.com
Reporter: aalam(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
kde-sig(a)lists.fedoraproject.org, me(a)dvratil.cz,
rdieter(a)gmail.com, smparrish(a)gmail.com,
than(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1735891
--> https://bugzilla.redhat.com/attachment.cgi?id=1735891&action=edit
KDE system Tray (software, Keyboard Indicator)
Description of problem:
Version-Release number of selected component (if applicable):
kde-l10n-pa-17.08.3-9.fc33.noarch
apper-1.0.0-6.fc32.x86_64
How reproducible:
every time
Steps to Reproduce:
1. translation is not available for various KDE packages
2.rpm -q kde-l10n-pa -l|grep apper||grep
rpm -q kde-l10n-pa -l|grep kdeplasma
3.
Actual results:
applications are untranslated. Various untranslated section on KDE desktop in
Punjabi
No output for file search
Expected results: 4 following files
apper._desktop_.po
apper.po
org.kde.apper.appdata.po
plasma_applet_org.packagekit.updater.po
Additional info:
KDE svn source has apper fully transalted files for Punjabi since 2011:
https://websvn.kde.org/trunk/l10n-kf5/pa/messages/apper/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1809989
Bug ID: 1809989
Summary: By default install Noto fonts for Unicode scripts not
already covered by default
Product: Fedora
Version: 31
Status: NEW
Component: google-noto-fonts
Assignee: petersen(a)redhat.com
Reporter: hsivonen(a)hsivonen.fi
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, psatpute(a)redhat.com,
pwu(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
There is currently movement towards protecting browser users from font
fingerprinting. This means refusing, by default, to load user-installed fonts,
which makes the set of fonts that each OS installs by default even more
important than before.
Firefox bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1582687
W3C CSS WG issue:
https://github.com/w3c/csswg-drafts/issues/4497
Currently, Windows 10, macOS, Android, and Chrome OS provide broader
installed-by-default Unicode coverage than Fedora.
Examples of living scripts that have enough active users to make it to the list
at
https://en.wikipedia.org/wiki/List_of_writing_systems#List_of_writing_scrip…
but are not supported by default in Fedora 31 include Javanese, Sundanese,
Batak, Balinese, Mongolian, and New Tai Lue.
Egyptian hieroglyphs is an example of a dead script the Fedora 31 doesn't
support out of the box but Windows 10, macOS, Chrome OS, and Android do.
To remedy this with minimal disk space impact, I suggest the same approach that
Apple took. Apple bundles with macOS those Noto fonts that cover scripts that
were not already covered by the previous installed-by-default set of fonts on
macOS. In the macOS case, the on-disk footprint of the Noto fonts that were
required to take macOS to Android/Chrome OS-competitive Unicode coverage was
only a couple of megabytes. (The fonts are hidden in /Library/Application
Support/Apple/Fonts/Language Support/.) In the case of Fedora, the set of Noto
fonts required to reach the Chrome OS / Android level of script coverage is a
bit larger than in the macOS case but should still be manageable.
Please install, by default, those Noto fonts that provide support for scripts
that are not properly supported by the fonts that Fedora already installs by
default.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2054934
Bug ID: 2054934
Summary: cldr-emoji-annotation-41-alpha2 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: cldr-emoji-annotation
Keywords: FutureFeature, Triaged
Assignee: tfujiwar(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 41-alpha2
Current version/release in rawhide: 41~alpha1-1.fc37
URL: https://github.com/unicode-org/cldr
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from Anitya:
https://release-monitoring.org/project/103642/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2054934
https://bugzilla.redhat.com/show_bug.cgi?id=1832351
Bug ID: 1832351
Summary: Macintosh keyboard variants not available
Product: Fedora
Version: 32
Hardware: x86_64
Status: NEW
Component: xkeyboard-config
Severity: medium
Assignee: peter.hutterer(a)redhat.com
Reporter: mthoemme(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org,
john.j5live(a)gmail.com, negativo17(a)gmail.com,
peter.hutterer(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
I do not have any variants for Macintosh available when trying to change the
keyboard layout via the GUI (Region & Language Settings).
Trying to manually set the keymap in the locale works for the VC keymap, but
not for the X11 Layout. It will set VC keymap to "de-mac" or "de_mac"
respectively, leave the X11 Layout at "de"
localectl set-keymap de-mac
Digging even deeper, the following commands all yield the same errors:
localectl set-x11-keymap de-mac
localectl set-x11-keymap de_mac
localectl set-x11-keymap de macintosh de_mac
All yield: "Failed to set keymap: Specified keymap cannot be compiled, refusing
as invalid."
Version-Release number of selected component (if applicable):
dnf info xkeyboard-config
Last metadata expiration check: 1:03:51 ago on Mi 06 Mai 2020 15:54:00 CEST.
Installed Packages
Name : xkeyboard-config
Version : 2.29
Release : 1.fc32
Architecture : noarch
Size : 5.5 M
Source : xkeyboard-config-2.29-1.fc32.src.rpm
Repository : @System
From repo : anaconda
Summary : X Keyboard Extension configuration data
URL : http://www.freedesktop.org/wiki/Software/XKeyboardConfig
License : MIT
Description : This package contains configuration data used by the X Keyboard
Extension (XKB),
: which allows selection of keyboard layouts when using a
graphical interface.
How reproducible:
Happens consistently. I'm on a fresh Fedora 32 install.
Steps to Reproduce:
1. localectl set-x11-keymap de macintosh de_mac
Actual results:
"Failed to set keymap: Specified keymap cannot be compiled, refusing as
invalid."
Expected results:
Successfully sets the keyboard layout to a Macintosh variant.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2058832
Bug ID: 2058832
Summary: translate-toolkit-3.6.0 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: translate-toolkit
Keywords: FutureFeature, Triaged
Assignee: suanand(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dwayne(a)translate.org.za,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com,
petersen(a)redhat.com, suanand(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 3.6.0
Current version/release in rawhide: 3.5.3-2.fc36
URL: http://toolkit.translatehouse.org/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from Anitya:
https://release-monitoring.org/project/3685/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2058832
https://bugzilla.redhat.com/show_bug.cgi?id=1961723
Bug ID: 1961723
Summary: dnf reports errors when processing
translate-toolkit.noarch
Product: Fedora
Version: rawhide
Hardware: x86_64
OS: Linux
Status: NEW
Component: translate-toolkit
Severity: high
Assignee: suanand(a)redhat.com
Reporter: grgoffe(a)yahoo.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dwayne(a)translate.org.za,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com,
petersen(a)redhat.com, suanand(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem: Attempting upgrade of this system; dnf reports an error
condition which stops upgrade (see below)
Version-Release number of selected component (if applicable):
see below
How reproducible:
always
Steps to Reproduce:
1.see below
2.
3.
Actual results: see below
Expected results: successful and clean system upgrade
Additional info:
/usr/bin/dnf --noautoremove --refresh --skip-broken --allowerasing --best
--setopt=zchunk=0 --exclude='*'kernel'*' --exclude=erlang'*'
--exclude='environment-modules*' --exclude=Lmod upgrade /root/upgrade.log
Script started, output log file is '/root/upgrade.log'.
Fedora rawhide openh264 (From Cisco) - x86_64
2.5 kB/s | 989 B 00:00
Fedora - Modular Rawhide - Developmental packages for the next Fedora release
679 kB/s | 1.6 MB 00:02
Fedora - Rawhide - Developmental packages for the next Fedora release
1.3 MB/s | 64 MB 00:47
Error:
Problem: cannot install the best update candidate for package
translate-toolkit-3.3.5-1.fc35.noarch
- problem with installed package translate-toolkit-3.3.5-1.fc35.noarch
- nothing provides python3.9dist(lxml) >= 4.6.3 needed by
translate-toolkit-3.3.6-1.fc35.noarch
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1784650
Bug ID: 1784650
Summary: Fontconfig is slow, causing stuttering and freezing
Product: Fedora
Version: 31
Status: NEW
Component: fontconfig
Severity: high
Assignee: tagoh(a)redhat.com
Reporter: bepvte+bugzilla(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
john.j5live(a)gmail.com, mclasen(a)redhat.com,
pnemade(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Fontconfig is much much slower than on other distros, and it stutters or
freezes applications that use it.
Version-Release number of selected component (if applicable):
Name : fontconfig
Version : 2.13.92
Release : 3.fc31
Architecture: x86_64
How reproducible:
I can reproduce this bug on a fresh Fedora 31 vm with the Xfce desktop and
google-noto-sans-* fonts installed.
Steps to Reproduce:
1. dnf install google-noto-sans-*
2. run gedit on the attached example file
alternatively
1. dnf install google-noto-sans-*
2. open firefox and browse to https://www.wikidata.org/wiki/Q52 (page with lots
of languages)
Actual results:
It takes around 60 seconds for gedit to become responsive to scrolling and
input. Mousepad is faster but still slow.
It takes firefox upwards of 5 minutes to get to first paint on a page with many
fonts or languages, compared to a simpler page.
Expected results:
Gedit should load files with many fonts at a similar speed as other distros.
The page should load quickly, like on Debian and others.
Additional info:
I have tried to diagnose the source of this issue in many ways.
Running `perf trace` on what sysprof indicated was the most busy function
(FcStrCmpIgnoreCaseAndDelims), shows that every name of every font family is
being compared to every other name of every other font family. I do not know if
this is a normal behaviour of fontconfig.
I have noticed the amount of calls to "FcStrCmpIgnoreCaseAndDelims" and program
startup time both drop to a similar amount as Debian's when all of the
"google-noto" configuration files in /etc/fonts/conf.d/ are deleted (These
files are not present in Debian). However, this might not be the source of the
problem:
In the Debian vm, with a copy of my computer's /etc/fonts/, including the
google-noto files, (I took care to ensure that there would be no broken
symlinks) and /usr/share/fonts, fontconfig does not stall any programs. The
amount of calls to FcStrCmpIgnoreCaseAndDelims is also much lower as well.
This led me to believe that it was a difference caused by compiler flags but
this does not seem to be the case. I tried to replace the optflags in the
package, except for the rpmbuild required debug ones, and found no difference.
I also checked to ensure that it was not caused by GCC version differences.
Debian results for mousepad:
1,845,449 calls to FcStrCmpIgnoreCaseAndDelims
Time: 5 seconds
Fedora results for mousepad:
11,658,380 calls to FcStrCmpIgnoreCaseAndDelims
Time: 23 seconds
https://perfht.ml/2tleJxN
Here is a link to a Firefox profiler result of the wikidata page, where in the
flame graph you can see that Firefox is spending most of its time in
fontconfig. You can also see "FirstNonBlankPaint" is at 50 seconds in the
marker table.
TLDR: Fontconfig matching is slow with all google-noto fonts installed, unless
you remove the noto config files. Using the same exact font directory and
config directory (including the noto config files) on Debian does not cause the
same problem.
--
You are receiving this mail because:
You are on the CC list for the bug.