Arch Linux User Repository

https://gitlab.manjaro.org/packages/extra/manjaro-asian-input-support/

In the latest version there still remains problems for both CN and JP input as I use. The place of the input would not be the place of cursor and as you do fcitx5-diagnose in konsole you would find it still lacks the env var for QT in KDE w/ wayland. Like before staying in the version 2021.09 e17561 fixes it for me. My environment is as below.

KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
Kernel Version: 6.13.2-arch1-1 (64-bit)
Graphics Platform: Wayland

https://gitlab.manjaro.org/packages/extra/manjaro-asian-input-support/

@MatrixC7

Thanks for the report.
I have reverted only to the fcitx environment of KDE, as some environments did not allow Asian language input when environment variables were present.
In KDE(Wayland), only fcitx has the environment variable set.
Please use KWin VirtualKeyboard for both ibus and fcitx5 in KDE.

I installed and tried Google Chrome(AUR,deb package conversion).

GNOME(Wayland) No environment variables required.

KDE(Wayland) Some environment variables are required. Firefox, Kwrite, Konsole, etc. cannot start IME and input if GTK_IM_MODULE or QT_IM_MODULE is set. Therefore, only the other environment variables have been modified to be set. This modification was made because environment variable settings can be an obstacle.

If you are still having problems, please let me know your specific environment.

Please consider adding the following options to the wayland operation.
By adding this option, even when running Google Chrome in the AUR package with Wayland,
IME activation was performed and Japanese input was possible. For your reference.

google-chrome --enable-wayland-ime --ozone-platform-hint=auto --wayland-text-input-v3=enable

echo --enable-wayland-ime --ozone-platform-hint=auto --wayland-text-input-v3=enable|xargs -n1| tee -a $HOME/.config/chrome-flags.conf

If this does not bring up the IME, go to chrome://flags, set the flag ozone-platform-hint to auto, enable wayland-text-input-v3, and restart chrome.

references: (Japanese) https://zenn.dev/ikuya/articles/39b03d8485471f https://zenn.dev/compass/articles/e1f4c88e78b721

"Setting environment variables is not necessary in a Wayland environment(GNOME or KDE)."

No, setting env vars is still necessary as Wayland e.g. KDE would not have fcitx5 available in some applications like Google Chrome installed via AUR. Returning to e175612aa06ad5bec46cb3fd85c800d7a162c477 to simply set vars could solve the problem.

Nice! Keep up the excellent work!

@willvar
I have turned off the echo message output.

Ah, I see the echo statement comes from the upstream source, maybe we could make some patches like this:

@@ -2,7 +2,6 @@
 # https://wiki.archlinux.org/index.php/Fcitx5

 function set_im_env {
-    echo "Setting environment variables for Input Method."
     im=fcitx
     export GTK_IM_MODULE=$im
     export QT_IM_MODULE=$im

Hi! I noticed that some shell scripts installed in /etc/profile.d/ echoes the message like:

echo "Setting environment variables for Input Method."

While the message is useful during setup, I would prefer not to see it every time I open a terminal session like konsole/gnome terminal. Could you kindly modify the PKGBUILD so that the echo command only runs when needed (e.g., during installation)?