[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.
6 days, 6 hours
[Fedora-i18n-bugs] [Bug 1938251] New: update_preedit_text_with_mode(..., .., ..., IBus.PreeditFocusMode.COMMIT) doesn’t work in Gnome Wayland (works fine in Gnome Xorg)
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1938251
Bug ID: 1938251
Summary: update_preedit_text_with_mode(..., .., ...,
IBus.PreeditFocusMode.COMMIT) doesn’t work in Gnome
Wayland (works fine in Gnome Xorg)
Product: Fedora
Version: 34
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
I installed Fedora-Workstation-Live-x86_64-34-20210308.n.0.iso into qemu.
Add the ibus-typing-booster input method in the Gnome control center and
also add the “Vietnamese (telex (m17n))” input method from ibus-m17n.
Both input methods use
update_preedit_text_with_mode(..., .., ..., IBus.PreeditFocusMode.COMMIT)
and this problem can be reproduced with either of them.
Open a gedit and a gnome-terminal.
Select ibus-typing-booster in the Gnome panel and type “test”.
The word “test” is underlined, indicating that it is in preedit and not yet
committed to gedit.
Now click on gnome-terminal to change the focus to gnome-terminal.
The string “test” vanishes from gedit. It should *not* vanish, it should
be committed i.e. the underline under “test” should vanish and the string
“test” should be in gedit.
Same problem with the Vietnamese (telex (m17n)) input method.
Select it in the Gnome panel.
Type “a” into gedit. The “a” is underlined because it is in preedit.
Click on gnome-terminal to change the focus to gnome-terminal.
The “a” vanishes. Here as well the “a” should be commited to gedit, i.e.
the underline should disappear and the “a” should remain in gedit.
--
You are receiving this mail because:
You are on the CC list for the bug.
2 weeks
[Fedora-i18n-bugs] [Bug 1937235] New: [abrt] ibus-hangul: hangul_ic_select_keyboard(): ibus-engine-hangul killed by SIGSEGV
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1937235
Bug ID: 1937235
Summary: [abrt] ibus-hangul: hangul_ic_select_keyboard():
ibus-engine-hangul killed by SIGSEGV
Product: Fedora
Version: 34
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:2c789cb882f05d089b3d896c3bf215104523de34;VAR
IANT_ID=workstation;
Component: ibus-hangul
Assignee: pwu(a)redhat.com
Reporter: mfabian(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, pwu(a)redhat.com,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
ibus-hangul-1.5.4-4.fc34
Additional info:
reporter: libreport-2.14.0
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service
cmdline: /usr/libexec/ibus-engine-hangul --ibus
crash_function: hangul_ic_select_keyboard
executable: /usr/libexec/ibus-engine-hangul
journald_cursor:
s=aeb2461fa27a41febb2b69e0c1f19a49;i=2a21e;b=02ae636d7bd94d8399fe1a589a2cc54d;m=de67d05db;t=5bd2a055e55b4;x=f89bc2f41f604a4d
kernel: 5.11.3-300.fc34.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (2 frames)
#0 hangul_ic_select_keyboard at
/usr/src/debug/libhangul-0.1.0-23.fc34.x86_64/hangul/hangulinputcontext.c:1626
#1 settings_changed at
/usr/src/debug/ibus-hangul-1.5.4-4.fc34.x86_64/src/engine.c:1941
--
You are receiving this mail because:
You are on the CC list for the bug.
3 weeks, 3 days
[Fedora-i18n-bugs] [Bug 1790554] New: Keyboard layout of Kana Kanji wont show up
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1790554
Bug ID: 1790554
Summary: Keyboard layout of Kana Kanji wont show up
Product: Fedora
Version: rawhide
Hardware: x86_64
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: sumukher(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:
The keyboard layout for Kana Kanji Japanese doesnt show up
Version-Release number of selected component (if applicable):
Fedora-Rawhide-20200112.n.0
How reproducible:
Everytime
Steps to Reproduce:
1. Install Fedora-Rawhide-20200112.n.0 WS from live boot
2. Open settings and navigate to Region and Language
3. Add Japanese Kana Kanji in the input source
4. Click the icon looking like an eye button which should open the keyboard
layout
Actual results:
Doesn't show up the keyboard layout
Expected results:
The keyboard layout should show up like it shows up for english
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
3 weeks, 3 days
[Bug 1964374] New: stardict scan hotkey doesn't work
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1964374
Bug ID: 1964374
Summary: stardict scan hotkey doesn't work
Product: Fedora
Version: 33
Status: NEW
Component: stardict
Assignee: psatpute(a)redhat.com
Reporter: antmak.pub(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: anish.developer(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org, nav007(a)gmail.com,
petersen(a)redhat.com, psatpute(a)redhat.com,
pwu(a)redhat.com, robinlee.sysu(a)gmail.com,
yanqiyu01(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
The "Use scan hotkey:" option from StarDict's Preferences doesn't work
Version-Release number of selected component (if applicable):
stardict-3.0.6-15.fc33.x86_64
Fedore 33
GNOME @ Wayland session
How reproducible:
Just change the option to any value, it doesn't work.
Steps to Reproduce:
1. Open StarDict
2. Open Preferences, "Scan Selection" tab
3. Enable "Use scan hotkey" option.
4. Values: "<Primary><Alt>x", "<Super>j", "<Primary><Alt>j" don't work - it
can't scan selected words from other windows like Firefox or Gedit
Actual results:
It should scan selected words in other apps and open a translate window
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
3 weeks, 3 days
[Fedora-i18n-bugs] [Bug 1847347] New: gnome-terminal and xfce4-terminal get surrounding text from previous application
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1847347
Bug ID: 1847347
Summary: gnome-terminal and xfce4-terminal get surrounding text
from previous application
Product: Fedora
Version: 32
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
I made the following screenshots and video by testing on Gnome-Xorg, but the
problem occurs on Gnome-Wayland as well.
How to reproduce (see also attached screenshots and video):
- To show what happens with the surrounding text, I first opened the
setup tool of ibus-typing-booster and set the debug level in the
options tab to 3.
When the debug level is high, the auxiliary text above the candidate
list shows what context has been obtained by using surrounding text
(if surrounding text is available, if it is not available like when
using xterm, the context is just remembered from what was typed
last).
- I opened 3 windows: gedit, firefox, and gnome-terminal.
- I focus on gedit and type "a b c d e"
On top of the candidate list one can see: "Context: b c d"
This is because when the letter "e" was typed, ibus-typing-booster
got the surrounding text at the cursor position and parsed the last
3 tokens left of the cursor out of the result. And these
last 3 tokens left of the cursor are "b c d".
- Now I focus on firefox and type "f g h i j"
On top of the candidate list one can see: "Context: g h i"
I.e. the correct context "g h i" to the left of the just typed "j"
(which is still in preedit) has been found using surrounding text.
- Now I focus on gnome-terminal and type "k l m"
On top of the candidate list one can see: "Context h i j"
This comes from the surrounding text left of the cursor in
*firefox*, *not* from gnome-terminal.
Although gnome-terminal reports that surrounding text is supported, i.e.
self.client_capabilities & IBus.Capabilite.SURROUNDING_TEXT
is True (see the code to get the context at:
https://github.com/mike-fabian/ibus-typing-booster/blob/master/engine/hun...
)
gnome-terminal does not really seem to support surrounding text.
The surrounding text comes from the previous client which really supported
surrounding text.
If the previous client was firefox, one still gets the surrounding text from
firefox while typing in gnome-terminal.
Same with gedit, if the previous client before focussing on gnome-terminal
was gedit, one still gets the surrounding text from gedit while typing in
gnome-terminal.
- The same problem occurs when using xfce4-terminal instead of gnome-terminal.
- When using xterm, the problem does *not* occur because when using xterm
self.client_capabilities & IBus.Capabilite.SURROUNDING_TEXT
is False and then the get_context() immediately returns and the context
remembered from the last text typed is used as a fallback.
--
You are receiving this mail because:
You are on the CC list for the bug.
3 weeks, 3 days
[Bug 2015149] New: Candidate lists shown in gnome on-screen keyboard
are not hidden/closed when they should
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2015149
Bug ID: 2015149
Summary: Candidate lists shown in gnome on-screen keyboard are
not hidden/closed when they should
Product: Fedora
Version: 34
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 1834251
--> https://bugzilla.redhat.com/attachment.cgi?id=1834251&action=edit
Video showing the problem
[mfabian@fedora ~]$ cat /etc/fedora-release
Fedora release 35 (Thirty Five)
[mfabian@fedora ~]$ rpm -q ibus
ibus-1.5.25-4.fc35.x86_64
[mfabian@fedora ~]$ rpm -q gnome-shell
gnome-shell-41.0-4.fc35.x86_64
[mfabian@fedora ~]$
Running in qemu-kvm with all current updates.
Gnome Xorg session.
Input methods sometimes show candidate lists and sometimes hide or close them
again.
For example, when a candidate is committed the candidate list usually
disappears.
The candidate list shown on top of the gnome on-screen keyboard should behave
the same way. Always when the “normal” candidate list would disappear, the
candidate list on top of the Gnome on-screen keyboard should disappear as well.
But this is not the case.
See the attached video.
The video shows using these input methods:
- ibus-libpinyin (Chinese (Intelligent Pinyin))
- ibus-kkc (Japanese (Kana Kanji))
- ibus-typing-booster (Other (Typing Booster))
- ibus-anthy (Japanese (Anthy))
*Only* if ibus-anthy is used, the candidate list disappears reliably when the
candidate currently shown in the preedit is commit by clicking on the "Return"
key on the on-screen keyboard.
When using ibus-kkc, the candidate list on top of the on-screen keyboard does
*not* disappear when committing the candidate currently shown in the preedit by
clicking on the Return key.
Same with ibus-libpinyin, when committing the candidate currently shown in the
preedit by clicking on the space bar on the on-screen keyboard, the candidate
list does *not* disappear.
Also the same with ibus-typing-booster, when committing the candidate currently
shown in the preedit by clicking either on the space bar or the return key on
hte on-screen keyboard, the candidate list does *not* disappear.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2015149
1 month, 1 week
[Bug 2013323] New: Cursor position and conversion regioni of
ibus-anthy are invisible in Google Documents (both in firefox and
google-chrome)
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2013323
Bug ID: 2013323
Summary: Cursor position and conversion regioni of ibus-anthy
are invisible in Google Documents (both in firefox and
google-chrome)
Product: Fedora
Version: 34
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 1832255
--> https://bugzilla.redhat.com/attachment.cgi?id=1832255&action=edit
Video showing the wrongly displayed cursor position using ibus-anthy in Google
Documents
I did choose component ibus, although this is likely not an ibus bug but a
problem in google docs, but I wanted to report it somehow, maybe something can
be done to improve this:
Fedora-Workstation-Live-x86_64-35-20210829.n.0.iso installed in qemu-kvm with
all current updates.
firefox-93.0-2.fc35.x86_64
google-chrome-unstable-96.0.4662.6-1.x86_64
ibus-1.5.25-4.fc35.x86_64
ibus-anthy-1.5.13-1.fc35.x86_64
See the attached video.
In the video I type わたしのなまえはやまだです first in gedit to show how it should work.
After typing that hiragana, I type space to start conversion. The current
conversion region is indicated by the cursor position and a purple background
color. When the conversion to kanji is startet, at first the cursor position is
at the left of the preedit and the conversion region is わたしの. I can then move
the conversion region right with arrow-right and see that it moves because the
blue background and the cursor position moves.
Then I do the same in Google Documents (both in firefox and google-chrome, that
makes no difference):
- The cursor position is *always* shown at the right end of the preedit
- The purple background color of the conversion region is not there
One can move the conversion region around using the arrow keys, one just cannot
see where the conversion region currently is the purple background is missing
*and* the cursor position is *always* at the right end of the preedit.
The same problem happens when trying to use ibus-typing-booster with the
"inline completion" option in Google Documents. The color of the inline
completion is missing *and* the cursor position is always at the end of the
preedit, so one cannot see where the inline completion is and whether it has
been accepted or not.
In gedit in wayland, the colors don't work either, but at least the cursor
position is shown correctly. When only the cursor position is shown but no
color, it is not great at least somewhat usable. By carefully watching the
cursor one can still see what is going on. But when the cursor positon is
always at the right of preedit *and* there is no colour, this is completely
unusable.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2013323
1 month, 1 week
[Fedora-i18n-bugs] [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 month, 2 weeks