uim OR ibus OR fcitx5 with mozc

[rych]

I'd like to build or adapt a foreign built of the uim input method framework with mozc module for Japanese input and the uim-mozc bridge.

This project is going to be hard I guess, and I don't think anyone can do it for me but if you come across these names please add a comment.
https://wiki.archlinux.org/title/Input_ ... _using_uim

Alternatively, I could instead look at ibus and ibus-mozc. Whichever is more doable and opinions which one would be better are welcome.
https://wiki.archlinux.org/title/Input_ ... using_ibus

Final alternative which looks kind of mainstream is fcitx5 and fcitx5-mozc (fcitx5-mozc-ut with an updated dictionary from Google IME) -- I hesitate to go this path as I had a bad experience over the years with a fcitx module on porteus -- id didn't work, froze and contaminated the system

So, 3 pathways:

1.

Uim is an input method module library supporting various languages, which
become a frontend for Anthy, SKK, Canna, T-Code, TUT-Code,
Pinyin (Chinese input method), Hangul (Korean input method),
IPA (International Phonetic Alphabet), etc.
Most of the functions are implemented with Scheme, so it's very simple
and flexible.
Mozc is a Japanese Input Method Editor (IME) designed for multi-platform
such as Chromium OS, Windows, Mac and Linux.
uim-mozc provides client part of the Mozc input method.

2.

IBus is an Intelligent Input Bus. It is a new input framework for Linux OS.
It provides full featured and user friendly input method user interface.
It also may help developers to develop input method easily.
Mozc is a Japanese Input Method Editor (IME) designed for multi-platform
such as Chromium OS, Windows, Mac and Linux.
ibus-mozc provides client part of the Mozc input method.
This open-source project originates from Google Japanese Input.

https://wiki.archlinux.org/title/IBus
https://wiki.archlinux.org/title/Input_ ... using_ibus

3. fcitx5
https://wiki.archlinux.org/title/Fcitx5
https://wiki.archlinux.org/title/Mozc

[ncmprhnsbl]

the ibus path seems like it could be easier.. in that there's slackware ibus packages (and various input engines, but not mozc) https://slakfinder.org/index.php?start= ... r=#results
this AUR PKGBUILD: https://aur.archlinux.org/cgit/aur.git/ ... =ibus-mozc gives an indication of how to build ibus-mozc
and mozc itself: https://aur.archlinux.org/cgit/aur.git/ ... ILD?h=mozc
and the main build dep for them: bazel is available in slackware: https://slakfinder.org/index.php?act=se ... e=#results
which in turn needs zulu-openjdk11 : https://slakfinder.org/index.php?act=se ... e=#results

but yeah, you never know, messing with ubuntu uim stuff could work out..

[rych]

ncmprhnsbl, how on earth they ended up requiring Java...

I'm now leaning towards fcitx5. Could you give your opinion about the fcitx5 packages in Slackware Current: can't we use them in Slackware-based Porteus 5.0?

[beny]

hi ncmprhnsbl there is a set of slackbuild made by a slackware user this is the tread:
https://www.linuxquestions.org/question ... 175709538/
is a big build for mozc

[ncmprhnsbl]

how on earth they ended up requiring Java...

well, that's just for the build tool, bazel ... not needed for runtime..

I'm now leaning towards fcitx5. Could you give your opinion about the fcitx5 packages in Slackware Current: can't we use them in Slackware-based Porteus 5.0?

depends what they depend on.. might work if the lib linking isn't too "hard"..
if you don't mind a slightly older fcitx (4 series) there's a ready made fcitx-mozc : https://slakfinder.org/index.php?act=se ... e=#results

[neko]

Please refer to Japanese locale modules for Porteus (Post by neko #59353)

Thanks.