[Fedora-i18n-bugs] [Bug 1813728] New: Square four dot Unicode character has incorrect glyph
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1813728
Bug ID: 1813728
Summary: Square four dot Unicode character has incorrect glyph
Product: Fedora
Version: 31
Hardware: x86_64
OS: Linux
Status: NEW
Component: pango
Severity: low
Assignee: pwu(a)redhat.com
Reporter: guillaumepoiriermorency(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,
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:
The glyph for the Unicode "square four dot" character is incorrect.
Version-Release number of selected component (if applicable):
I think this problem arose when upgrading from Fedora 30 to Fedora 31.
How reproducible:
The simplest way is to start GNOME Characters Map and search for "square four
dot".
--
You are receiving this mail because:
You are on the CC list for the bug.
1 hour, 47 minutes
[Bug 2095164] New: Conversion region of ibus-anthy is invisible in
konsole, kwrite, kate
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2095164
Bug ID: 2095164
Summary: Conversion region of ibus-anthy is invisible in
konsole, kwrite, kate
Product: Fedora
Version: 36
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: mfabian(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
Created attachment 1888253
--> https://bugzilla.redhat.com/attachment.cgi?id=1888253&action=edit
Video showing the the conversion region is visible in some places but
invisible in konsole, kwrite, kate
Using Fedora-Workstation-Live-x86_64-36-1.2.iso installed in qemu-kvm with all
current updates.
kwrite, kate, and konsole, do not show the conversion region when using
ibus-anthy
konsole5-22.04.1-1.fc36.x86_64
kwrite-22.04.1-1.fc36.x86_64
kate-21.12.2-1.fc36.x86_64
It does not matter whether these programs are used in
Plasma(X11), Plasma(Wayland), Gnome(Xorg), Gnome(Wayland), the behaviour is
always the same, the conversion region is never visible.
In konsole the behaviour is even worse because not even the cursor is shown at
the start of the conversion region.
When testing in Plasma(Wayland) or Plasma(X11) and typing with ibus-anthy into
the search field of the KDE control center, the conversion region is coloured
and thus visible. It is also visible when typing into the entry field for a
command which opens with Alt+F2. So there are only some programs in KDE where
it does not work like konsole, kwrite, kate, ... whereas it works in other
places.
See the attached video.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2095164
1 day, 17 hours
[Bug 2171140] New: [abrt] ibus-typing-booster:
on_gsettings_value_changed():
hunspell_table.py:7038:on_gsettings_value_changed:AttributeError:
'TypingBoosterEngine' object has no attribute '_set_get_functions'
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2171140
Bug ID: 2171140
Summary: [abrt] ibus-typing-booster:
on_gsettings_value_changed():
hunspell_table.py:7038:on_gsettings_value_changed:Attr
ibuteError: 'TypingBoosterEngine' object has no
attribute '_set_get_functions'
Product: Fedora
Version: 37
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:55bb325f294216e1e5be0a1ae112085ddc7a8f5d;VAR
IANT_ID=workstation;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: fedora(a)oursique.net
QA Contact: extras-qa(a)fedoraproject.org
CC: anish.developer(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
ibus-typing-booster-2.21.3-1.fc37
Additional info:
reporter: libreport-2.17.4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py
--ibus
crash_function: on_gsettings_value_changed
exception_type: AttributeError
executable: /usr/share/ibus-typing-booster/engine/main.py
interpreter: python3-3.11.1-3.fc37.x86_64
kernel: 6.1.11-200.fc37.x86_64
runlevel: N 5
type: Python3
uid: 1000
Truncated backtrace:
hunspell_table.py:7038:on_gsettings_value_changed:AttributeError:
'TypingBoosterEngine' object has no attribute '_set_get_functions'
Traceback (most recent call last):
File "/usr/share/ibus-typing-booster/engine/hunspell_table.py", line 7038, in
on_gsettings_value_changed
if (key in self._set_get_functions
^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'TypingBoosterEngine' object has no attribute
'_set_get_functions'
Local variables in innermost frame:
self: <hunspell_table.TypingBoosterEngine object at 0x7f19f751a600
(hunspell_table+TypingBoosterEngine at 0x5562b24f1130)>
_settings: <Gio.Settings object at 0x7f19f7317880 (GSettings at
0x5562b1c30a60)>
key: 'dictionary'
value: 'en_US_POSIX,fr,fr_FR'
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2171140
2 days, 16 hours
[Bug 2189797] New: [abrt] ibus-typing-booster:
on_gsettings_value_changed():
hunspell_table.py:7055:on_gsettings_value_changed:AttributeError:
'TypingBoosterEngine' object has no attribute '_set_get_functions'
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2189797
Bug ID: 2189797
Summary: [abrt] ibus-typing-booster:
on_gsettings_value_changed():
hunspell_table.py:7055:on_gsettings_value_changed:Attr
ibuteError: 'TypingBoosterEngine' object has no
attribute '_set_get_functions'
Product: Fedora
Version: 38
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:0957dc1ea8e83c522388380c6fce0209c6f1810f;VAR
IANT_ID=workstation;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: vgerris(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: anish.developer(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
ibus-typing-booster-2.22.3-1.fc38
Additional info:
reporter: libreport-2.17.9
kernel: 6.2.12-300.fc38.x86_64
cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py
--ibus
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
uid: 1000
reason:
hunspell_table.py:7055:on_gsettings_value_changed:AttributeError:
'TypingBoosterEngine' object has no attribute '_set_get_functions'
executable: /usr/share/ibus-typing-booster/engine/main.py
type: Python3
package: ibus-typing-booster-2.22.3-1.fc38
runlevel: N 5
exception_type: AttributeError
crash_function: on_gsettings_value_changed
interpreter: python3-3.11.3-1.fc38.x86_64
Truncated backtrace:
hunspell_table.py:7055:on_gsettings_value_changed:AttributeError:
'TypingBoosterEngine' object has no attribute '_set_get_functions'
Traceback (most recent call last):
File "/usr/share/ibus-typing-booster/engine/hunspell_table.py", line 7055, in
on_gsettings_value_changed
if (key in self._set_get_functions
^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'TypingBoosterEngine' object has no attribute
'_set_get_functions'
Local variables in innermost frame:
self: <hunspell_table.TypingBoosterEngine object at 0x7f2e03a3a680
(hunspell_table+TypingBoosterEngine at 0x55b935a4d770)>
_settings: <Gio.Settings object at 0x7f2e065ef280 (GSettings at
0x55b9353531c0)>
key: 'dictionary'
value: 'en_US_POSIX,en,en_US'
Potential duplicate: bug 2188139
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2189797
3 days, 15 hours
[Bug 2119015] New: fontconfig-devel may require gettext-runtime
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2119015
Bug ID: 2119015
Summary: fontconfig-devel may require gettext-runtime
Product: Fedora
Version: rawhide
Status: NEW
Component: fontconfig
Assignee: tagoh(a)redhat.com
Reporter: suanand(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, rstrode(a)redhat.com,
sandmann(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
In F37 we moved the gettext runtime programs to gettext-runtime.
So assuming if fontconfig-devel does not require any translation
management tools (like msgcat or xgettext) at runtime,
it should be possible for it to only Requires: gettext-runtime
(instead of gettext). The goal here is only to install
gettext-runtime in the Fedora live image(s), etc.
Additional info:
https://fedoraproject.org/wiki/Changes/GettextRuntimeSubpackage
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2119015
3 days, 17 hours
[Bug 2184872] New: User installed Japanese fonts override system
fonts when substituting glyphs
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2184872
Bug ID: 2184872
Summary: User installed Japanese fonts override system fonts
when substituting glyphs
Product: Fedora
Version: 37
Status: NEW
Component: fontconfig
Assignee: tagoh(a)redhat.com
Reporter: bztdlinux(a)gmail.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 installing a Japanese font locally (using gnome font viewer, which
effectively copies to ~/.local/share/fonts/), with the default fontconfig, all
kana in the system uses that font.
However, it only affects certain applications. Firefox (rpm) and Inkscape
(flatpak) is affected, but gwrite is not.
Version-Release number of selected component (if applicable):
fontconfig-2.14.0-3.fc37.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Download the following font:
http://font.sumomo.ne.jp/fontdata-c2157415/k-font.zip
2. Unzip and install by double-clicking the font in nautilus and clicking
install.
3. Restart Firefox or Inkscape and paste "です” in a field with sans-serif or
system-ui font
Actual results:
Text appears with the new font
Expected results:
Text appears with the normal system font
Additional info:
Running pango-view, e.g. the following, works fine and selects a reasonable
font (Droid Sans Japanese):
FC_DEBUG=4 pango-view --font="system-ui" -t です | grep family
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2184872
3 days, 17 hours
[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
4 days, 20 hours