As I have stated many times in my blog, the most serious problem of input method in linux world is not input method, but actually the application. That’s why I maintain a page of applications with buggy input method support.

http://fcitx-im.org/wiki/Hall_of_Shame_for_Linux_IME_Support

Actually I haven’t worked hard on reporting bugs to application themselves. But now I decide to help them fix their problems in the future, with more concrete description what theirs bug is.

Recently I tried to fix an input method bug in kate (though a rarely used feature, so don’t worry).

Though I cannot fix code I’m not familiar with (no I really can’t, there are huge monsters like firefox or libreoffice, or emacs, even gtk will look like a small kitty comparing with them), but more accurate description of bug report may help upstream application more.

There is another problem, that I cannot use all applications (for example I only use firefox, so I’m not be able to notice chromium bugs), but normal user can hardly describe a problem accurately, so if anyone found any reproducible problem (yes, this is very important, otherwise there might be no bug or just because of some careless operation) may related to input method, feel free to send it to fcitx@googlegroups.com and I will take a look at it.

Here comes a new feature for fcitx in next release.

(Though video is in Chinese, it’s easy to understand. I’m trying to make three different windows to using different input methods.)

The basic idea is, user can choose a different input method based on window. Generally, fcitx can have two global input method, for Active and Inactive state.

Now we can have a different “local” input method for each input context, and it’s easy to choose.

You can talk with different friends in different languages at the same time, for example, you want to talk with your American, German, Chinese friends at the same time, just change the message window, and no need to worry about to switch between different input method.

Before those NIH guys harm the world.

Thanks @doublechou’s first shot.

http://lists.opensuse.org/opensuse-factory/2012-05/msg00169.html

fcitx 4.2.3
1. Lua extension support, same interface with Googlepinyin.
Lua 扩展支持，采用Googlepinyin的接口，支持整合类扩展和命令类扩展，暂时不支持转换器。（需要编译时开启）
2. super can be used in hotkey again
Super(win) 可以再次被用于快捷键中
3. fixes Trad-Simp native engine in chttrans.
修复原生的繁转简支持。
4. Update fcitx-pinyin algorithm
更新fcitx-pinyin的拼音切分
5. txt2mb and mb2txt support new English format
txt2mb和mb2txt支持的英文格式的码表
6. Fix a crash when enable share status.
修复在设置为共享状态时可能导致的崩溃
7. Add surrounding text support.
增加获得周围文本的支持。
8. Commit input when unfocus.
失去焦点时提交输入
9. Classic UI improvement, including trayicon, menu.
经典界面改进。托盘图标居中并且不会被放大。

fcitx-fbterm 0.1.4
kill the fcitx and dbus-daemon launched by the script
在退出时杀死由脚本启动的fcitx和dbus-daemon。

fcitx-sunpinyin 0.3.6
option for memory strength, enable fuzzy segement by default
增加记忆强度选项。

fcitx-keyboard 0.1.3
1. add existing keyboard layout on first start up
在首次启动时加入当前已经配置的键盘布局
2. try to set fcitx “first input method as inactive state” when install
将fcitx默认设置为第一个输入法作为非激活状态。
3. restore origin keyboard layout on exit.
在退出时恢复键盘布局。

fcitx-chewing 0.1.2
1. fix space key
修复空格键的处理
2. fix issue 553
修复 issue 553

kcm-fcitx 0.3.3
1. add super support.
增加super(win)键的设置支持
2. workaround a potential freeze bug
绕过一个潜在导致界面冻结的错误。

fcitx-configtool 0.4.3
lower gtk2 version library request compatible to RHEL/CentOS 6.
降低gtk2版的库要求支持，可以满足在RHEL/CentOS 6上的编译依赖

fcitx-m17n 0.1.2
add surrounding text support.
增加获得周围文本的支持。

fcitx-hangul 0.1.1
add surrounding text support.
增加获得周围文本的支持。

fcitx-table-extra 0.3.0
add more table from ibus-table-chinese.
增加更多在ibus-table-chinese中的码表

fcitx-table-other 0.1.0
Fork of ibus-table-others.
ibus-table-others的fork。

fcitx-unikey 0.1.0
unikey support for fcitx
fcitx的unikey支持（越南语）

kimpanel-for-gnome-shell
Menu support, and move it top of other window.
插件已经上传到 https://extensions.gnome.org/extension/261/kimpanel/ ，目前的最新版相比之前增加了菜单支持，并且显示时不会再被某些窗口遮挡。