FAQ - Revision history

Weng Xuetian at 01:28, 22 November 2024

2024-11-22T01:28:43Z

← Older revision		Revision as of 01:28, 22 November 2024
Line 202:		Line 202:
	* Opera, enable on the spot for [[Special:MyLanguage/XIM\|XIM]].		* Opera, enable on the spot for [[Special:MyLanguage/XIM\|XIM]].
	* Firefox, enable preedit.		* Firefox, enable preedit.
			* Java program that uses swing or awt. There is a historical OpenJDK bug. But jetbrains patches there own JDK with the fix. https://youtrack.jetbrains.com/issue/JBR-2460/Wrong-position-of-input-window-and-no-input-preview-with-fcitx-and-ubuntu-13.04 You may want to try jetbrains jdk instead. Confirmed that 21.0.5b631.19 can work properly.

	== Colored Emoji ==		== Colored Emoji ==

Weng Xuetian at 16:13, 6 January 2024

2024-01-06T16:13:20Z

← Older revision		Revision as of 16:13, 6 January 2024
Line 202:		Line 202:
	* Opera, enable on the spot for [[Special:MyLanguage/XIM\|XIM]].		* Opera, enable on the spot for [[Special:MyLanguage/XIM\|XIM]].
	* Firefox, enable preedit.		* Firefox, enable preedit.

			== Colored Emoji ==
			The issue itself is usually not relevant to Fcitx itself, but the library used to render text. When using X11, or using native wayland input method protocol, the text is rendered by pango, which is the same as Gtk. You can also check if Gtk application is fine with such emoji character. A common issue is that, the embedded bitmap font is disabled by fontconfig, which is required to display color emoji.

			As for Wayland that uses "Client side input panel" feature, the text is rendered natively by the toolkit. If it is a Qt application, which you may hit some Qt bugs: https://bugreports.qt.io/browse/QTBUG-80434 , https://bugreports.qt.io/browse/QTBUG-85744 , which does not have a resolution yet.

	<!--T:14-->		<!--T:14-->

Weng Xuetian: Marked this version for translation

2023-02-26T04:53:39Z

Marked this version for translation

← Older revision		Revision as of 04:53, 26 February 2023
Line 16:		Line 16:
	Check the application you want to type into.		Check the application you want to type into.

	<!--T:84-->		=== Wayland === <!--T:84-->
	~~=== Wayland ===~~

			<!--T:89-->
	See [[Special:MyLanguage/Using Fcitx 5 on Wayland\|Using Fcitx 5 on Wayland]].		See [[Special:MyLanguage/Using Fcitx 5 on Wayland\|Using Fcitx 5 on Wayland]].

Weng Xuetian at 04:53, 26 February 2023

2023-02-26T04:53:23Z

← Older revision		Revision as of 04:53, 26 February 2023
Line 13:		Line 13:
	== When use Ctrl + Space, Fcitx cannot be triggered on == <!--T:3-->		== When use Ctrl + Space, Fcitx cannot be triggered on == <!--T:3-->

	~~=== Wayland ===~~ <!--T:84-->		<!--T:37-->
			Check the application you want to type into.

			<!--T:84-->
			=== Wayland ===

	See [[Special:MyLanguage/Using Fcitx 5 on Wayland\|Using Fcitx 5 on Wayland]].		See [[Special:MyLanguage/Using Fcitx 5 on Wayland\|Using Fcitx 5 on Wayland]].

	~~<!--T:37-->~~
	~~Check the application you want to type.~~

	=== Only one specific app has problem? === <!--T:61-->		=== Only one specific app has problem? === <!--T:61-->

Weng Xuetian: Marked this version for translation

2023-02-26T04:50:24Z

Marked this version for translation

← Older revision		Revision as of 04:50, 26 February 2023
Line 13:		Line 13:
	== When use Ctrl + Space, Fcitx cannot be triggered on == <!--T:3-->		== When use Ctrl + Space, Fcitx cannot be triggered on == <!--T:3-->

	=== Wayland ===		=== Wayland === <!--T:84-->
	See [[Special:MyLanguage/Using Fcitx 5 on Wayland\|Using Fcitx 5 on Wayland]].		See [[Special:MyLanguage/Using Fcitx 5 on Wayland\|Using Fcitx 5 on Wayland]].

