[SCIM] Re: Problems starting SCIM
David Oftedal
david at start.no
Wed Jun 16 16:12:32 PDT 2004
I've figured out what the problem was. Did you read my earlier mail
where I'd tried installing SCIM in the "C" locale? Turns out that it
didn't help at all. Here are a couple of error messages I've gotten:
=====================================================================
(gimp-2.0:947): Gtk-WARNING **:
/usr/lib/gtk-2.0/2.4.0/immodules/im-scim.so: cannot open shared object
file: No such file or directory
=====================================================================
Cannot load module /usr/lib/gtk-2.0/immodules/im-scim.so:
libscim-0.9.so.0: cannot open shared object file: No such file or directory
/usr/lib/gtk-2.0/immodules/im-scim.so does not export GTK+ IM module
API: libscim-0.9.so.0: cannot open shared object file: No such file or d$
=====================================================================
And when I tried installing SCIM again:
=====================================================================
../intltool-update zh_CN.po
../intltool-update zh_TW.po
WARNING: It seems that none of the files in POTFILES.in contain marked
strings
make[2]: *** [zh_CN.po] Error 1
make[2]: *** Waiting for unfinished jobs....
........................................ done.
355 translated messages, 8 fuzzy translations, 9 untranslated messages.
make[2]: Leaving directory
`/var/tmp/portage/scim-0.99.0_pre20040614/work/scim-lib-20040614/po'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/scim-0.99.0_pre20040614/work/scim-lib-20040614'
make: *** [all] Error 2
!!! ERROR: app-i18n/scim-0.99.0_pre20040614 failed.
!!! Function gnome2_src_compile, Line 39, Exitcode 2
=====================================================================
So it turns out that the command lines aren't the problem, it's just
that SCIM can't be installed. It could still be because of the locale
I'm using, but that isn't easy for me to find out.
On another note, I'm still confused by the command line syntax. Why not
just autodetect the uim or m17n modules and simplify it down to:
scim -f socket -d
scim -f x11 -d
I guess a lot of this comes down to me not understanding the mechanisms
behind SCIM properly. It seems to me like they're more flexible than
they need to be, though, which is making it seem more difficult than it is.
-David
More information about the scim
mailing list