From ArchWiki
Revision as of 19:46, 20 February 2006 by Aquila deus (talk | contribs)
Jump to: navigation, search

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

About GCIN


Installing GCIN

pacman -S gcin

Installing Other Input Tables


Configure 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.utf8

(the LC_CTYPE locale for gcin and for the applications must match; if LC_CTYPE is not set, LANG is used)


export XMODIFIERS=@im=xcin

gcin use the name "xcin" 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=xcin_zh
export XMODIFIERS=@im=xcin_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.