Comment 70 for bug 34282

Ming, if someone would have been so kind as to explain to Gusty users how they could eventually solve their deadkeys problem and get scim to work (I'm sorry, but
>Please follow up deadkey issues in bug #155780, thanks.
didn't solve anything, neither for scim nor for the deadkeys issue), we wouldn't have to maintain the SCIM page ourselves.

I'm far from being able to make a better judgement than you - but I know only robinl came with a method that worked, and that after one week of big regression, when we couldn't use our computer for the productivity tasks we were taking for granted.

We all know it's not your fault, and it's quite saddening to see the good work you do in Debian messed up by some anonymous Ubuntu main developer.

The documentation at https://help.ubuntu.com/community/SCIM is open to anyone to edit - and different inputs have already made the page more helpful. Anybody able to understand the method you just suggested and check it works in Gutsy will be able to edit that page accordingly - the only important thing is that the explanation is easily understandable by a newbie, with screenshots and such.

>Personally I think it's a very bad idea to encourage users to manually
>change system conffiles (/etc/X11/xinit/xinput.d/scim is one of them)
>when there is an alternative

There was no alternative till you explained it to us, and during that time we need to get our job done. I know you're on Debian, but for the other subscribers, if this was a so well-known method, how come none of the Gusty developers answered our difficulties in this thread, or, better, advertise us that a major breakage would occur with scim in Gutsy (release highlights are for that, not just for show)?

Anyway, thanks again Ming for spending time for us even though you're on Debian. If none edits the documentation, I might do it again if I can test that on another computer. For the moment, I'd rather keep things as they are on mine, because one week of mess is more than enough.