Personally I don't think gyp would cause a lot trouble and the main
problem would be the dependency to framework libraries. Would it be
possible to split the package into two sources or something like that so
we are able build only ibus/fcitx support from a source that's OK to
MIR? I don't think
Personally I don't think gyp would cause a lot trouble and the main
problem would be the dependency to framework libraries. Would it be
possible to split the package into two sources or something like that so
we are able build only ibus/fcitx support from a source that's OK to
MIR? I don't think
@Aron,
I'm not sure about the future including Desktop Next or convergence,
however I believe it's still worthy to have Mozc as default for the time
being. The engine itself is well maintained by Google team as
Mozc/Google Japanese Input(It's like a Chromium/Chrome relation) in
upstream, and
@aron, yes, it is true that Mozc conversion engine is the *best* for Japanese
input.
I always use Mozc instead of Anthy.
Mozc is default conversion engine on Ubuntu Japanese Remix which is our team is
released.
Anthy is stopped to develop for a long time.
But I think it is hard to pass MIR
@ikuya, I have a question when revisiting this bug, that is how do you
evaluate the possibility of using mozc engine as default, rather than
anthy? I'm not a user of either because I don't type in Japanese, but
there's quite a few hints that show mozc is much more advanced than the
aged anthy.
--
** Summary changed:
- [FFe] Install Fcitx for Japanese users
+ Install Fcitx for Japanese users
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439006
Title:
Install Fcitx for Japanese users
To
