Difference between revisions of "Gcin"

From ArchWiki
Jump to: navigation, search
(Configure GCIN)
Line 19: Line 19:
  
 
= Configure GCIN =
 
= Configure GCIN =
MISSING
+
== Steps for XFCE with SLiM ==
 +
Add the following lines to ~/.xinitrc before executing your XFCE. If you want all the users of your system to use gcin, place these lines in your /etc/profile.
 +
 
 +
export XMODIFIERS=@im=gcin
 +
export LC_CTYPE=zh_TW.UTF-8
 +
gcin&
 +
 
 +
This is what your .xinitrc file should look like. Note that the "exec startxfce4" line comes '''after''' the lines for GCIN
 +
 
 +
#!/bin/sh
 +
 +
#
 +
# ~/.xinitrc
 +
#
 +
# Executed by startx (run your window manager from here)
 +
#
 +
 +
#GCIN
 +
export XMODIFIERS=@im=gcin
 +
export LC_CTYPE=zh_TW.UTF-8
 +
gcin&
 +
 +
exec startxfce4
  
 
= Use GCIN =
 
= Use GCIN =

Revision as of 08:45, 9 November 2008

Template:I18n links start Template:I18n entry Template:I18n entry Template:I18n links end

Tango-document-new.pngThis article is a stub.Tango-document-new.png

Notes: please use the first argument of the template to provide more detailed indications. (Discuss in Talk:Gcin#)

About GCIN

MISSING

Installing GCIN

pacman -S gcin

Installing Other Input Tables

MISSING

Configure GCIN

Steps for XFCE with SLiM

Add the following lines to ~/.xinitrc before executing your XFCE. If you want all the users of your system to use gcin, place these lines in your /etc/profile.

export XMODIFIERS=@im=gcin
export LC_CTYPE=zh_TW.UTF-8
gcin&

This is what your .xinitrc file should look like. Note that the "exec startxfce4" line comes after the lines for GCIN

#!/bin/sh

#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
#

#GCIN
export XMODIFIERS=@im=gcin
export LC_CTYPE=zh_TW.UTF-8
gcin&

exec startxfce4

Use GCIN

With GNOME/GTK+ 2 applications

gcin provides a gtk input module, thus all gtk2-based applications are directly supported, there is no need to configure anything after installation (it's not XIM, and gcin is automatically started when needed).

With other applications

1.Set environment locale to use UTF-8, for example:

export LC_CTYPE=en_US.UTF-8

(You must set the LC_CTYPE locale even if it's as same as LANG, otherewise gcin may not be activated in non-gtk2 programs that use x input)

2.Set XMODIFIERS:

export XMODIFIERS=@im=gcin

gcin use the name "gcin" by default, and you can change this by the environment variable GCIN_XIM in order to run multiple gcin instances, for example:

export GCIN_XIM=gcin_zh
export XMODIFIERS=@im=gcin_zh

Remember that gtk2 applications start one instance of gcin automatically if it doesn't exist.

3.Start gcin:

gcin &

4.Run your applications! (If gcin is killed when your applications are running, it's likely to cause crash or other problems.)

Additional notes for wine/crossover office

1.If you run wine or crossover office, it's better to use windows 2000 emulation instead of windows 98, and you have to start gcin and wine/cxoffice with at least LC_CTYPE=zh_TW.utf8, otherwise wine wouldn't be able to show chinese correctly.

2.In wine+IE6 with windows 98 emulation, LC_CTYPE isn't enough if you want to input chinese on the web-pages - you have to set either LANG or LC_ALL to zh_TW.utf8, which slows down wine a lot. However, you can always type chinese in the location bar or other places and paste it.