From ArchWiki

Module fcitx5-lua

This module add support for date and time support. That is, when using pinyin input method, type "sj", "rq" can typing current time or date. But English I don't has this feature or not.

Such, type "sj". Give me 21:01

And type "rq". Give me 2021-06-03

-- Dragonwater (talk) 13:01, 3 June 2021 (UTC)Reply[reply]

Move tip "SDL_IM_MODULE=fcitx"

Would there be any harm done if the line "SDL_IM_MODULE=fcitx" under Integration would be added to the codeblock above? It would look something like this:

Tip: See Environment variables for other possible ways to set these variables.

Id prefer having a more experienced user approve of this before i edit anything. --GMON (talk) 16:05, 21 January 2022 (UTC)Reply[reply]

As a potential argument against this, the SDL environment variable appears to be categorically different from the others. It's not recognized as an Fcitx variable by fcitx-diagnose, and doesn't have the same framework-wide support that Qt and GTK have (since apparently this is only supported through vendor modification). Cheers, CodingKoopa (talk) 15:28, 15 March 2022 (UTC)Reply[reply]

fcitx5 or fcitx

I am confused about fcitx and fcitx5. This wiki Page says QT_IM_MODULE=fcitx while wiki says QT_IM_MODULE=fcitx5 Kearney (talk) 09:28, 17 September 2022 (UTC)Reply[reply]

The referenced issue of that section is pretty old and no longer applies (as far as I understand the comments on that issue). `fcitx` should be preferred as stated by fcitx's wiki. `fcitx5` most likely works too. It was used during the development of fcitx5 but later compatibility with the old `fcitx` IM module is completed. Some software packages GUI toolkit with `fcitx` IM module but not the newer `fcitx5` one, so setting to `fcitx5` will not work for them (e.g. mindmaster). An exception to this is Telegram Desktop (their official build, not Arch's build), which bundles both `fcitx` and `fcitx5` IM modules but the `fcitx` one is from fcitx4, thus won't work well on Wayland (which fcitx4 doesn't natively support and the input window will be at a wrong position). Lilydjwg (talk) 11:23, 17 September 2022 (UTC)Reply[reply]
It is a issue with WPS version between and It only support fcitx5, not fcitx. --Fengchao (talk) 02:00, 18 November 2022 (UTC)Reply[reply]

fcitx5 on Wayland no longer requires user to set GTK_IM_MODULE=fcitx (except weston)

"For GTK_IM_MODULE, as for now, the modern Gtk 3/4 application should be able to use text-input-v3 which is supported almost by every compositor, except weston. There are a few different options in terms of setting the value of GTK_IM_MODULE. When it is unset, the Gtk built-in Wayland im module will be used for Gtk3 and Gtk4. While you can also enforce it by doing GTK_IM_MODULE=wayland, remember it will be also picked up by Gtk2. Setting GTK_IM_MODULE=fcitx can still work, and it is necessary if your compositor does not support Wayland input method frontend."

Although setting the environmental variable under wayland(I'm on Hyprland) will work perfectly fine, it'll prompt a warning.

I'm not modifying it since I'm not sure how to explain it clearly in the wiki page, but I'll leave it here for future reference. Pedestrianlove (talk) 14:43, 13 February 2024 (UTC)Reply[reply]