[Pkg-ime-devel] SCIM: README.Debian updated
Osamu Aoki
osamu@debian.org
Fri, 3 Dec 2004 19:55:35 +0100
Hi,
On Fri, Dec 03, 2004 at 03:48:54PM +0900, Yooseong Yang wrote:
> On Sun, Nov 28, 2004 at 04:58:00PM +0100, Osamu Aoki wrote:
> > Hi,
> >
> > I have updated README.Debian.
...
> > SCIM can be automatically started during the X start up. This
> > configuration can be easily done by the helper package m17n-env. All
> > you have to do is to install m17n-env package and then to run
> > set-m17n-env command from the root and your user shell account while
> > choosing scim as your preferred IM from the menu choice. (This is just
> > a helper package focused on mostly Gnome/Gtk+2 environment.)
> >
>
> what about corporation with language-env with scim?
Basically it is possible but not much interesting.
scim: very good for X run under UTF-8 locales
language-env: syatem customization script helper which set system to
non-UTF-8 localization
The reason behind why I made m17n-env was this gap.
> language-env is not properly maintained but we could talk about this
> cowork with the maintainer, Tomohiro KUBOTA.
Yes, it can make to use scim but I would rather use it as shell
customization scripts only. Then m17n-env can be used to set up UTF-8
system.
> For korean, other
> suggestion for input method is reported against language-env like
> "nabi" instead of "ami".
I thought so too. You need to file BTS report with patch to get it
changed.
> > Alternatively, you can do this manually. In order to provide the SCIM
> > input method for the traditional X programs such as xterm, start SCIM
> > before running such programs:
> > $ scim -d
> > $ XMODIFIERS="@im=SCIM"; export XMODIFIERS
>
> with some editor, we could add lines in .xssession or .xinitrc in ~/:
>
> export XMODIFIERS="@im=SCIM"
> export GTK_IM_MODULE="scim"
> exec scim -d &
Yes this is true and exactly what I do in m17n-env
But using .xsession is not compatible with GDM menu.
Anyway, I will try including this aspect.
> > Gtk+2 programs can select their input method by right clicking input
> > field. If you chose XIM in this right clicked selections, then above
> > initialization should be sufficient for SCIM to provide input method.
> >
> > Alternatively, Gtk+2 programs can directly obtain their input from SCIM
> > through GTK IMModule by selecting SCIM in the right clicked selections
> > when scim-gtk2-immodule package is installed. In order to make this as
> > the default behavior, set the environment variable GTK_IM_MODULE in X
> > session as:
> > $ GTK_IM_MODULE="scim"; export GTK_IM_MODULE
> >
> > There is also a separate qt(kde) module for scim, but it's not packaged
> > (yet).
> >
> > SCIM supports any locales which are supported by IMEngines directly.
> > Any UTF-8 locales can be supported by modifying ~/.scim/config:
> >
> > After first run of SCIM, ~/.scim/config contains:
> > /SupportedUnicodeLocales = en_US.UTF-8
> > To add ja_JP.UTF-8, modify this to:
> > /SupportedUnicodeLocales = en_US.UTF-8,ja_JP.UTF-8
> >
>
> We could give some other suggestions, couldn't we?
> #en_US.UTF-8 for english
> #ja_JP.UTF-8
> #ko_KR.UTF-8
OK.
> ....
>
>
> > Alternatively, /etc/scim/global may be set this globally when you have
> > root access.
>
> Can we update /etc/scim/global by /etc/locale.gen or something?
I thought about it for m17n-env. This is TODO.
I should update it when I create /etc/gdm/locale-utf-8.conf
Oops, I need to restore gdm.conf when purging m17n-env,...
> CCs of replies from mailing lists are encouraged