On Thu, Jan 06, 2022 at 03:11:41AM +0000, Yifei Zhan wrote: > On 21/12/31 12:16PM, Omar Polo wrote: > > Yifei Zhan <openbsd@zhan.science> writes: > > > > > You can edit that file to enable and setup IME plugins you want, but > > > it's more common to use fcitx5-config-qt for that. A typical workflow > > > would look like this: > > > > > > 1. install fcitx5 fcitx5-gtk fcitx5-qt fcitx5-config-qt fcitx5-$IME_Plugin > > > which $IME_Plugin to use depends on which language you want to type. > > > (e.g. fcitx5-anthy for Japanese) > > > > i suppose all of these fcitx5-* packages are yet to be submitted ^^" > > They are on the way now :) > > Some IME plugins require more work than others as they depend on newer > version of IME libs we don't have yet, but I'm working on a few updates > now, should not take too long. At the moment I have attached fcitx5 > fcitx5-gtk fcitx5-qt fcitx5-config-qt, lightly tested and working here > on my amd64 box. > > fcitx5-anthy is also just around the corner, it can be used as a good > test case. > > By the way, fcitx support for gnome-terminal is currently broken because > gnome-terminal is built with gtk4 and uses GNOME's own IME integration > system, I will dig into it later, but any other terminal emulator should > be usable. konsole(qt)/sakura(gtk) both are fine. > > > > > > 2. setup session environment variables in ~/.xsession, and start fcitx > > > when logging in > > > > > > export XMODIFIERS=@im=fcitx > > > export GTK_IM_MODULE=fcitx > > > export QT_IM_MODULE=fcitx > > > /usr/local/bin/fcitx5 > > > > Oh, I should have guessed that, it's similar to fcitx4. Maybe we can > > adopt the same wording as in fcitx' DESCR? > > (and similar for the gtk and qt module) > > > > I prefer to maintain a single README file documenting all the setup > instructions, just like meta/gnome/pkg/README-main. I think doing so > makes it easier to keep instructions up to date. (I plan to write that > once I got more IME plugins working) > > > > Since fcitx5 is meant to be the successor for fcitx4 which is no > > longer developed, it may make sense to replace fcitx4 with 5 instead > > of keeping both in the port tree? I'm not using either, so I'm > > probably missing something here. > > I agree, if Kevin is ok with that we can drop fcitx4 once fcitx5 and its > plugins are tested and imported.
Hmm, fcitx5 doesn't work on x11/dwm. Launching fcitx5 with "fcitx5 -d" (gives no error), Ctrl+Space shortcut to change input method doesn't do anything on applications (firefox, konsole, etc). I have the following installed: fcitx5-5.0.11 flexible input method framework fcitx5-chewing-5.0.8 chewing wrapper for fcitx5 fcitx5-gtk-5.0.10 GTK IM module for fcitx5 fcitx5-m17n-5.0.7 m17n wrapper for fcitx5 fcitx5-qt-5.0.9 Qt library and IM module for fcitx5 xcb-imdkit-1.0.3 implementation of xim protocol in xcb
