ibus VS mozc

1.5.29-rc2 was tagged on 9 Nov 2023 [1] and in did not contain "N_("CJK Unified Ideographs Extension I")," in src/ibusunicodegen.h [2].

Commit 228f0a77b2047ade54e132bab69c0c03f0f41aae from 28 Feb 2023 introduced this change instead. It's the same person who tagged 1.5.29-rc2 and committed 228f0a77b2047ade54e132bab69c0c03f0f41aae which is typically an indication the maintainer tar'd their checked out git folder and accidentally included changes not get committed.

[1] https://github.com/ibus/ibus/releases/tag/1.5.29-rc2

[2] https://github.com/ibus/ibus/blob/0ad8e77bd36545974ad8acd0a5...

[2] https://github.com/ibus/ibus/commit/228f0a77b2047ade54e132ba...

On https://github.com/ibus/ibus we can see gtk+ are probably only need for ibus-setup. I would like help to be sure i not miss any step.

I also know input methods work great in Ubuntu (Gnome Wayland) because Gnome supports ibus.

But the article is specifically about incompatibility of input methods among different DEs: Gnome, KDE, wlroots-based environments such as Sway and Hyprland.

After many years, ibus still doesn’t work with wlroots: https://github.com/ibus/ibus/issues/2182

The list of recommended IMEs on Sway are all WIP: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway#...

Most people use fcitx5 with Sway because fcitx5 and Sway both support input method unstable v2. But the article explains that v2 is still not universally supported among wayland DEs, and that’s why it’s problematic.

Have no idea what the daemon does practically, here is the GitHub page.

The F38 beta is currently affected by two (mostly gaming-related) issues that you should be aware of: - https://gitlab.gnome.org/GNOME/mutter/-/issues/2678 -> a lot of SDL-based games have their fullscreen mode broken. The issue is bisected. - https://github.com/ibus/ibus/issues/2480 -> Keyboard input sometimes gets stuck. Issue has already been identified and we're waiting for an ibus release.

Also, to add to what u/Pizza-Driver said, it seems that ibus is not yet interoperable with the protocol used by Wayland display servers based on wlroots.

I meant ctrl+., but it looks like ibus recently changed their emoji input shortcut back to super+., so the gtk emoji picker should be available via ctrl+. again without requiring changes: https://github.com/ibus/ibus/commit/1520c39d0d6036da725fcecd932883be3f3d3575

Looks like it was changed here: https://github.com/ibus/ibus/commit/1520c39d0d6036da725fcecd932883be3f3d3575

I think Ubuntu is shipping an earlier version of it that predates the commit that I believe might have introduced the bug. Since you're compiling from the AUR, anyway, maybe you can try patching it yourself and change EscapeXmlValue(engine.symbol()) back to engine.symbol().

It's worth noting mozc (the most popular open source japanese input method) has its own emacs input method: mozc.el.

(define-public fcitx5-mozc-ut ;; (let ((commit "d0d8a87c1ef19b7bd1d2c040e4ef38951b07fbd0"))) (package (name "fcitx5-mozc-ut") (version "2.26.4520.102") (source (origin (method git-fetch) (uri (git-reference (url "https://github.com/fcitx/mozc") (commit "59c4b009a1fd642f7b6070356b9ddc73c30fd99b"))) (sha256 (base32 "0xzjfrn0m8mc6k8vrggrf50x0ssbb9yq9c5qnval8gk8v78rpyl5")))) (build-system python-build-system) (arguments `(#:use-setuptools? #f #:tests? #f #:phases (modify-phases %standard-phases (add-after 'unpack 'symlink (lambda* (#:key inputs #:allow-other-keys) (let ((gyp (assoc-ref inputs "python-gyp"))) (rmdir "src/third_party/gyp/") (symlink gyp "src/third_party/gyp")))) (replace 'configure (lambda* (#:key inputs ouputs #:allow-other-keys) (let ((gyp (assoc-ref inputs "python-gyp"))) ;; (chdir "src") (add-installed-pythonpath inputs outputs) (setenv (string-append "GYP_DEFINES=" "\"" "document_dir=" (assoc-ref ouputs "outs") "/share/doc/mozc" "use_libzinnia=1" "use_libprotobuf=1" "use_libabseil=1" "\"") (invoke "python" "build_mozc.py" "gyp" (string-append "--gypdir=" gyp "/bin") (string-append "--server_dir=" (assoc-ref ouputs "outs") "/lib/mozc") "--target_platform=Linux"))))) (replace 'build (lambda* (#:key outputs #:allow-other-keys) (add-installed-pythonpath inputs outputs) (invoke "python" "build_mozc.py" "build" "-c" "Release" "server/server.gyp:mozc_server" "gui/gui.gyp:mozc_tool" "unix/fcitx5/fcitx5.gyp:fcitx5-mozc"))) (delete 'check) (replace 'install (lambda* (#:key outputs #:allow-other-keys) (add-installed-pythonpath inputs outputs) (setenv (string-append "PREFIX=" (assoc-ref outputs "out"))) (setenv "_bldtype=Release") (invoke "scripts/install_server") (invoke "install" "-d" (string-append (assoc-ref outputs "out") "/share/licenses/fcitx5-mozc")))) ))) (inputs `(("python-gyp" ,python-gyp) ("gtk2" ,gtk+-2) ("zinnia" ,zinnia))) (propagated-inputs `(("six" ,python-six))) (native-inputs `(("python" ,python) ("qtbase" ,qtbase-5) ("ninja" ,ninja) ("fcitx5" ,fcitx5) ("pkg-config" ,pkg-config))) (synopsis "A Japanese Input Method Editor designed for multi-platform") (description "Mozc is a Japanese Input Method Editor (IME) designed for multi-platform such as Android OS, Apple OS X, Chromium OS, GNU/Linux and Microsoft Windows. This OpenSource project originates from Google Japanese Input.") (home-page "https://github.com/google/mozc") (license bsd-3)))

This bug looks like fixed with this commit https://github.com/google/mozc/commit/9ba59b64d53365c1fe93c1c245b4ec3e35bdadf0