The README does not explain at all, only that it's the next generation. I had no issue with fcitx4, and I don't care that fcitx4 in maintenance mode. Why should I switch?
After trying for a little bit, this is why:
- Better integration with Plasma. The KCM is shipped as part of fcitx5, instead of as a separate package (
kcm-fcitx). It's not integrated as well as ibus does to GNOME though — keyboard layouts and input methods are still configured in different pages. GNOME just merges the two. - You can bind any key to switch to the next input method now. Fcitx 4 only offered four options, none of which use the Super key to avoid conflict with other apps
- There is this new concept of input method groups. I find it pointless in my use case, but maybe some people rely on this. Windows offered something similar: you switch languages with
<S-space>and switch input method within a language withC-space. - It seems like there are more themes available on the AUR, but I haven't wanted to try because
kimpanellooks the best.
Unless something breaks spectacularly, I'm probably not switching again for some time.
Aside: making fcitx.el work for fcitx5
fcitx.el is an Emacs package that automatically disables the input method when entering contexts that only really ever expects English input. For example, it disables the IME when leaving insert state, allowing normal state commands to go through.
It works out of the box for fcitx 4; for fcitx5, this will make it work:
(setq fcitx-use-dbus nil ; fcitx.el doesn't know fcitx5's new dbus interface
;; the command name changed, but the switches and arguments haven't
fcitx-remote-command "fcitx5-remote")
(fcitx-default-setup)