[Bug 2088665] New: Noto Sans is chosen to display symbol characters
it doesn't contain
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2088665
Bug ID: 2088665
Summary: Noto Sans is chosen to display symbol characters it
doesn't contain
Product: Fedora
Version: 36
Status: NEW
Component: google-noto-fonts
Assignee: tagoh(a)redhat.com
Reporter: talk(a)danielflaum.net
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
Created attachment 1881507
--> https://bugzilla.redhat.com/attachment.cgi?id=1881507&action=edit
A zipped sample PDF and image of relevant portion of PDF when affected by the
issue
Description of problem:
Given a PDF lacking embedded fonts which use certain characters (including →
and ≥), GNOME's Evince on Fedora 36 chooses to substitute the Noto Sans font,
which does not include these characters.
Version-Release number of selected component (if applicable):
How reproducible:
Successfully reproduced by two people independently.
Steps to Reproduce:
1. Boot a fresh copy of Fedora 36 (the Live version in a VM will do).
2. Open the attached sample PDF in GNOME Evince (aka Document Viewer).
3. Observe the missing characters in the second paragraph from the top of the
page.
Actual results:
See attached image.
Expected results:
The missing characters should be displayed properly as → (that is,
https://unicode-table.com/en/2192/).
Additional info:
The filer initially sought help at
https://ask.fedoraproject.org/t/missing-characters-in-pdfs-since-upgrade-...,
which may be informative in reproducing the issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2088665
1 month, 1 week
[Bug 2093080] New: Default fonts for Arabic do not match the font
packages list
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2093080
Bug ID: 2093080
Summary: Default fonts for Arabic do not match the font
packages list
Product: Fedora
Version: 36
Hardware: All
OS: Linux
Status: NEW
Component: fontconfig
Severity: medium
Assignee: tagoh(a)redhat.com
Reporter: awilliam(a)redhat.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, 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
There's a test case:
https://fedoraproject.org/wiki/QA:Testcase_i18n_default_fonts
which requires checking the default fonts for various languages against a list,
http://tagoh.fedorapeople.org/fonts/fc-test.sh .
The current default fonts for Arabic installs do not match the list. The list
states sans should be DejaVu Sans, serif should be FreeSerif or MPH 2B Damase,
and mono should be DejaVu Sans Mono. These may have been changed recently, as
our openQA reference text file expects them to be Noto Naskh Arabic (for both
sans and serif?) and PakType Naskh Basic for mono.
In any case, what we actually see doesn't match either the list or the openQA
reference file. We see "Noto Sans Arabic" and "PakType Naqsh" in the output
from the test, I think for serif (yes really) and monospace respectively.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2093080
1 month, 1 week
[Bug 1761885] New: rpm -V complains about mode for ghost .uuid files
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1761885
Bug ID: 1761885
Summary: rpm -V complains about mode for ghost .uuid files
Product: Fedora
Version: rawhide
Status: NEW
Component: fontpackages
Assignee: nicolas.mailhot(a)laposte.net
Reporter: mtasaka(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,
redhat-bugzilla(a)linuxnetz.de, tagoh(a)redhat.com
Target Milestone: ---
Link ID: Red Hat Bugzilla 1564432
Classification: Fedora
Description of problem:
rpm -Va complains a lot about mode of %ghost .uuid files:
.M....... g /usr/share/fonts/paktype-naqsh/.uuid
.M....... g /usr/share/fonts/lilypond/.uuid
.M....... g /usr/share/fonts/sil-padauk/.uuid
.M....... g /usr/share/fonts/google-droid/.uuid
.M....... g /usr/share/fonts/lilypond/.uuid
.M....... g /usr/share/fonts/smc-suruma/.uuid
.M....... g /usr/share/fonts/google-android-emoji/.uuid
.M....... g /usr/share/fonts/google-crosextra-carlito/.uuid
.M....... g /usr/share/fonts/lohit-assamese/.uuid
.M....... g /usr/share/fonts/dejavu/.uuid
.M....... g /usr/share/fonts/lohit-telugu/.uuid
.M....... g /usr/share/fonts/lilypond/.uuid
.....
Looks like fontpackages-devel template rpmmacro creates .uuid which %ghost
%atttr(0000)
e.g.
[root@localhost ~]# rpm -qf /usr/share/fonts/google-droid/.uuid
google-droid-sans-fonts-20120715-16.fc31.noarch
[root@localhost ~]# rpm -qlv google-droid-sans-fonts | grep uuid
---------- 1 root root 0 7月 25 23:03
/usr/share/fonts/google-droid/.uuid
ref:
https://src.fedoraproject.org/rpms/fontpackages/blob/master/f/fontpackage...
but I guess %transfiletriggerin script by fontconfig creates .uuid as 0755
permission (perhaps)
Version-Release number of selected component (if applicable):
fontpackages-filesystem-1.44-25.fc31.noarch
fontconfig-2.13.92-3.fc31.x86_64
fontconfig-2.13.92-3.fc31.i686
google-droid-sans-fonts-20120715-16.fc31.noarch
How reproducible:
100%
Steps to Reproduce:
1. See above, try $ rpm -Va
2.
3.
Actual results:
See above, lots of .uuid permission complaint
Expected results:
No complaint by rpm -Va
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
2 months
[Bug 2265259] New: google-noto-sans-phags-pa-fonts fails to upgrade
from F39 -> F40
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2265259
Bug ID: 2265259
Summary: google-noto-sans-phags-pa-fonts fails to upgrade from
F39 -> F40
Product: Fedora
Version: 40
OS: Linux
Status: NEW
Component: google-noto-fonts
Severity: high
Assignee: tagoh(a)redhat.com
Reporter: msuchy(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
During upgrade from F39 to F40 I get this error:
Problém 3: package google-noto-sans-phags-pa-fonts-20230801-4.fc39.noarch from
@System requires google-noto-fonts-common = 20230801-4.fc39, but none of the
providers can be installed
- google-noto-fonts-common-20230801-4.fc39.noarch from @System does not
belong to a distupgrade repository
- problém s nainstalovaným balíčkem
google-noto-sans-phags-pa-fonts-20230801-4.fc39.noarch
Problém 4: package network-scripts-ppp-2.5.0-3.fc39.x86_64 from @System
requires network-scripts, but none of the providers can be installed
This is because the subpackage google-noto-sans-phags-pa-fonts in F39 that is
named differently in F40 google-noto-sans-phagspa-fonts. Mind the difference
between phagspa vs. phags-pa.
This blocks upgrades for users from F39.
Here is policy regarding renaming packages
https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-re...
Reproducible: Always
Steps to Reproduce:
1. sudo dnf --releasever=40 --setopt=module_platform_id=platform:f40 \
--enablerepo=updates-testing \
$(rpm -q fedora-repos-modular >/dev/null && echo
--enablerepo=updates-testing-modular) \
--assumeno distro-sync
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2265259
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
2 months
[Bug 2112732] New: Fail to build from source
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2112732
Bug ID: 2112732
Summary: Fail to build from source
Product: Fedora
Version: rawhide
Status: NEW
Component: campivisivi-titillium-fonts
Assignee: luya_tfz(a)thefinalzone.net
Reporter: tagoh(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
luya_tfz(a)thefinalzone.net
Target Milestone: ---
Classification: Fedora
Description of problem:
Titillium_roman_upright_italic_2_0_OT.zip contains two directory. one is
Titillium_roman_upright_italic_2_0_OT which is specified as a base directory in
the spec file. another one is __MACOSX. the spec file doesn't clean up
__MACOSX, thus, the build stop on extracting like:
+ /usr/lib/rpm/rpmuncompress -x
/var/home/tagoh/rpmbuild/SOURCES/Titillium_roman_upright_italic_2_0_OT.zip
replace __MACOSX/Titillium_roman_upright_italic_2_0_OT/._Titillium-Black.otf?
[y]es, [n]o, [A]ll, [N]one, [r]ename:
Version-Release number of selected component (if applicable):
campivisivi-titillium-fonts-20120913-25.fc37
How reproducible:
always
Steps to Reproduce:
1.download SRPM
2.rpmbuild --rebuild campivisivi-titillium-fonts-20120913-25.fc37.src.rpm
3.try again once the rebuild finished.
Actual results:
the rebuild always fails except first try.
Expected results:
the rebuild should be successfully finished any time.
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=2112732
2 months, 1 week