Bug#520509: libx11-data: Thai XIM not turned on by default due to excessive Compose files
On Fri, Mar 20, 2009 at 11:23 PM, Theppitak Karoonboonyanan
> On Fri, Mar 20, 2009 at 9:41 PM, Julien Cristau <firstname.lastname@example.org> wrote:
>> On Fri, 2009-03-20 at 20:16 +0700, Theppitak Karoonboonyanan wrote:
>>> Surely this is not the correct fix. The Compose files do not belong here, and
>>> the above bugs should be fixed instead.
>> The problem is, nobody upstream seems comfortable with XIM, so
>> developers are hesitant to apply patches to that part of the code, for
>> fear of breaking stuff...
> Oh, no. So, how can we do? Could we patch Debian?
Let me elaborate this a little bit.
The most serious bug which is actually avoided is
fd.o #16475, which blocks SCIM events on Thai locale.
If not all the three bugs will be fixed, this one should be
considered at least. It's not about XIM, but SCIM.
And the proposed fix is just about fixing Thai XLOCALE data.
The other two are specific to Thai XIM.
fd.o #12759 also affects GTK+/Qt apps with XIM selected
as the input method. GTK+ users can avoid this by choosing
other IM module instead. But Qt users must wait for KDE 4
to be able to do that. This bug causes some valid sequences
to be blocked. So, it's still essential to KDE users.
fd.o #12517 is minor bug. It hardly affects laptop users in
general, for example, as NumLock/CapsLock is hardly used
there. But desktop users can still see it. BTW, it doesn't block
Thai text input. Just stop filtering.