GNOME Bugzilla – Bug 787664
Set Mozc as default Gnome input method of Japan
Last modified: 2020-11-25 01:46:06 UTC
Currently, Anthy is stopped developing for several years, But Mozc is being used more and more widely in Japan Linux user. Gnome-desktop has default-input-sources.h which are guiding the default input engine in Gnome desktop. So, I want modify this to fit to the popular user habit. Reference mozc on github: https://github.com/google/mozc/commits/master and anthy on osdn: https://osdn.net/projects/anthy/releases/
Created attachment 359777 [details] [review] Modify Japanese input.
I'd like to get more input about this change. Should we switch to mozc by default? I think fedora is using kkc by default already, maybe we should move upstream's default to that instead? Any other options?
Created attachment 359840 [details] [review] Patch to switch to kkc (In reply to Rui Matos from comment #2) > I'd like to get more input about this change. Should we switch to mozc by > default? I think fedora is using kkc by default already, maybe we should > move upstream's default to that instead? Any other options? Hi Rui: The attachment is the patch switch the default Japanese engine to KKC. and, I also glad to hear other people's opinion on this issue. From my point of view, I feel Mozc is more powerful than KKC. :-)
I think mozc is not changed for linux at present. And right. anthy has not been updated for a long time while ibus-anthy has been updated. I'm not sure about kkc but I know we have an employee movement. What I don't prefer mozc is which is based on QT UI and I'm not sure it follows ibus changes.
(In reply to Takao Fujiwara from comment #4) > I think mozc is not changed for linux at present. > And right. anthy has not been updated for a long time while ibus-anthy has > been updated. > I'm not sure about kkc but I know we have an employee movement. > What I don't prefer mozc is which is based on QT UI and I'm not sure it > follows ibus changes. Thanks! Then, What should be the 1st prefer input-engine for Japanese in your mind?
From the user experience perspective, lots of Japanese users have used with Mozc, especially in Debian|Ubuntu|opensuse. They always install Mozc after default installation. From the technical perspective: Yes, there have many works which didn't solve very well, like the integration with gnome stack. But these problems can be resolved if we really care about it. And in my humble opinion, accommodate with the user's habit, Providing an easier desktop is more important.
(In reply to Zhao Qiang from comment #6) > They always install Mozc after default installation. If the default installation does not include mozc, I don't think mozc is the best. Also not sure how many people do. (In reply to Zhao Qiang from comment #5) > Then, What should be the 1st prefer input-engine for Japanese in your mind? I think every input method has pros and cons and not sure what is the primary. But I prefer GTK UI.
(In reply to Takao Fujiwara from comment #7) > (In reply to Zhao Qiang from comment #5) > > Then, What should be the 1st prefer input-engine for Japanese in your mind? > > I think every input method has pros and cons and not sure what is the > primary. > But I prefer GTK UI. Okay, understood now. Then, I think KKC is written in Vala and C and is absolutely Gtk based. Do you agree with KKC? just like what the Fedora does.
(In reply to Zhao Qiang from comment #8) > (In reply to Takao Fujiwara from comment #7) > > (In reply to Zhao Qiang from comment #5) > > Okay, understood now. > Then, I think KKC is written in Vala and C and is absolutely Gtk based. Do > you agree with KKC? just like what the Fedora does. Yes, you have told me that "Not sure what is the primary."(Japanese). But in fact, I mean, Do you have any *concern* on KKC? and also, Does any other people have objection on this? I think we'd better make some decisions at the end.
(In reply to Zhao Qiang from comment #9) > (In reply to Zhao Qiang from comment #8) > > (In reply to Takao Fujiwara from comment #7) > > > (In reply to Zhao Qiang from comment #5) > > > > Okay, understood now. > > Then, I think KKC is written in Vala and C and is absolutely Gtk based. Do > > you agree with KKC? just like what the Fedora does. > > Yes, you have told me that "Not sure what is the primary."(Japanese). > But in fact, I mean, Do you have any *concern* on KKC? > and also, Does any other people have objection on this? > > I think we'd better make some decisions at the end. It's fine with me. However my concern is if ibus-kkc is maintained now.
(In reply to Takao Fujiwara from comment #10) > (In reply to Zhao Qiang from comment #9) > > (In reply to Zhao Qiang from comment #8) > > > (In reply to Takao Fujiwara from comment #7) > > > > (In reply to Zhao Qiang from comment #5) > > > > > It's fine with me. > However my concern is if ibus-kkc is maintained now. ibus-kkc upstream is in https://github.com/ueno/ibus-kkc/commits/master, obviously, it is in maintaining now. On the other hand, I think this decision isn't forever which means never changed. If KKC is stop maintained someday in future, then we can change to other engines which are most favor by Japanese people. And also, I'm volunteered to do the related works. :-)
Hi, Rui: Do we still need to wait for other people's input? I suppose Takao can agree for KKC still in maintaining currently.
Review of attachment 359840 [details] [review]: Please add a link to this bugzilla issue in the commit message (see other commit messages or use git-bz) and a little rational for the change would be nice as well.
Comment on attachment 359777 [details] [review] Modify Japanese input. >From 0aa674d8e1f5eb8d65f0703dca8284bbfb6b1901 Mon Sep 17 00:00:00 2001 >From: zhaoqiang <zhaoqiangx@gmail.com> >Date: Thu, 14 Sep 2017 17:34:51 +0800 >Subject: [PATCH] Switch user's default input engine from anthy to mozc. > >--- > libgnome-desktop/default-input-sources.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >diff --git a/libgnome-desktop/default-input-sources.h b/libgnome-desktop/default-input-sources.h >index b3430828..20d27cdf 100644 >--- a/libgnome-desktop/default-input-sources.h >+++ b/libgnome-desktop/default-input-sources.h >@@ -34,7 +34,7 @@ static DefaultInputSource default_input_sources[] = > { "he_IL", "xkb", "il" }, > { "hi_IN", "ibus", "m17n:hi:inscript" }, > { "it_IT", "xkb", "it" }, >- { "ja_JP", "ibus", "anthy" }, >+ { "ja_JP", "ibus", "Japanese (Mozc)" }, > { "kn_IN", "ibus", "m17n:kn:kgp" }, > { "ko_KR", "ibus", "hangul" }, > { "mai_IN", "ibus", "m17n:mai:inscript" }, >-- >2.13.0 >
(In reply to Rui Matos from comment #13) > Review of attachment 359840 [details] [review] [review]: > > Please add a link to this bugzilla issue in the commit message (see other > commit messages or use git-bz) and a little rational for the change would be > nice as well. Thanks, Rui. I will modify as soon as possible. For today and tomorrow, I will in a trip, So I will update the day after tomorrow. Regards!
Created attachment 360727 [details] [review] change default Japanese input-engine to "KKC"
(In reply to Zhao Qiang from comment #16) > Created attachment 360727 [details] [review] [review] > change default Japanese input-engine to "KKC" Rui: Is it ok for you this time?
Created attachment 361163 [details] [review] Change default Japanese input engine to KKC. Most Japanese people will not use anthy any more. and KKC is user friendly and fully based on GTK.
(In reply to Zhao Qiang from comment #18) > Most Japanese people will not use anthy any more. I don't think so. Many people uses ibus-anthy and it have lots of the features.
(In reply to Takao Fujiwara from comment #19) > (In reply to Zhao Qiang from comment #18) > > Most Japanese people will not use anthy any more. > > I don't think so. Many people uses ibus-anthy and it have lots of the > features. Okay If I rephrase the comment like: "KKC is in a more active developing and it is user-friendly, additionally fully based on GTK." Will you accept it?
(In reply to Zhao Qiang from comment #20) > If I rephrase the comment like: "KKC is in a more active developing and it > is user-friendly, additionally fully based on GTK." > Will you accept it? Yeah, it's fine with me.
Created attachment 361233 [details] [review] Change default Japanese input engine to KKC. KKC is in a more active developing and it is user-friendly, additionally it's fully based on GTK
(In reply to Zhao Qiang 赵强 from comment #22) > Created attachment 361233 [details] [review] [review] > Change default Japanese input engine to KKC. > > KKC is in a more active developing and it is user-friendly, > additionally it's fully based on GTK Rui: Could you please help to re-review this? Thanks!
Review of attachment 361233 [details] [review]: looks good, thanks
Dear maintainers: Could you please review this request? and also so expect to get your opinion.
(In reply to Zhao Qiang 赵强 from comment #25) > Dear maintainers: > > Could you please review this request? and also so expect to get your opinion. It's already been reviewed, it's waiting for you to commit it.
Created attachment 361721 [details] [review] default-input-sources: Change default Japanese engine Change the default Japanese input engine to KKC. KKC is in a more active development and is user-friendly. Finally, it's fully based on GTK.
Attachment 361721 [details] pushed as 9c1aea9 - default-input-sources: Change default Japanese engine
Ubuntu uses ibus-mozc by default for Japanese so please don't assume that Fedora == GNOME.
(In reply to Jeremy Bicha from comment #29) > Ubuntu uses ibus-mozc by default for Japanese so please don't assume that > Fedora == GNOME. Which isn't what the upstream GNOME was using either. If you want/need a particular input source to be the default, please file a new bug and explain why.
Sorry, it was a late drive-by comment replying to the original bug report and comment #2.
I'd think it would be the best way to rebase anthy or develop another IME from a scratch.
(In reply to Jeremy Bicha from comment #29) > Ubuntu uses ibus-mozc by default for Japanese so please don't assume that > Fedora == GNOME. I'm wondering, would it make sense to move this list to GSettings so a distribution can easily override it with their favorite default? Unlike input method frameworks, input methods are more like an application (e.g. Chromium vs Firefox); downstreams should be able to customize the default as per their requirements, IMO.
(In reply to Daiki Ueno from comment #33) > (In reply to Jeremy Bicha from comment #29) > > Ubuntu uses ibus-mozc by default for Japanese so please don't assume that > > Fedora == GNOME. > > I'm wondering, would it make sense to move this list to GSettings so a > distribution can easily override it with their favorite default? Unlike > input method frameworks, input methods are more like an application (e.g. > Chromium vs Firefox); downstreams should be able to customize the default as > per their requirements, IMO. No, because modifying a header file is just as straight forward for distributors. The defaults are not a user preference, they're just defaults. Hopefully downstreams can tell us how their defaults are different from ours and why, so we can change those defaults if warranted. That's not stopping those distributors from setting their own defaults.
(In reply to Jeremy Bicha from comment #29) > Ubuntu uses ibus-mozc by default for Japanese so please don't assume that > Fedora == GNOME. Hi Jeremy: This has been discussed at the beginning: I think Mozc is an excellent input engine, and I found a lot of openSUSE's users also choose Mozc just like Ubuntu community. But sir Takao found that Mozc is mostly based on QT, So it's not a proper choice for gnome user, and one immediate question is Mozc's setup program can't work in purely Gnome desktop. Although Mozc has dropped Qt 4 support recent days, it still needs QT base libraries support. I'm interested in how Ubuntu solve this problem? Because I can't answer this, so the only choice for me is SKK. After all, it's better than the original Anthy.
(In reply to Takao Fujiwara from comment #32) > I'd think it would be the best way to rebase anthy or develop another IME > from a scratch. I will totally support this proposal!
Now I'm thinking to revert this change since kkc has been delayed to move gsettings migrations and etc for many years: https://github.com/ibus/ibus/wiki/GSettingsMigration I got the agreement with the original anthy developers and has been forked it to anthy-unicode: https://github.com/fujiwarat/anthy-unicode