On Sun, May 13, 2012 at 1:14 AM, Satoru Matsumoto
Marguerite Su wrote:
On Sat, May 12, 2012 at 10:29 PM, Fuminobu TAKEYAMA
wrote: With regard to Mozc, it seems that the developers try to concentrate on IBus like the mozc_renderor feature. They will remove code for SCIM soon. We have to be careful.
I and many Japanese users want to put Mozc into the official repository as an exception for usability.
then it's another story. you can ask them to vote for mozc or any other favorite IM.
anyway, user experience is much more important than patches. since there're already someone develop it, even they don't want our code work, they still welcome our feedback.
Well, I think stability is as important as user experience, in particular for our DEFAULT choice.
yes. but I think even if we don't make patch, things won't be too bad. compared with the everyday fighting with ibus-anthy or others. I didn't provide any patches for openSUSE for almost two years, when I'm a newbie. openSUSE didn't go bad but better. I want to be clear, I will not try to affect to any extent on Japanese's choice of default IM. if you say, oh, we choose mozc, then I'll implement it. but if you say we choose ibus, It's also welcome. just because I never saw so many Japanese users appeared at the same time in openSUSE, just want to learn your preference more though dicussion.
I also recognize the superiority of mozc and use it for my daily work, but still I'm not positive toward making it as the _DEFAULT_ IM for Japanese.
Mozc developers only consist of Google employees, that is, the development of it can be very much affected by Google's will and strategy. It will be a risk, if we will too much depend on such a software. You say 'they still welcome our feedback', but I'd like to add 'as long as the feedback is comply with their strategy'. ;-)
yes, that's what we worried about. and one of the reason why FOSS people are hard to accept it as Real Free Software.
And one of the negative effects caused by their reject of patches from third parties is, that each distribution and project has to prepare and maintain needed patches by themselves, even if the purpose of patches is fixing small problems. An important thing is, that upstream developers don't know and take care of such patches. This may cause some problems every time upstream releases a new version. If there are and will be responsible maintainers for that, there might be no problem. But if there isn't, this will be also a risk.
yes, I said things above because if you choose mozc as default IM. then we're ready to face the situation and conquer the difficulties. but if you're kind to take maintainers into consideration. oh, really appreciated.
Note, I also value users' freedom of choice. If we can provide a good way to choose favorite IM much more easily, that will be nice and may be the solution of this discussion. :-)
then your future might be fcitx, XD. today I just know its developer finished a new feature that you can use different input methods in different window. but the input methods now have to be implementation under fcitx framework. https://www.csslayer.info/wordpress/fcitx-dev/use-multiple-input-method-in-d... if he's crazy enough, maybe one day we can use scim/ibus/fcitx/mozc/gcin/hime at the same time without cold switch.
Best,
-- _/_/ Satoru Matsumoto - openSUSE Member - Japan _/_/ _/_/ Marketing/Weekly News/openFATE Screening Team _/_/ _/_/ mail: helios_reds_at_gmx.net / irc: HeliosReds _/_/ _/_/ http://blog.zaq.ne.jp/opensuse/ _/_/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org