https://bugzilla.redhat.com/show_bug.cgi?id=2001332
Bug ID: 2001332
Summary: pango-view with --backend=ft2 and ---antialias=none
generates antialiased renderings
Product: Fedora
Version: 34
Hardware: x86_64
OS: Linux
Status: NEW
Component: pango
Severity: high
Assignee: pwu(a)redhat.com
Reporter: andre.maute(a)gmx.de
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com,
pwu(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1820649
--> https://bugzilla.redhat.com/attachment.cgi?id=1820649&action=edit
image showing the problem
Description of problem:
Hello Fedora Team,
I have a recently updated Fedora 34 installation.
The problem I want to report is that it looks like
the pango-view tool is always turning antialiasing on
when one uses the FreeType backend --backend=ft2,
even when one explicitly switches antialiasing off with --antialias=none,
whereas it works for the --backend=cairo option.
A second question would be if the FreeType backend
generally doesn't/can't support --antialias=none?
I tried to find some examples in C with antialising turned off
but I wasn't successful.
I must confess I didn't check other distributions.
As pango-view is regarded as a tool for creating minimal reproducers
against the font rendering stack, I dare to set the severity to 'high' :-)
Best Regards
Andre
Version-Release number of selected component (if applicable):
$ uname -a
Linux localhost.localdomain 5.13.13-200.fc34.x86_64 #1 SMP Thu Aug 26 17:06:39
UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ dnf list installed | grep dejavu
dejavu-lgc-sans-fonts.noarch 2.37-16.fc34
@fedora
dejavu-lgc-sans-mono-fonts.noarch 2.37-16.fc34
@fedora
dejavu-lgc-serif-fonts.noarch 2.37-16.fc34
@fedora
dejavu-sans-fonts.noarch 2.37-16.fc34
@fedora
dejavu-sans-mono-fonts.noarch 2.37-16.fc34
@fedora
dejavu-serif-fonts.noarch 2.37-16.fc34
@fedora
$ dnf list installed | grep ImageMagick
ImageMagick.x86_64 1:6.9.11.27-3.fc34
@fedora
ImageMagick-libs.x86_64 1:6.9.11.27-3.fc34
@fedora
$ dnf list installed | grep pango
pango.i686 1.48.9-2.fc34
@updates
pango.x86_64 1.48.9-2.fc34
@updates
pango-devel.x86_64 1.48.9-2.fc34
@updates
pangomm.x86_64 2.46.1-1.fc34
@updates
$ dnf list installed | grep freetype
freetype.i686 2.10.4-3.fc34
@fedora
freetype.x86_64 2.10.4-3.fc34
@fedora
freetype-devel.x86_64 2.10.4-3.fc34
@fedora
$ dnf list installed | grep fontconfig
fontconfig.i686 2.13.94-2.fc34
@updates
fontconfig.x86_64 2.13.94-2.fc34
@updates
fontconfig-devel.x86_64 2.13.94-2.fc34
@updates
$ dnf list installed | grep cairo
cairo.i686 1.17.4-3.fc34
@fedora
cairo.x86_64 1.17.4-3.fc34
@fedora
cairo-devel.x86_64 1.17.4-3.fc34
@fedora
cairo-gobject.i686 1.17.4-3.fc34
@fedora
cairo-gobject.x86_64 1.17.4-3.fc34
@fedora
cairomm.x86_64 1.14.2-8.fc34
@fedora
python2-cairo.x86_64 1.18.2-8.fc34
@fedora
python3-cairo.x86_64 1.20.0-2.fc34
@fedora
How reproducible:
Always
Steps to Reproduce:
$ pango-view --no-display --dpi=72 --backend=cairo --antialias=none
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-cairo-aa-none.png
$ pango-view --no-display --dpi=72 --backend=cairo --antialias=gray
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-cairo-aa-gray.png
$ pango-view --no-display --dpi=72 --backend=cairo --antialias=subpixel
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-cairo-aa-subpixel.png
$ pango-view --no-display --dpi=72 --backend=ft2 --antialias=none
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-ft2-aa-none.png
$ pango-view --no-display --dpi=72 --backend=ft2 --antialias=gray
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-ft2-aa-gray.png
$ pango-view --no-display --dpi=72 --backend=ft2 --antialias=subpixel
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-ft2-aa-subpixel.png
$ gimp abc-*.png
Actual results:
Attached pngs.
The file abc-ft2-aa-none.png is in gray-scale and not as expected in
black-white.
The file abc-cairo-aa-none.png is in black-white as expected.
Expected results:
I would have expected the files abc*--aa-none.png looking near identical.
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=2009807
Bug ID: 2009807
Summary: Change default Amharic font from Abyssinica SIL to
Noto Serif Ethiopic
Product: Fedora
Version: 35
Hardware: x86_64
OS: Linux
Status: NEW
Component: Fonts
Severity: medium
Assignee: i18n-bugs(a)lists.fedoraproject.org
Reporter: beta-stage(a)tutanota.com
QA Contact: fonts-bugs(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Description of problem:
Abyssinica SIL is an old font. It's barely legible and breaks in most apps.
Noto Serif Ethiopic, on the other hand, is a modern and well designed font.
Noto Serif Ethiopic is distributed with Open Font License, so packaging it
won't be a problem.
Link
https://fonts.google.com/noto/specimen/Noto+Serif+Ethiopic?noto.query=Amhar…
How reproducible:
always
Steps to Reproduce:
1. Pretty much using the the Amharic language anywhere on Fedora
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2009807
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 QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2021366
https://bugzilla.redhat.com/show_bug.cgi?id=1909251
Bug ID: 1909251
Summary: stix-fonts-2.10 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: stix-fonts
Keywords: FutureFeature, Triaged
Assignee: nicolas.mailhot(a)laposte.net
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
nicolas.mailhot(a)laposte.net, paul(a)frixxon.co.uk
Target Milestone: ---
Classification: Fedora
Latest upstream release: 2.10
Current version/release in rawhide: 2.0.2-8.fc34
URL: http://sourceforge.net/projects/stixfonts
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/4893/
--
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=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.
https://bugzilla.redhat.com/show_bug.cgi?id=1806272
Bug ID: 1806272
Summary: forge-font macro transition causes broken dependencies
Product: Fedora
Version: rawhide
Status: NEW
Component: dejavu-fonts
Assignee: nicolas.mailhot(a)laposte.net
Reporter: decathorpe(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
nicolas.mailhot(a)laposte.net, paul(a)frixxon.co.uk,
peter(a)thecodergeek.com
Target Milestone: ---
Classification: Fedora
With the transition to new forge-based fonts macros, the -common subpackage was
dropped, but some packages depend on that. They are now not installable on
fedora 32+ because that package is gone (only Obsoleted, not Provided).
This affects at least python3-weasyprint.
Additionally, the sdljava-demo package now has broken dependencies as well:
- /usr/share/fonts/dejavu/DejaVuSans-Bold.ttf
- /usr/share/fonts/dejavu/DejaVuSans-BoldOblique.ttf
- /usr/share/fonts/dejavu/DejaVuSans-Oblique.ttf
- /usr/share/fonts/dejavu/DejaVuSans.ttf
Probably those files were renamed with the forge macro transition.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1977272
Bug ID: 1977272
Summary: sil-charis-fonts-6.000 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: sil-charis-fonts
Keywords: FutureFeature, Triaged
Assignee: nicolas.mailhot(a)laposte.net
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org, kevin(a)scrye.com,
nicolas.mailhot(a)laposte.net
Target Milestone: ---
Classification: Fedora
Latest upstream release: 6.000
Current version/release in rawhide: 5.000-14.fc33
URL: http://scripts.sil.org/CharisSIL_download
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/4818/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1890210
Bug ID: 1890210
Summary: CVE-2020-15999 freetype: heap-based buffer overflow
via malformed ttf files
Product: Security Response
Hardware: All
OS: Linux
Status: NEW
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: gsuckevi(a)redhat.com
CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com,
erack(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org,
gecko-bugs-nobody(a)redhat.com, gghezzo(a)redhat.com,
gnome-sig(a)lists.fedoraproject.org, gparvin(a)redhat.com,
jhorak(a)redhat.com, john.j5live(a)gmail.com,
jramanat(a)redhat.com, jweiser(a)redhat.com,
kevin(a)tigcc.ticalc.org, mclasen(a)redhat.com,
mkasik(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
scorneli(a)redhat.com, stcannon(a)redhat.com,
stransky(a)redhat.com, thee(a)redhat.com,
tpopela(a)redhat.com
Target Milestone: ---
Classification: Other
A flaw was found in freetype in the way it processes PNG images embedded into
fonts. A crafted TTF file can lead to heap-based buffer overflow due to integer
truncation in Load_SBit_Png function.
Reference:
https://savannah.nongnu.org/bugs/?59308
Upstream patch:
https://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=a3bab16…
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1820166
Bug ID: 1820166
Summary: Droid sans overrides my default CJK font
Product: Fedora
Version: 32
Status: NEW
Component: google-droid-fonts
Severity: low
Assignee: nicolas.mailhot(a)laposte.net
Reporter: taocrismon(a)hotmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
nicolas.mailhot(a)laposte.net, oliver(a)redhat.com,
paul(a)frixxon.co.uk, tremble(a)tremble.org.uk
Target Milestone: ---
Classification: Fedora
Description of problem:
I have this (per-user) fontconfig configuration to set my preferred sans-serif
font:
<alias>
<family>sans-serif</family>
<prefer>
<family>Noto Sans</family>
<family>Noto Sans CJK SC</family>
</prefer>
</alias>
It should fall back to "Noto Sans CJK SC" when displaying CJK characters. Since
F32 this isn't working anymore. CJK characters are rendered in a different
font, which I cannot recognize.
Digging through fc_debug logs, "Droid Sans" is appended right after "Noto
Sans", before "Noto Sans CJK SC" in the font matching list. Debug messages
confirm it's indeed Droid Sans getting picked.
Removing the relevant part in /etc/fonts/conf.d/65-google-droid-sans-fonts.conf
mitigates this issue. However since both Noto Sans & Droid Sans do not contain
CJK characters, they should both be skipped in favor of CJK fonts. Could this
be a metadata problem? i.e. Droid Sans wrongly advertises as CJK capable.
Version-Release number of selected component (if applicable):
google-droid-sans-fonts-20200215-3.fc32.noarch
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1938205
Bug ID: 1938205
Summary: google-droid-sans-fonts has higher priority than
google-noto-sans-fonts
Product: Fedora
Version: 34
Status: NEW
Component: google-droid-fonts
Assignee: nicolas.mailhot(a)laposte.net
Reporter: tagoh(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
nicolas.mailhot(a)laposte.net, oliver(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Summary says it all. I don't think Droid Fonts is better than Noto Fonts.
Version-Release number of selected component (if applicable):
google-droid-sans-fonts-20200215-9.fc34.noarch
How reproducible:
Steps to Reproduce:
1.rpmm -ql google-droid-sans-fonts google-noto-sans-fonts | grep conf.d
2.
3.
Actual results:
/etc/fonts/conf.d/65-google-droid-sans-fonts.conf
/etc/fonts/conf.d/66-google-noto-sans.conf
Expected results:
google-noto-sans one should come first.
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=2013083
Bug ID: 2013083
Summary: 31-cantarell.conf causes inconsistent font choice for
numerals and symbols when the system locale is zh-*
Product: Fedora
Version: 35
Status: NEW
Component: abattis-cantarell-fonts
Assignee: klember(a)redhat.com
Reporter: vtq-gnome(a)outlook.com
QA Contact: extras-qa(a)fedoraproject.org
CC: cosimo.cecchi(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
klember(a)redhat.com, mark(a)net-c.com, me(a)fale.io,
tagoh(a)redhat.com
Target Milestone: ---
Link ID: GNOME Gitlab GNOME/gnome-shell/-/issues/4683
Classification: Fedora
Created attachment 1832054
--> https://bugzilla.redhat.com/attachment.cgi?id=1832054&action=edit
Inconsistent font for numerals and symbols in Nautilus
Description of problem:
In Fedora Workstation, the GNOME desktop is using Cantarell as its main font.
However, the following section in /etc/fonts/conf.d/31-cantarell.conf, which
comes from Fedora's abattis-cantarell-fonts package, allows the font choice to
be overridden:
<match target="pattern">
<test qual="any" name="family">
<string>Cantarell</string>
</test>
<edit name="family" mode="assign" binding="weak">
<string>Cantarell</string>
</edit>
</match>
$ env LANG=en_US.utf8 fc-match Cantarell
Cantarell-Regular.otf: "Cantarell" "Regular"
$ env LANG=zh_CN.utf8 fc-match Cantarell
NotoSansCJK-Regular.ttc: "Noto Sans CJK SC" "Regular"
GTK/Pango seems to select a font based on the language of the text, and the
decision is affected by the context. When the text is only numerals and symbols
it will assume the language from the locale. This kind of decisions seems to be
reasonable too. So for example, Latin script will still be displayed with
Cantarell. "1234567890" will be displayed with Noto Sans CJK while "1234567890
GNOME" will be displayed with Cantarell (see screenshot):
$ env LANG=zh_CN.utf8 pango-view --markup -t '<span face="Cantarell"
font_features="tnum" size="xx-large">1234567890</span>'
$ env LANG=zh_CN.utf8 pango-view --markup -t '<span face="Cantarell"
font_features="tnum" size="xx-large">1234567890 GNOME</span>'
As a result, numerals and symbols in the GNOME UI are sometimes displayed with
Cantarell and sometimes displayed with Noto Sans CJK (see screenshots). The
inconsistency makes the UI appear broken. This is especially noticeable for
time in various places of the UI, because time is displayed in Noto Sans CJK
and the separator between hour and minute (a ratio symbol, which is a
full-width glyth in Noto Sans CJK and many other CJK fonts) has extra blank
space around it. (See https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4683)
Version-Release number of selected component (if applicable):
0.301-3.fc35
How reproducible:
Always
Steps to Reproduce:
1. In GNOME desktop, choose "中文 臺灣", "中文 香港", or "汉语 中国" in "Settings" –
"Region & Language" – "Language".
2. Log out & log in.
Actual results:
Numerals and symbols in the GNOME UI are sometimes displayed with Cantarell and
sometimes displayed with Noto Sans CJK (see screenshots).
Expected results:
Numerals and symbols should be consistently displayed with the same font,
ideally the same as the Latin alphabet. Since GNOME explicitly requests
Cantarell as UI font, Cantarell should be used here. Noto Sans CJK would only
be used as fallback for Chinese characters which are not covered by Cantarell.
Note that other common Latin fonts in the system are not overridden by Noto
Sans CJK like Cantarell is:
$ env LANG=zh_CN.utf8 fc-match "DejaVu Sans"
DejaVuSans.ttf: "DejaVu Sans" "Regular"
$ env LANG=zh_CN.utf8 fc-match "Liberation Sans"
LiberationSans-Regular.ttf: "Liberation Sans" "Regular"
$ env LANG=zh_CN.utf8 fc-match "Nimbus Sans"
NimbusSans-Regular.otf: "Nimbus Sans" "Regular"
Generally in mixed use of Latin and Chinese fonts, it is common to use the
selected Latin font for numbers and symbols and only fallback to the Chinese
font for glyths not covered. This is seen in word processors (e.g.
LibreOffice), Flatpak apps (because the Freedesktop runtime doesn't have font
config similar to the 31-cantarell.conf), as well as other OS (e.g. MacOS,
Android).
By deleting the previously mentioned fontconfig section in 31-cantarell.conf,
the expected results can be achieved (see screenshots).
env LANG=zh_CN.utf8 fc-match Cantarell
Cantarell-Regular.otf: "Cantarell" "Regular"
Additional info:
In my test without the relevant fontconfig section everything seems to be
working very well and I've not noticed any adverse effect. But I'm not aware of
why it was originally included in the package.
An alternative solution is to use Noto Sans CJK for everything if the locale is
zh-*. But this is less favorable because it's against upstream choice of
Cantarell and needs a change in gsettings-desktop-schemas for these locales.
The clock separator issue would additionally need workarounds in Nautilus and
in GNOME translations to fix.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2013083
https://bugzilla.redhat.com/show_bug.cgi?id=2033126
Bug ID: 2033126
Summary: fonttools-4.28.4 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: fonttools
Keywords: FutureFeature, Triaged
Assignee: pnemade(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
pnemade(a)redhat.com, sshedmak(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 4.28.4
Current version/release in rawhide: 4.28.3-2.fc36
URL: https://github.com/fonttools/fonttools/
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/7388/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2033126
https://bugzilla.redhat.com/show_bug.cgi?id=1993670
Bug ID: 1993670
Summary: segfault with pango-view assert in cairo
Product: Fedora
Version: 34
Hardware: x86_64
OS: Linux
Status: NEW
Component: pango
Severity: high
Assignee: pwu(a)redhat.com
Reporter: andre.maute(a)gmx.de
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com,
pwu(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:
1. This one works
$ pango-view --nodisplay --text "abc"
2. This one doesn't
$ pango-view --no-display --text "abc"
pango-view: cairo-hash.c:217: _cairo_hash_table_destroy: Assertion
`hash_table->live_entries == 0' failed.
Aborted (core dumped)
So pango-view triggers an assertion in Cairo.
Version-Release number of selected component (if applicable):
$ dnf repoquery --installed pango
pango-0:1.48.7-1.fc34.i686
pango-0:1.48.7-1.fc34.x86_64
How reproducible:
always
Steps to Reproduce:
1. see 1. of description above
2. see 2. of description above
Actual results:
segfault
Expected results:
no segfault
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=2035992
Bug ID: 2035992
Summary: Unknown license 0FL
Product: Fedora
Version: rawhide
Status: NEW
Component: abattis-cantarell-fonts
Assignee: klember(a)redhat.com
Reporter: msuchy(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: cosimo.cecchi(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
klember(a)redhat.com, mark(a)net-c.com, me(a)fale.io,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
abattis-cantarell-fonts.spec uses license 0FL which is not listed as approved
license here
https://fedoraproject.org/wiki/Licensing:Main#Software_License_List
Please either:
1) add the license to list of approved license (after discussion with
fedora-legal) or
2) update the license string or
3) remove the package from Fedora Distribution (I really hope this will not
be the case :) )
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2035992
https://bugzilla.redhat.com/show_bug.cgi?id=2035996
Bug ID: 2035996
Summary: Unknown license 0FL
Product: Fedora
Version: rawhide
Status: NEW
Component: adobe-source-code-pro-fonts
Assignee: mattrose(a)folkwolf.net
Reporter: msuchy(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org, mark(a)net-c.com,
mattrose(a)folkwolf.net
Target Milestone: ---
Classification: Fedora
The license of adobe-source-code-pro-fonts.spec is 0FL but
https://fedoraproject.org/wiki/Licensing:Main#Software_License_List does not
recognizes this license.
I believe you have there typo and correct license is OFL. Mind the letter O
instead of number zero.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2035996
https://bugzilla.redhat.com/show_bug.cgi?id=2031877
Bug ID: 2031877
Summary: pango 1.50.0-1.fc35 makes darktable crash
Product: Fedora
Version: 35
Hardware: x86_64
OS: Linux
Status: NEW
Component: pango
Severity: low
Assignee: pwu(a)redhat.com
Reporter: thommy.m.malmstrom(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com,
pwu(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:
After a "sudo dnf upgrade --refresh" pango version 1.50.0-1.fc35 was installed.
Then darktable started to crash repeatedly.
Version-Release number of selected component (if applicable):
1.50.0-1.fc35
How reproducible:
Steps to Reproduce:
1. Start darktable
2. Try to do a crop&rotate
3.
Actual results:
darktable crashes
Expected results:
darktable to crop the image
Additional info:
I downgrade pango to previous version 1.49.1-1.fc35 and then darktable works as
expected.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2031877
https://bugzilla.redhat.com/show_bug.cgi?id=2028489
Bug ID: 2028489
Summary: freetype-2.11.1 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: freetype
Keywords: FutureFeature, Triaged
Assignee: mkasik(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
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, mclasen(a)redhat.com,
mkasik(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 2.11.1
Current version/release in rawhide: 2.11.0-1.fc35
URL: https://www.freetype.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/854/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2028489
https://bugzilla.redhat.com/show_bug.cgi?id=2029061
Bug ID: 2029061
Summary: fonttools-4.28.3 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: fonttools
Keywords: FutureFeature, Triaged
Assignee: pnemade(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
pnemade(a)redhat.com, sshedmak(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 4.28.3
Current version/release in rawhide: 4.27.1-1.fc36
URL: https://github.com/fonttools/fonttools/
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/7388/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2029061