On Tue, Nov 29, 2011 at 11:39 PM, Osamu Aoki <os...@debian.org> wrote: > > As I think about this again, I made false statement. > > We need something like (multi-arch makes library file path complicated.) > > IM_CONFIG_KEY="/usr/share/libthai/thbrk.tri"
So, what's the real purpose of $IM_CONFIG_KEY? If I'm right, in /usr/share/im-config/im-config.common, it's used for probing for automatic_im by checking the file existence. And setting it to this libthai dictionary file would always enable it on virtually all machines with GTK+ installed, whether or not gtk[3]-im-libthai is installed. (It's libpango1.0-0 that pulls libthai0 in, which in turn pulls libthai-data in.) Is that what you mean? Other potential r-depends are libm17n-0 and libsombok3 (via libunicode-linebreak-perl, sympa). But it may be missed on pure KDE environments, because libthai0 is not required there (although it Enhances: kdelibs5), but the 'thai' entry is still valid for XIM setup there. If we really want to find the minimal requirement of this 'thai' entry, it's probably libx11, where Thai XIM is implemented. But again, it's multiarch. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
