https://qa.mandrakesoft.com/show_bug.cgi?id=1681
------- Additional Comments From <a href=/faq.html#spam>[EMAIL PROTECTED]</a> 2003-02-21 19:18 ------- Yes, this bug is still valid. However, it has now several mitigating factors: 1) qtconfig is installed by default. Changing the XIM-style for qt applications by running /usr/lib/qt3/bin/qtconfig makes this bug mute. 2) localedrake will [hopefully soon] be modified to change the XIM-style for qt applications, so the users won't even have to run qtconfig in order to avoid this bug. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: <a href=/faq.html#spam>[EMAIL PROTECTED]</a> status: UNCONFIRMED creation_date: description: On a fresh cooker install, I created a new user, switched that user to use Japanese. Once logged in, I started kwrite and activated kinput2 with shift-space. After that, no characters appeared in the document I was editing. I closed kwrite, edited ~/.qt/qtrc and added XIMInputStyle=On The Spot in the [General] section I started kwrite again and I could use kinput2 as to do all the editing I wanted. In short: with some KDE applications on-the-spot does not work well or look all that great. With kwrite, it simply does not work at all! Since on-the-spot is the default state of a Japanese environment created by localedrake, this is a problem. My suggestion: I'm sure nobody on the Mandrake team wants to find this error in kwrite. Instead, I say that localedrake should change ~/.qt/qtrc in the manner prescribed above when Japanese is selected as the locale. That's a simple solution, it's relatively clean and all users of Japanese will love it because on-the-spot in KDE is just painfully ugly! [Just to name one: there is no indicator that the Input Method Editor is active.]
