Comment 53 for bug 37711

I understand your point very well but I'm pretty sure that would be a bad idea. More people will put bug report on it more chance we will have a correction. I'm very surprised that this bug is still here because ubuntu is the only distribution (with the last Suse) touch by this so the chance must come from an ubuntu bug (debian doesn't have the problem). Is it more UTF-8 related and not Qt-Scim? I think so or perhaps some developper can explain me why the same behavior happen with python/tk software...