|
发表于 2004-1-9 10:31:44
|
显示全部楼层
3, Configuration
Application communicates with XIM through environment variable XMODIFIERS, you can setup XMODIFIRES like this (for bash):
export XMODIFIERS="@im=YOUR_XIM_NAME"
Aboved-mentioned YOUR_XIM_NAME is registered name of your XIM application in the system. When start-up, application will find corresponding XIM sever by this variable. So, even if there are several applications running in the system at the same time, one application will take one XIM input method by one time. Sometimes you may account situation, apparently you have started XIM, but application doesn't take it. It's mostly caused by wrong XMODIFIERS configuration. One example will be that you modify XMODIFIERS in diffirent script files, which causes the variable unconsitent when X starts up and after.
By default, fcitx will register fcitx as XIM name, but if XMODIFIERS has been setup when fcitx starts up, fcitx will register its name according system configuration. So, for fresh-installed mandrake and Redhat, the simplest way is to execute the following commands:
cd /usr/bin
ln -sf fcitx chinput
Then restart X. If it can't work out, you need setup your environment manually, usually adding these lines in ~/.bashrc could do the trick:
export XMODIFIERS="@im=fcitx"
export XIM=fcitx
export XIM_PROGRAM=fcitx
Then restart X, logout and login. If fcitx doesn't load automatically, you need execute the following in the commandline:
fcitx
By default, fcitx runs in backgroud, if you don't want it in this way, you can use:
fcitx -nb
4, Configuration file |
|