Fcitx
Fcitx (Flexible Input Method Framework) is a lightweight input method framework aimed at providing environment independent language support for Linux. It supports a lot of different languages and also provides many useful non-CJK features.
Installation
Input method engines
Fcitx provides built-in input methods for Chinese Pinyin and table-based input (for example Wubi).
Depending on the language you wish to type, other input method engines are available:
Chinese
- fcitx-sunpinyin, based on sunpinyin. It strikes a good balance between speed and accuracy.
- fcitx-libpinyin, based on libpinyin. It has a better algorithm than fcitx-sunpinyin.
- fcitx-rime, based on schemas from the Rime IME project.
- fcitx-googlepinyin, the Google pinyin IME for Android.
- fcitx-sogoupinyinAUR, Sogou input method for linux—Supports, Jianpin, fuzzy sound, cloud input, English input, mixed skin.Official website
- fcitx-cloudpinyin uses internet sources to provide input candidates. The selected cloud result will be added to local dictionary.
- fcitx-chewing is a popular Zhuyin input engine for Traditional Chinese based on libchewing.
- fcitx-table-extra adds Cangjie, Zhengma, Boshiamy support.
Japanese
- fcitx-anthy, a popular Japanese input engine. However, it is not actively developed anymore.
- fcitx-mozc, based on Mozc, the Open Source Edition of Google Japanese Input.
- fcitx-kkc, a new Japanese Kana Kanji input engine, based on libkkc.
Other languages
- fcitx-hangul, for typing Korean hangul, based on libhangul.
- fcitx-unikey, for typing Vietnamese characters.
- fcitx-sayura, for typing Sinhalese.
- fcitx-m17n, for other languages provided by M17n.
Input method module
To obtain a better experience in Gtk+ and Qt programs, install the fcitx-gtk2, fcitx-gtk3, fcitx-qt4 and fcitx-qt5 input method modules as your need, or the fcitx-im group to install all of them.
Applications below do not use Gtk+/Qt input module:
- Applications use Tk, motif or xlib
- Emacs, Opera, OpenOffice, LibreOffice, Skype, Wine, Java, Xterm, urxvt, WPS
Others
- fcitx-ui-light, light UI for fcitx.
- fcitx-fbterm, for Fbterm support.
- fcitx-table-extra, extra table.
- fcitx-table-other, tables for Latex, Emoji and others.
- kcm-fcitx, KDE configuration module for fcitx.
Others packages (including git version) are also available in the AUR. All components of fcitx will requires fcitx to restart after install.
Usage
Desktop Environment
If you are using any XDG compatible desktop environment such as KDE, GNOME, Xfce, LXDE, after you relogin, the autostart should work out of box. If not, open your favorite terminal, type:
$ fcitx
To see if fcitx is working correctly, open an application such as leafpad and press CTRL+Space (the default shortcut for switching input method) to invoke FCITX and input some words.
If Fcitx failed to start with your desktop automatically or if you want to change the parameters to start fcitx, please use tools provided by your desktop environment to configure xdg auto start or edit the fcitx-autostart.desktop
file in your ~/.config/autostart/
directory (copy it from /etc/xdg/autostart/
if it doesn't exist yet).
If your desktop environment does not support xdg auto start, please add the following command to your startup script (after the environment variables are set up properly).
$ fcitx
When other input methods with xim support is also running, Fcitx may fail to start due to xim error. Please make sure no other input method is running before you start Fcitx.
Non desktop environment
Add the following lines to your desktop start up script files to register the input method modules and support xim programs.
- Use
.xprofile
if you are using KDM, GDM, LightDM or SDDM. - Use
.xinitrc
if you are using startx or Slim.
export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx export XMODIFIERS=@im=fcitx
- Re-login to make these environment changes effective.
Xim
Optionally, you can use xim in your GTK+ and/or Qt programs without installing the above modules in which case you need to change the corresponding lines above as following:
export GTK_IM_MODULE=xim export QT_IM_MODULE=xim
Configuration
Configuration tools
Fcitx provides GUI configure tools. You can install either kcm-fcitx(KDE), fcitx-configtool (based on gtk3). Run fcitx-config-gtk3 after fcitx-configtool is installed. Unset Only Show Current Language if you want to enable a input method of a different language.
Note that Fcitx does not supports manual configuration while its GUI is active.
In order to enable spell checking, press ctrl + alt + h when fcitx is on a input method provides by fcitx-keyboard. Then that's it, you can type long word, to see whether it works.
Change default UI
Fcitx support kimpanel protocal to provide bettter desktop intergation.
Gnome-Shell
You can install kimpanel from extensions.gnome.org or gnome-shell-extension-kimpanel-gitAUR package in AUR, which provides a similar user experience as ibus-gjs.
KDE
kdeplasma-addons-applets-kimpanel[broken link: package not found] - a plasmoids providing native feeling under kde. Simply add kimpanel to plasma and fcitx will automatically switch to it without extra configuration.
kimpanel UI
kimtoy could use skin from Sogou and fcitx.
Extend pinyin dictionary
Pinyin dictionary is located at ~/.config/fcitx/pinyin
. File pybase.mb
is for single characters and file pyphrase.mb
defines pinyin phrases. To extend them, put your file into /usr/share/fcitx/pinyin
and restart fcitx.
Tips and tricks
Clipboard Access
You can use fcitx to input text in you clipboard (as well as a short clipboard history and primary selection). The default trigger key is Control-;. You can change the trigger key as well as other options in the Clipboard addon configure page.
NOTE: This is NOT a clipboard manager, it doesn't hold the selection or change its content as what a clipboard manager is supposed to do. It can only be used to input from the clipboard.
Troubleshooting
Diagnose the problem
If you have problems using fcitx, eg. Ctrl+Space fail to work in all applications, then the first thing you should try is to diagnose using fcitx-diagnose
.
The output of fcitx-diagnose
should contain the clue to most common problems.
Providing the output of it will also help when you consult other people(eg. in IRC or forums).
Emacs
If your LC_CTYPE
is English, you may not be able to use input method in emacs due to an old emacs' bug. You can set your LC_CTYPE
to something else such as zh_CN.UTF-8
before emacs starts to get rid of this problem.
Note that the corresponding locale should be enabled on your your system. Uncomment the corresponding line, for example, zh_CN.UTF-8
, in /etc/locale.gen
and run locale-gen
.
The default fontset will use `-*-*-*-r-normal--14-*-*-*-*-*-*-*' as basefont(in src/xfns.c), if you do not have one matched(like terminus、or 75dpi things, you can look the output of `xlsfonts'), XIM can not be activated.
Emacs Daemon
If you are using emacs daemon/client mode, LC_CTYPE
should be set when starting the daemon. For example, by running emacs daemon with LC_CTYPE=zh_CN.UTF-8 emacs --daemon
.
If starting emacs daemon from systemd, set Environment in the unit file like this:
Environment="LC_CTYPE=zh_CN.UTF-8" "XMODIFIERS=@im=fcitx"
(XMODIFIERS may need to be set explicitly here as systemd doesn't load .xprofile. Check the initial-environment
variable in emacs to verify both variables are set correctly.)
Input method module
Ctrl+Space fail to work in GTK programs
This problem sometimes happens especially when locale is set as English. Please make sure your GTK_IM_MODULE is set correctly.
See also FAQ
If you have set the *_IM_MODULE environment variables to fcitx but cannot activate fcitx, please check if you have installed the corresponding input method modules.
Some programs can only use xim, if you are using these programs, please make sure your XMODIFIERS is set properly and be aware of the problems you may have. These programs includes: all programs that are not using gtk or qt (e.g. programs that use tk, motif, or xlib directly), emacs, opera, openoffice, libreoffice, skype
If you cannot enable fcitx in gnome-terminal under gnome and the above way doesn't work, try:
$ gsettings set org.gnome.settings-daemon.plugins.xsettings overrides "{'Gtk/IMModule':<'fcitx'>}"
Buildin Chinese Pinyin Default NOT ACTIVE
If your locale is en_US.UTF-8
, fcitx did NOT enable the buildin Chinese Pinyin input method by default. There is only fcitx-keyboard-us
input method enabled. You can get a notice by fcitx-diagnose
command like this:
## Input Methods: 1. Found 1 enabled input methods: fcitx-keyboard-us 2. Default input methods: **You only have one input method enabled, please add a keyboard input method as the first one and your main input method as the second one.**
Then you should add Pinyin
or Shuangpin
input method to actived input methods by the GUI configure tool.
fcitx and KDE
For some reasons, KDE doesn't handle keyboard layouts properly. For example, if you switch from US (English) to LT (Lithuanian), all numbers on the keyboard should produce Lithuanian letters, but they still produce numbers as the output. This can be fixed by these steps:
- Install required packages mentioned here.
- Turn off
fcitx
if it's running in the background. - Disable stuff related to KDE:
- At System settings --> Input devices --> Layouts (tab) make sure that "Configure layouts" is unchecked.
- At System settings --> Input devices --> Advanced (tab) make sure that "Configure keyboard options" is unchecked.
- Open terminal and type
fcitx
to start it. You can close terminal -fcitx
will still be running in the background. - Set up your needed layouts (Right click on the system tray icon, then "Configure").
- Right click on the system tray icon, then "Exit"
At this point you should have working layouts, native KDE layouts switch icon should appear and you can switch them by mouse scroll or click on it.
Input method switched to English unintentionally
For instance, in XMind, when the user presses Enter to create a node, input method is always switched to English, and have to be switched back to Chinese manually.
To fix this issue, open the fcitx GUI configuration tool (provided by fcitx-configtool), switch to tab "Global Config", in dropdown menu "Share State Among Window", select "PerProgram" or "All".