On Sat, May 12, 2012 at 11:49 PM, Fuminobu TAKEYAMA <ftake@geeko.jp> wrote:
please help me translate the introduction and options into Japanese, and send them to me. I'll modify the form then.
btw, please help me add some sentence in Japanese to encourage use write the input method he's now using and would like to use. because in my options, there're only one Japanese method, mozc( I really have little knowledge of Japanese IM)
- Why "IM" and "IM engine" are mixed?
- There are a lot of unneeded sentences make it more simple
any feedback or suggestion to him is appreciated.(eg, which input method backend is the most famous and successful in Japan, anthy? skk? wnn? or else?)
Bug reports written in Japanese are acceptable?
Well yes. I don't really mind non-English language bug report.
# If fcitx supports canna and separated key settings for IM-on/off, # I'll consider to use fcitx. Note that this is just for me :)
and Takashi didn't want mozc to be included as default IM for jp locale. because it's close developed and does not accept any patch. if one day it fails, japanese users will hate us because they don't know the details.
My suggestion is you should write documents about fcitx. Some Japanese community members are googling but they cannot find how it is.
but to tell the truth, famous bugs are still there, like input in Firefox/Chromium, and etc.
users already have bad impression on it. once they leave, it's harder to call them back than newbies.
Could you show me URLs to bugzilla of Novell or other distributions?
in my survey, there're Taiwan users who are using ibus, but vote for gcin/hime.
How many users? I heard he would not use gcin since it is too old. I don't know fcitx-chewing is OK for him.
fcitx-chewing is developed by a Taiwan developer. And some of Taiwan user are using it, AFAIK there is no much problem about it. And fcitx-libpinyin will provide better experience than chewing, though usage is not exact same with chewing. (All based on bopomofo, like pinyin on Chinese mainland)
Fuminobu TAKEYAMA
(12/05/11 17:09), Marguerite Su wrote:
Hi, last night I asked coolo about how to replace input methods in ISOs. he said all I have to do is to make proposal here and cc-ed to related parts like maintianers of those input methods and users interested in.
Here're the names I found from OBS. they're package maintainers. below are their packages and locales.
Me myself: fcitx, hime. zh_CN hillwood: fcitx zh_CN swyear: fcitx, ibus, gcin zh_TW tiwai: mozc, scim jp ftake: mozc jp
and if everyone feel affected or involved in this issue, please feel free to join.
(because those input methods also support other languages besides CJK, although such support is minor.)
and Here're the packages involved:
scim/ibus: they're the Chinese input methods in the old days. fcitx/gcin/hime: they're the Chinese input methods in modern
Linux.
mozc: it's popular IM in Japan.
of course they're both for Linux, and both open source works.
and the situation is, when I freshly installed openSUSE, the first thing I do is uninstall those old-time input methods and install new ones. so I wonder if this situation is common, and if it is common, why not replace them by default instead of leaving works to our users?
so I made a survey:
https://docs.google.com/a/marguerite.su/spreadsheet/viewform?formkey=dDdoMmU...
and posted on G+, forums. the temporary result I've got is this situation is common in Chinese Community.
(tiwai or ftake, can you please translate to Japanese and spread it out to Japanese Community?)
(since we do not have active Korean developers here, so no way to hear from them. so only C and J here.)
and my proposal is:
- drop scim/ibus from DVD/CD. (they're really old and react slow to bugs and have famous bugs)
- add fcitx/gcin/mozc in. (hime is just another fork of gcin. it's another issue, it has a small user database)
so guys what do you think?
Marguerite
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org