Category Archives: fcitx development

Gaps between Wayland and Fcitx (or all Input methods).

Though some people have no problem (or, only few problems) about using fcitx (to be more specifically version 4) with wayland, but the truth is there are still lots of problems left to be addressed. The truth is, wayland is … Continue reading

Posted in fcitx development | Tagged , , , | 2 Comments

A new pinyin input method that might be slightly better than sunpinyin

What do I mean when I say “slightly better”? First of all, thanks to sunpinyin’s open-gram, I can use its data for free. So, on the pinyin side, libime IS using the exact same data from sunpinyin. So what’s the … Continue reading

Posted in fcitx development | Tagged , | 1 Comment


不要奇怪为什么在这个分类下面。这是一个 fcitx 躺枪的故事。

Posted in fcitx development | Leave a comment

One bad API in sd-bus

I’m using sd-bus to develop the dbus part for fcitx5, because I’d like to seamlessly support kdbus in the future. (Don’t argue with me about bsd or sth else right now, for now I don’t care about that.) But one … Continue reading

Posted in fcitx development, Linux | Tagged , | Leave a comment

On porting Fcitx KCM module to KF5

Porting Fcitx KCM to KF5 is not that easy. It’s not only about porting kcm itself, but also porting missing part of fcitx-qt5 to Qt5 (mostly widgets). The old pkgconfig file is quite messed up, so I decided to experiment … Continue reading

Posted in fcitx development | Tagged | 3 Comments