Line 44:		Line 44:
	Some distribution enables Qt6 for telegram desktop. Just make sure you have the Qt6 im module (For fcitx4, it's fcitx-qt6 on archlinux).		Some distribution enables Qt6 for telegram desktop. Just make sure you have the Qt6 im module (For fcitx4, it's fcitx-qt6 on archlinux).

	=== Chromium or any other chromium based browser (E.g. Microsoft Edge) ===		=== Chromium or any other chromium based browser (E.g. Microsoft Edge) === <!--T:85-->
	For Chromium running under X11, if you are using startx to start your graphical user interface, you may hit [https://gitlab.freedesktop.org/xorg/app/xinit/-/issues/9 an issue] in startx that unset the DBUS_SESSION_BUS_ADDRESS, which prevent chromium based browser from using dbus correctly. To mitigate this, you may:		For Chromium running under X11, if you are using startx to start your graphical user interface, you may hit [https://gitlab.freedesktop.org/xorg/app/xinit/-/issues/9 an issue] in startx that unset the DBUS_SESSION_BUS_ADDRESS, which prevent chromium based browser from using dbus correctly. To mitigate this, you may:

			<!--T:86-->
	1. either export DBUS_SESSION_BUS_ADDRESS by yourself in your ~/.xinitrc (or simply change to use ~/.xsession if you are using debian based system).		1. either export DBUS_SESSION_BUS_ADDRESS by yourself in your ~/.xinitrc (or simply change to use ~/.xsession if you are using debian based system).

			<!--T:87-->
	2. or use a display manager like sddm, gdm, lightdm instead of startx.		2. or use a display manager like sddm, gdm, lightdm instead of startx.

			<!--T:88-->
	For Chromium that runs natively under wayland, the only native wayland input method protocol it supports is text-input-v1, which is only supported by weston. Alternatively, it can also use Gtk4's im module, you can use following flag (---enable-features=UseOzonePlatform --ozone-platform=wayland --gtk-version=4) to make it use Gtk im module, but it doesn't fully work in terms of popup window position unless you are using kimpanel + GNOME.		For Chromium that runs natively under wayland, the only native wayland input method protocol it supports is text-input-v1, which is only supported by weston. Alternatively, it can also use Gtk4's im module, you can use following flag (---enable-features=UseOzonePlatform --ozone-platform=wayland --gtk-version=4) to make it use Gtk im module, but it doesn't fully work in terms of popup window position unless you are using kimpanel + GNOME.

Weng Xuetian: /* Chromium or any other chromium based browser (E.g. Microsoft Edge) */

2023-02-26T04:49:55Z

Chromium or any other chromium based browser (E.g. Microsoft Edge)

← Older revision		Revision as of 04:49, 26 February 2023
Line 51:		Line 51:
	2. or use a display manager like sddm, gdm, lightdm instead of startx.		2. or use a display manager like sddm, gdm, lightdm instead of startx.

	For Chromium that runs natively under wayland, the only native wayland input method protocol it supports is text-input-v1, which is only supported by weston. Alternatively, it can also use Gtk4's im module, you can use following flag (---enable-features=UseOzonePlatform --ozone-platform=wayland --~~gtk_version~~=4) to make it use Gtk im module, but it doesn't fully work in terms of popup window position unless you are using kimpanel + GNOME.		For Chromium that runs natively under wayland, the only native wayland input method protocol it supports is text-input-v1, which is only supported by weston. Alternatively, it can also use Gtk4's im module, you can use following flag (---enable-features=UseOzonePlatform --ozone-platform=wayland --gtk-version=4) to make it use Gtk im module, but it doesn't fully work in terms of popup window position unless you are using kimpanel + GNOME.

	=== Is it Java, Xterm, wine, or some other non-Gtk/Qt Application? === <!--T:39-->		=== Is it Java, Xterm, wine, or some other non-Gtk/Qt Application? === <!--T:39-->

Weng Xuetian at 04:49, 26 February 2023

2023-02-26T04:49:22Z

← Older revision		Revision as of 04:49, 26 February 2023
Line 12:		Line 12:

	== When use Ctrl + Space, Fcitx cannot be triggered on == <!--T:3-->		== When use Ctrl + Space, Fcitx cannot be triggered on == <!--T:3-->

			=== Wayland ===
			See [[Special:MyLanguage/Using Fcitx 5 on Wayland\|Using Fcitx 5 on Wayland]].

	<!--T:37-->		<!--T:37-->

Weng Xuetian at 22:50, 14 December 2022

2022-12-14T22:50:46Z

← Older revision		Revision as of 22:50, 14 December 2022
Line 40:		Line 40:
	==== Telegram desktop ==== <!--T:77-->		==== Telegram desktop ==== <!--T:77-->
	Some distribution enables Qt6 for telegram desktop. Just make sure you have the Qt6 im module (For fcitx4, it's fcitx-qt6 on archlinux).		Some distribution enables Qt6 for telegram desktop. Just make sure you have the Qt6 im module (For fcitx4, it's fcitx-qt6 on archlinux).

			=== Chromium or any other chromium based browser (E.g. Microsoft Edge) ===
			For Chromium running under X11, if you are using startx to start your graphical user interface, you may hit [https://gitlab.freedesktop.org/xorg/app/xinit/-/issues/9 an issue] in startx that unset the DBUS_SESSION_BUS_ADDRESS, which prevent chromium based browser from using dbus correctly. To mitigate this, you may:

			1. either export DBUS_SESSION_BUS_ADDRESS by yourself in your ~/.xinitrc (or simply change to use ~/.xsession if you are using debian based system).

			2. or use a display manager like sddm, gdm, lightdm instead of startx.

			For Chromium that runs natively under wayland, the only native wayland input method protocol it supports is text-input-v1, which is only supported by weston. Alternatively, it can also use Gtk4's im module, you can use following flag (---enable-features=UseOzonePlatform --ozone-platform=wayland --gtk_version=4) to make it use Gtk im module, but it doesn't fully work in terms of popup window position unless you are using kimpanel + GNOME.

	=== Is it Java, Xterm, wine, or some other non-Gtk/Qt Application? === <!--T:39-->		=== Is it Java, Xterm, wine, or some other non-Gtk/Qt Application? === <!--T:39-->

Weng Xuetian: Marked this version for translation

2022-12-13T19:25:23Z

Marked this version for translation

← Older revision		Revision as of 19:25, 13 December 2022
Line 38:		Line 38:
	* Above solution can also applies if you want use XIM, but still we highly recommend you to use im module. See Also [[Special:MyLanguage/Input method related environment variables\|Input method related environment variables]].		* Above solution can also applies if you want use XIM, but still we highly recommend you to use im module. See Also [[Special:MyLanguage/Input method related environment variables\|Input method related environment variables]].

	==== Telegram desktop ====		==== Telegram desktop ==== <!--T:77-->
	Some distribution enables Qt6 for telegram desktop. Just make sure you have the Qt6 im module (For fcitx4, it's fcitx-qt6 on archlinux).		Some distribution enables Qt6 for telegram desktop. Just make sure you have the Qt6 im module (For fcitx4, it's fcitx-qt6 on archlinux).

Line 68:		Line 68:
	Emacs will use `----r-normal--<some font size>-------' as basefont(in src/xfns.c), if you do not have one matched, the code for input method won't run. Install some font package may help (For required fonts xorg-fonts-misc might be the right package but you can also try other xorg-fonts-* package.).		Emacs will use `----r-normal--<some font size>-------' as basefont(in src/xfns.c), if you do not have one matched, the code for input method won't run. Install some font package may help (For required fonts xorg-fonts-misc might be the right package but you can also try other xorg-fonts-* package.).

	=== Non Gtk/Qt Wayland Application (Alacritty, kitty, etc) ===		=== Non Gtk/Qt Wayland Application (Alacritty, kitty, etc) === <!--T:78-->
	It is possible that the application you use does not support input method at all, because they need to have relevant code to implement it. Even if they do, it is highly possible that compositor does not have the support for input method. Only GNOME Shell and KWin has full text-input-v3 support. As of 2022/05/07, sway still does not have full zwp_input_method_v2 support to support input surface. For KWin, you will need Plasma 5.24+ and Fcitx 5.0.14+ and make KWin to start Fcitx 5. You will need to go to Virtual Keyboard KCM and select Fcitx 5 in the KCM.		It is possible that the application you use does not support input method at all, because they need to have relevant code to implement it. Even if they do, it is highly possible that compositor does not have the support for input method. Only GNOME Shell and KWin has full text-input-v3 support. As of 2022/05/07, sway still does not have full zwp_input_method_v2 support to support input surface. For KWin, you will need Plasma 5.24+ and Fcitx 5.0.14+ and make KWin to start Fcitx 5. You will need to go to Virtual Keyboard KCM and select Fcitx 5 in the KCM.

	== Candidate window is blinking under wayland with Fcitx 5 ==		== Candidate window is blinking under wayland with Fcitx 5 == <!--T:79-->
	This is mainly due to the whole poor state of wayland input method. The existing wayland input method protocol is not widely supported by compositor. Even though fcitx 5 support those protocols, the poor support in application and compositor make them not usable. Not to mention certain design flaw within the protocol.		This is mainly due to the whole poor state of wayland input method. The existing wayland input method protocol is not widely supported by compositor. Even though fcitx 5 support those protocols, the poor support in application and compositor make them not usable. Not to mention certain design flaw within the protocol.

			<!--T:80-->
	In order to make input method some what usable with '''CURRENTLY''' available and widely adopted techniques, Fcitx 5 implements a mechanism called "Client Side Input Panel", which basically asks client application to render the input window. This is done through dbus and IM Module for Gtk/Qt. The implementation requires using a underlying wayland protocol xdg_popup to show the window. Unfortunately, only new version of xdg_popup protocol supports '''moving''' a visible popup window, and this part is '''NOT''' implemented in Gtk3 and Qt5. What makes it even worse is that Gtk3 and Qt5 both comes to their end of life, which means it is not possible to get this new protocol support in Gtk3/Qt5. The issue is that input method requires to display a window that resizes and moves extremely frequently. To mitigate this issue, Fcitx 5 IM Module implement a hack that when we need to move the window, it will hide the window first and then show the window. Unfortunately, this would cause certain-level of blinking. It might looks bad in certain hardware and compositor combination.		In order to make input method some what usable with '''CURRENTLY''' available and widely adopted techniques, Fcitx 5 implements a mechanism called "Client Side Input Panel", which basically asks client application to render the input window. This is done through dbus and IM Module for Gtk/Qt. The implementation requires using a underlying wayland protocol xdg_popup to show the window. Unfortunately, only new version of xdg_popup protocol supports '''moving''' a visible popup window, and this part is '''NOT''' implemented in Gtk3 and Qt5. What makes it even worse is that Gtk3 and Qt5 both comes to their end of life, which means it is not possible to get this new protocol support in Gtk3/Qt5. The issue is that input method requires to display a window that resizes and moves extremely frequently. To mitigate this issue, Fcitx 5 IM Module implement a hack that when we need to move the window, it will hide the window first and then show the window. Unfortunately, this would cause certain-level of blinking. It might looks bad in certain hardware and compositor combination.

			<!--T:81-->
	Here is some possible workaround for this.		Here is some possible workaround for this.

			<!--T:82-->
	1. Use kimpanel under GNOME shell, which will make the candidate window to be rendered with a totally different mechanism, which won't cause any blinking.		1. Use kimpanel under GNOME shell, which will make the candidate window to be rendered with a totally different mechanism, which won't cause any blinking.

			<!--T:83-->
	2. Disable Fade-in and Fade-Out effect under KWin. KWin seems to tolerate such blink much better than certain compositor.		2. Disable Fade-in and Fade-Out effect under KWin. KWin seems to tolerate such blink much better than certain compositor.

Weng Xuetian at 04:30, 8 May 2022

2022-05-08T04:30:10Z

← Older revision		Revision as of 04:30, 8 May 2022
Line 67:		Line 67:
	<!--T:70-->		<!--T:70-->
	Emacs will use `----r-normal--<some font size>-------' as basefont(in src/xfns.c), if you do not have one matched, the code for input method won't run. Install some font package may help (For required fonts xorg-fonts-misc might be the right package but you can also try other xorg-fonts-* package.).		Emacs will use `----r-normal--<some font size>-------' as basefont(in src/xfns.c), if you do not have one matched, the code for input method won't run. Install some font package may help (For required fonts xorg-fonts-misc might be the right package but you can also try other xorg-fonts-* package.).

			=== Non Gtk/Qt Wayland Application (Alacritty, kitty, etc) ===
			It is possible that the application you use does not support input method at all, because they need to have relevant code to implement it. Even if they do, it is highly possible that compositor does not have the support for input method. Only GNOME Shell and KWin has full text-input-v3 support. As of 2022/05/07, sway still does not have full zwp_input_method_v2 support to support input surface. For KWin, you will need Plasma 5.24+ and Fcitx 5.0.14+ and make KWin to start Fcitx 5. You will need to go to Virtual Keyboard KCM and select Fcitx 5 in the KCM.

	== Candidate window is blinking under wayland with Fcitx 5 ==		== Candidate window is blinking under wayland with Fcitx 5 ==