[Bug 1898319] New: dejavu-lgc-sans-mono-fonts: Misleading summary
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1898319
Bug ID: 1898319
Summary: dejavu-lgc-sans-mono-fonts: Misleading summary
Product: Fedora
Version: 33
Hardware: x86_64
OS: Linux
Status: NEW
Component: dejavu-fonts
Severity: low
Assignee: nicolas.mailhot(a)laposte.net
Reporter: van.de.bugger(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
Description of problem:
Summary of dejavu-lgc-sans-mono-fonts is misleading. It is: "A variable-width
Latin-Greek-Cyrillic mono-space font family". Accordingly to Wikipedia:
> A monospaced font, also called a fixed-pitch, fixed-width, or non-proportional font, is a font whose letters and characters each occupy the same amount of horizontal space. This contrasts with variable-width fonts, where the letters and spacings have different widths.
So, a font is either monospaced or variable-width but not both, these are
mutually exclusive concepts. How dejavu-lgc-sans-mono-fonts can be "a
variable-width mono-space font family"??
Version-Release number of selected component (if applicable):
dejavu-lgc-sans-mono-fonts-2.37-15.fc33
How reproducible:
Always.
Steps to Reproduce:
1. $ dnf info dejavu-lgc-sans-mono-fonts
Actual results:
Summary : A variable-width Latin-Greek-Cyrillic mono-space font family
Expected results:
Summary : A Latin-Greek-Cyrillic mono-space font family
--
You are receiving this mail because:
You are on the CC list for the bug.
11 months
[Bug 2186711] New: "Open Sans" substitute config affects other
languages' default font selection
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2186711
Bug ID: 2186711
Summary: "Open Sans" substitute config affects other languages'
default font selection
Product: Fedora
Version: rawhide
Status: NEW
Component: google-droid-fonts
Assignee: aekoroglu(a)linux.intel.com
Reporter: tagoh(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: aekoroglu(a)linux.intel.com,
fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
nicolas.mailhot(a)laposte.net, oliver(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Having "Open Sans" substitution isn't bad BUT "Droid Sans" family name works as
an alias for all variants of Droid Sans families in current config. since we
have proper priority against language coverage to prioritize latin fonts and
non-latin fonts, this alias escalates a priority of that "other variants" in
Droid Sans families. For example, non-latin fonts are supposed to be managed
between 65 and 69, and 65 is used for default fonts, and
google-droid-sans-fonts take 66 to avoid conflict to other default fonts.
However, by this substitution config, it becomes equivalant to 60 because
open-sans-fonts puts their config at 60.
There are two options to address this:
a) drop "Open Sans" substitution from config. this will stops escalating their
config.
b) stop unifying all "Droid Sans" families. Droid Sans still works as
substitution of "Open Sans" but only take effects for "Droid Sans" family only
then.
Version-Release number of selected component (if applicable):
google-droid-sans-fonts-20200215-14.fc38.noarch
How reproducible:
always
Steps to Reproduce:
1.LANG=ja_JP.UTF-8 fc-match sans:lang=ja
2.
3.
Actual results:
DroidSansJapanese.ttf: "Droid Sans" "Regular"
Expected results:
NotoSansCJK-VF.ttc: "Noto Sans CJK JP" "Regular"
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=2186711
11 months, 1 week
[Bug 2144373] New: reduce the fontconfig priority of Droid fonts
below default CJK fonts
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2144373
Bug ID: 2144373
Summary: reduce the fontconfig priority of Droid fonts below
default CJK fonts
Product: Fedora
Version: 37
Status: NEW
Component: google-droid-fonts
Severity: medium
Assignee: aekoroglu(a)linux.intel.com
Reporter: petersen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: aekoroglu(a)linux.intel.com,
fonts-bugs(a)lists.fedoraproject.org,
nicolas.mailhot(a)laposte.net, oliver(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
These days Droid is considered a general fallback font so it should not
have higher fontconfig priority than other default system fonts,
including in particular google-noto-sans-cjk-ttc-fonts.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. see for example bug 517789
Actual results:
Droid interferes with system fonts priorities
Expected results:
Droid should be a fallback font.
Additional info:
The family unification configuration in the Fedora package
is also involved here, but hopefully lowering the priority
could be sufficient to avoid these issues, otherwise perhaps
the families should be un-unified.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2144373
11 months, 1 week
[Bug 2123720] New: Noto Sans Thai to default for Thai
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2123720
Bug ID: 2123720
Summary: Noto Sans Thai to default for Thai
Product: Fedora
Version: rawhide
Status: NEW
Component: google-noto-fonts
Keywords: FutureFeature
Assignee: tagoh(a)redhat.com
Reporter: tagoh(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, psatpute(a)redhat.com,
pwu(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
As we have changed most languages default to Noto, it may be good to consider
updating Thai to Noto as well.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2123720
11 months, 4 weeks
[Bug 2123722] New: Noto Khmer to default for Khmer
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2123722
Bug ID: 2123722
Summary: Noto Khmer to default for Khmer
Product: Fedora
Version: rawhide
Status: NEW
Component: google-noto-fonts
Keywords: FutureFeature
Assignee: tagoh(a)redhat.com
Reporter: tagoh(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, psatpute(a)redhat.com,
pwu(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
As we have changed most languages default to Noto, it may be good to consider
updating Khmer to Noto as well.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2123722
11 months, 4 weeks
[Bug 1779123] New: Pango no longer supports type1 fonts
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1779123
Bug ID: 1779123
Summary: Pango no longer supports type1 fonts
Product: Fedora
Version: rawhide
Status: NEW
Component: pango
Assignee: pwu(a)redhat.com
Reporter: mjg(a)fedoraproject.org
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,
john.j5live(a)gmail.com, 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:
In pango 1.44, pango dropped support for type1 fonts. Therefore, no application
which uses pango for font loading can use type1 fonts any more.
Version-Release number of selected component (if applicable):
pango-1.44.6-1.fc31.x86_64 (and later)
How reproducible:
always
Steps to Reproduce:
1. Upgrade F31 or rawhide
2. Open any pango-using application
3. Try to use type1 font
Actual results:
No type1 font is usable
Expected results:
Type1 font is usable
Additional info:
bug 1753295 is the same bug for dropped bitmap font support. Over there,
workarounds specific for bitmap fonts (conversion to opentype bitmap fonts) are
discussed. An attempt to discuss type1 there failed.
This bug here is specifically about type1 fonts to discuss ways (or their
absence) to deal with pangos dropped type 1 support.
--
You are receiving this mail because:
You are on the CC list for the bug.
1 year
[Bug 2129399] Postscript standard symbol font is not looked up
correctly
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2129399
--- Comment #32 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on
2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
'version' of '36'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version'
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora Linux 36 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2129399
1 year
[Bug 683325] pidgin freezes for some specific messages and window
size
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=683325
--- Comment #37 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on
2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
'version' of '36'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version'
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora Linux 36 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=683325
1 year
[Bug 2164233] New: FcCacheFini: Assertion `fcCacheChains[i] == NULL'
failed.
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2164233
Bug ID: 2164233
Summary: FcCacheFini: Assertion `fcCacheChains[i] == NULL'
failed.
Product: Fedora
Version: 37
Status: NEW
Component: fontconfig
Assignee: tagoh(a)redhat.com
Reporter: byoungchan.lee(a)gmx.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.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, rstrode(a)redhat.com,
sandmann(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
When I try to run openttd, fontconfig crashes due to an assertion.
https://github.com/freedesktop/fontconfig/blob/2.14.1/src/fccache.c#L808
Version-Release number of selected component (if applicable):
$ rpm -qa | grep fontconfig
fontconfig-2.14.1-2.fc37.x86_64
fontconfig-2.14.1-2.fc37.i686
fontconfig-devel-2.14.1-2.fc37.x86_64
fontconfig-debugsource-2.14.1-2.fc37.x86_64
$ rpm -qa | grep openttd
openttd-opengfx-7.1-3.fc37.noarch
openttd-12.2-4.fc37.x86_64
How reproducible:
Run openttd
Steps to Reproduce:
1.
2.
3.
Actual results:
Crash
Expected results:
Game runs.
Additional info:
I'm not sure why assertions are enabled in fontconfig.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164233
1 year