https://bugzilla.redhat.com/show_bug.cgi?id=1938091
Bug ID: 1938091
Summary: Kasumi-unicode: Check for only hiragana letters in
reading column fails as user can input non-hiragana
characters in it.
Product: Fedora
Version: 34
Status: NEW
Component: kasumi
Keywords: i18n
Assignee: tagoh(a)redhat.com
Reporter: bbarve(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1762901
--> https://bugzilla.redhat.com/attachment.cgi?id=1762901&action=edit
kasumi unicode non-hiragana letters
Description of problem: In the kasumi-unicode dict, there is a message which
pops-up if user tries to input non-hiragana characters like kanji or katakana.
However this check is not consistent as user can input other non-hiragana input
like English words, letters, numbers etc. This can be done using any mode in
Anthy like hiragana or direct input. Attaching screenshot for reference.
Version-Release number of selected component (if applicable):
Fedora 34
kasumi-unicode-2.5.33.fc34
How reproducible:
always
Steps to Reproduce:
1. Run /usr/bin/kasumi-unicode from terminal
2. click on add
3. add a jpn word in any script under first column i.e. words
4. hit tab and enter to input in the second column i.e. reading
5. In hiragana mode, input 'k' and hit enter
6. click on save.
Actual results:
user is ablke to input non-hiragana input in reading column
Expected results:
The check for non-hiragana input should be consistent.
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=2016613
--- Comment #47 from Jiri Konecny <jkonecny(a)redhat.com> ---
Copying this message from ticket
https://pagure.io/fedora-qa/blocker-review/issue/577 -- seems to be missed
there.
Hi everyone,
I guess we are in the situation that we have to decide about the solution here.
There are two ways to "solve" this which I'm able to find out.
One is to disconnect keyboard control between Live system and Anaconda. So
Anaconda will handle after installation keyboard configuration and Live will
handle current Live.
- this will solve the current bug issue
- could be confusing to people
- it's not really a fix
Another solution is to leave it as it is. I know it's broken but AFAIK there is
no fix in the Anaconda project to solve this. In general there is no fix I
could create which would not be additional work for Live maintainers.
- not a solution
- not really sure if this is worse or better solution than the above
I honestly don't mind about any of these solution but I would like to know your
input if you think it's better to fix this or not. My personal preference is to
go with the second option, it's less disruptive for people who use English for
the installation.
Also if we are going with the first fix. Do we want to use this for all the
Wayland systems or just KDE where it's currently the biggest issue?
P.S.: I think there could be a better solution in general but that is more
about F38+ it would be a bigger change on more than just Anaconda but could
improve the overall experience for Live maintainers and Anaconda. The solution
is in discussion with all the required parties and I have ACK from them that
it's doable and they are fine to do that. I'll contact Fedora community but
this is not a correct place to do that.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2016613
https://bugzilla.redhat.com/show_bug.cgi?id=683325
Cristian Ciupitu <cristian.ciupitu(a)yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|34 |35
--- Comment #34 from Cristian Ciupitu <cristian.ciupitu(a)yahoo.com> ---
It's still happening with pidgin-2.14.6-2.fc35.x86_64
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=683325
https://bugzilla.redhat.com/show_bug.cgi?id=2035841
Bug ID: 2035841
Summary: Please build nkf for EPEL 9
Product: Fedora EPEL
Version: epel9
Hardware: All
OS: Linux
Status: NEW
Component: nkf
Severity: medium
Assignee: tagoh(a)redhat.com
Reporter: redhat-bugzilla(a)linuxnetz.de
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Please build nkf for EPEL 9, because it's a dependency of the w3m package.
Version-Release number of selected component (if applicable):
nkf-2.1.4-22.fc35
Actual results:
No nkf in EPEL 9.
Expected results:
nkf-2.1.4-22.el9 - or better ;-)
Additional info:
Please let me know if you are not interested in maintaining the package on EPEL
9 branch.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2035841
https://bugzilla.redhat.com/show_bug.cgi?id=2016613
--- Comment #45 from Lukas Ruzicka <lruzicka(a)redhat.com> ---
Ok, I also have another, yet not a beautiful solution.
What if Anaconda provided an overlay graphical keyboard (or perhaps a character
table) that would allow to choose special characters using users' mice?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2016613
https://bugzilla.redhat.com/show_bug.cgi?id=2016613
--- Comment #42 from Michael Catanzaro <mcatanza(a)redhat.com> ---
I think GNOME could live with this as long as anaconda gets the default
keyboard layout to use from localed instead of just assuming en_US. That would
allow us to pass along the correct keyboard layout from gnome-initial-setup to
anaconda via localed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2016613
https://bugzilla.redhat.com/show_bug.cgi?id=2016613
--- Comment #41 from Adam Williamson <awilliam(a)redhat.com> ---
I was kinda afraid we'd end up here, yeah.
I agree this may be the way to go, unfortunately. The fancy dbus solution would
be nice but it's committing someone to a reasonable degree of work, and
requires buy-in from at least KDE and GNOME...
If we're going with the 'just not allowed' approach, I'd like the warning to be
a bit more high profile, I think. And maybe have it reinforced on spoke close,
like we do for other cases where we really want you to confirm something before
you leave a spoke...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2016613