|
|
楼主 |
发表于 2003-5-8 11:08:23
|
显示全部楼层
6. Troubleshooting for configuration:
If you followed everthing in Step 4 but can't get fcitx work, please
read the following configuration guide. If Step 4 works fine, you can
skip this.
The applications communicate with XIM through the environment variable
XMODIFIERS. Take bash as an example, the way to set XMODIFIER is:
export XMODIFIERS="@im=YOUR_XIM_NAME"
The ``YOUR_XIM_NAME'' above it the name XIM program registered as in the
operating system. Applications will look for the XIM server corresponds
this name. Therefore, even if there are several XIM programs running
simultaneously, an application can only use one XIM at a time. Sometime
you will find that although XIM is already invoked, the application
can't use it, then this is mostly due to a wrong setup of XMODIFIERS
variable. For example, you may have modified some scripts, so that this
variable have a different value when X starts than when system boots to
command line.
The default name fcitx register as is, well, fcitx. However, if
XMODIFIERS is already set when fcitx starts, fcitx can register an
suitable name according to it. So, for newly installed Mandrake 8.x/9
and Red Hat 7.x/8, the easiest way is to do
cd /usr/bin
ln -sf fcitx chinput
then reboot, and everything should be okay.
If this doesn't work, you need to manually set the environment variable.
You can do this in ~/.bashrc, just add line export
XMODIFIERS="@im=fcitx"
export XIM=fcitx
export XIM_PROGRAM=fcitx
then relogin and start X. If fcitx is not invoked automatically, you
need to run
fcitx &
in an X console. |
|
IP卡
狗仔卡
发表于 2003-5-7 18:23:46
显身卡
发表于 2003-5-8 16:41:15
