Mike schreef: " If you look at Scim Setup → IMEngine → Global Setup you should find the M17N input methods listed there as well. For example, under "Arabic (Egypt)" you should find 2 input methods: M17N-ar-kbd (this is from m17n-lib) Arabic (this is from scim-tables) " Only "Arabic" shows up there, no sign of "M17N-ar-kbd", nor any other of the m17n-lib package, although the latter have clearly been installed. I guess it's just an Ubuntu problem, so I shouldn't be bothering you; maybe I should try to put Suse Slick on the old machine. By the way, Ubuntu/Debian only has libm17n-0, and m17n-lib-bin in their repositories, but no m17n-lib. Maybe that's part of the problem? regards, Herman
h.w.meester@umail.leidenuniv.nl さんは書きました:
By the way, Ubuntu/Debian only has libm17n-0, and m17n-lib-bin in their repositories, but no m17n-lib. Maybe that's part of the problem?
The names of the packages and the distribution of the files may differ a little bit between different distribution. SUSE Debian m17n-lib libm17n-0, m17n-lib-bin m17n-lib-devel libm17n-dev m17n-db m17n-db On SUSE Linux, the .so files of the libraries are in the "m17n-lib" package. On Debian the .so files are in the libm17n-dev package. Apparently the .so files are needed for some input engines, see http://www.m17n.org/mlarchive/m17n-lib/200602/msg00013.html and followups. Usually, -devel or -dev packages are only needed for development, not for using the software. And usually .so files are not needed at runtime and can therefore be packaged in a -devel package. But it looks like m17n-lib is a little bit different. I.e. it might help if you install the lib17n-dev package as well. On SUSE the .so files are already in the m17n-lib package, therefore this problem doesn't occur. -- Mike FABIAN <mfabian@suse.de> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。
participants (2)
-
h.w.meester＠umail.leidenuniv.nl -
Mike FABIAN