Difference between revisions of "Configure (Other)"

From Fcitx
Jump to navigation Jump to search
m
(Marked this version for translation)
Line 2: Line 2:
 
<translate>
 
<translate>
  
== Setup environment variables ==
+
== Setup environment variables == <!--T:1-->
 
In spite of Ubuntu, Debian, Fedora, OpenSUSE, other distribution don't have utils to help to setup required environment variable.
 
In spite of Ubuntu, Debian, Fedora, OpenSUSE, other distribution don't have utils to help to setup required environment variable.
  
 +
<!--T:2-->
 
Fcitx can use XIM or Fcitx's own DBus protocol to communicate with input program. Since 4.1, Fcitx provides GTK2/3 and Qt4 input method module, in order to provides better experience in those application, it's highly recommended to use im module instead of XIM, in order to avoid unresolvable problem.
 
Fcitx can use XIM or Fcitx's own DBus protocol to communicate with input program. Since 4.1, Fcitx provides GTK2/3 and Qt4 input method module, in order to provides better experience in those application, it's highly recommended to use im module instead of XIM, in order to avoid unresolvable problem.
  
 +
<!--T:3-->
 
There are several places to setup environment variable. It depends on how you start up your Display Server.
 
There are several places to setup environment variable. It depends on how you start up your Display Server.
  
 +
<!--T:4-->
 
Required lines
 
Required lines
  
     export GTK_IM_MODULE=fcitx # or xim
+
     <!--T:5-->
 +
export GTK_IM_MODULE=fcitx # or xim
 
     export QT_IM_MODULE=fcitx # or xim
 
     export QT_IM_MODULE=fcitx # or xim
 
     export XMODIFIERS=@im=fcitx
 
     export XMODIFIERS=@im=fcitx
  
=== Use GDM/KDM/LightDM ===
+
=== Use GDM/KDM/LightDM === <!--T:6-->
 
~/.xprofile is the best choice, since it will only affect X and will not pollute to other console environment. Some other people might like to use ~/.profile (Affect whenever you login), or /etc/profile (Global profile).
 
~/.xprofile is the best choice, since it will only affect X and will not pollute to other console environment. Some other people might like to use ~/.profile (Affect whenever you login), or /etc/profile (Global profile).
  
=== Use Slim/startx ===
+
=== Use Slim/startx === <!--T:7-->
 
In that case, you are using ~/.xinitrc to startup, you also need those lines in your ~/.xinitrc. And depends on you use DBus (im module and kimpanel need it), you might want to add
 
In that case, you are using ~/.xinitrc to startup, you also need those lines in your ~/.xinitrc. And depends on you use DBus (im module and kimpanel need it), you might want to add
  
     eval `dbus-launch --sh-syntax --exit-with-session`
+
     <!--T:8-->
 +
eval `dbus-launch --sh-syntax --exit-with-session`
  
 +
<!--T:9-->
 
At the head, to make sure DBus correctly initialized.
 
At the head, to make sure DBus correctly initialized.
  
=== Other environment ===
+
=== Other environment === <!--T:10-->
 
Maybe you are using vncserver, or something else, you need to figure out your start script, for example, vncserver use ~/.vnc/xstartup. Treat it similar with ~/.xinitrc.
 
Maybe you are using vncserver, or something else, you need to figure out your start script, for example, vncserver use ~/.vnc/xstartup. Treat it similar with ~/.xinitrc.
  
== Autostart ==
+
== Autostart == <!--T:11-->
 
For ~/.xinitrc, you can put fcitx to your ~/.xinitrc. Fcitx will run as daemon by default, so no need to use fcitx & to start it.
 
For ~/.xinitrc, you can put fcitx to your ~/.xinitrc. Fcitx will run as daemon by default, so no need to use fcitx & to start it.
  
 +
<!--T:12-->
 
If you running a [http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html XDG] compatible desktop, for example, Gnome, KDE, LXDE, Xfce, you can run
 
If you running a [http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html XDG] compatible desktop, for example, Gnome, KDE, LXDE, Xfce, you can run
  
     cp /usr/share/applications/fcitx.desktop ~/.config/autostart/fcitx.desktop
+
     <!--T:13-->
 +
cp /usr/share/applications/fcitx.desktop ~/.config/autostart/fcitx.desktop
  
 +
<!--T:14-->
 
To add fcitx to your autostart. You can also use tool provided by your desktop to do the same thing.
 
To add fcitx to your autostart. You can also use tool provided by your desktop to do the same thing.
  
== See also ==
+
== See also == <!--T:15-->
 
[[Input method related environment variables]]
 
[[Input method related environment variables]]
  
 +
<!--T:16-->
 
[[Category:How-to]]
 
[[Category:How-to]]
  
 
</translate>
 
</translate>

Revision as of 09:01, 17 March 2012

Other languages:
English • ‎中文(简体)‎

Setup environment variables

In spite of Ubuntu, Debian, Fedora, OpenSUSE, other distribution don't have utils to help to setup required environment variable.

Fcitx can use XIM or Fcitx's own DBus protocol to communicate with input program. Since 4.1, Fcitx provides GTK2/3 and Qt4 input method module, in order to provides better experience in those application, it's highly recommended to use im module instead of XIM, in order to avoid unresolvable problem.

There are several places to setup environment variable. It depends on how you start up your Display Server.

Required lines

   export GTK_IM_MODULE=fcitx # or xim
   export QT_IM_MODULE=fcitx # or xim
   export XMODIFIERS=@im=fcitx

Use GDM/KDM/LightDM

~/.xprofile is the best choice, since it will only affect X and will not pollute to other console environment. Some other people might like to use ~/.profile (Affect whenever you login), or /etc/profile (Global profile).

Use Slim/startx

In that case, you are using ~/.xinitrc to startup, you also need those lines in your ~/.xinitrc. And depends on you use DBus (im module and kimpanel need it), you might want to add

   eval `dbus-launch --sh-syntax --exit-with-session`

At the head, to make sure DBus correctly initialized.

Other environment

Maybe you are using vncserver, or something else, you need to figure out your start script, for example, vncserver use ~/.vnc/xstartup. Treat it similar with ~/.xinitrc.

Autostart

For ~/.xinitrc, you can put fcitx to your ~/.xinitrc. Fcitx will run as daemon by default, so no need to use fcitx & to start it.

If you running a XDG compatible desktop, for example, Gnome, KDE, LXDE, Xfce, you can run

    cp /usr/share/applications/fcitx.desktop ~/.config/autostart/fcitx.desktop

To add fcitx to your autostart. You can also use tool provided by your desktop to do the same thing.

See also

Input method related environment variables