(*** This bug was imported into bugs.kde.org ***) Package: kdelibs Version: KDE 2.9.2 Severity: normal Installed from: Mandrake RPMs Compiler: precompiled mdk 8.1 version on website OS: Linux OS/Compiler notes: Not Specified My xkb keyboard layouts don't work anymore in KDE3 - they worked perfectly in KDE2. It would appear that the characters have been "forced" into the iso8859-1 character set since they appear exactly as a text file does when opened in a non-i18n-aware text editor. However other keyboard layouts work. (Submitted via bugs.kde.org)
I have identified the cause of the problem. It seems to be a conflict in th= e=20 charset names between Qt/KDE and Gtk in the environment variable "LC_CTYPE= "=20 (or LC_ALL). If I set LC_CTYPE to "ISO-8859-3" before launching a KDE application the= =20 "special keys" on the keyboard don't work. With the same setting gtk=20 applications work correctly and display their messages in Maltese. On the other hand if I set it to "ISO8859-3" (without the first "-") the= =20 keyboard works correctly in KDE applications but Gtk applications show the= =20 message "Gdk-WARNING **: locale not supported by C library" and everything= =20 gets displayed in English. Hope this helps in pinpointing the problem and fixing it. Ramon Casha
On Wednesday 06 March 2002 05:18 rcasha@waldonet.net.mt wrote: > Package: kdelibs > Version: KDE 2.9.2 > Severity: normal > Installed from: Mandrake RPMs > Compiler: precompiled mdk 8.1 version on website > OS: Linux > OS/Compiler notes: Not Specified > > My xkb keyboard layouts don't work anymore in KDE3 - they worked perfectly > in KDE2. It would appear that the characters have been "forced" into the > iso8859-1 character set since they appear exactly as a text file does wh= en > opened in a non-i18n-aware text editor. However other keyboard layouts > work. I don't understand. Your xkb layouts? They are part of XFree what has KDE = to=20 do with that? Greetings Stephan
I think I may offer some insight: any X application gets its keyboard composition map dependent on the locale of the environment (as set by the LANG, LC_ALL or LC_CTYPE variables). Without changing my keyboard layout, I get different results running the following commands: LANG=pt_BR kate LANG=pt_BR.UTF-8 kate LANG=pt_BR.UNDEFINED kate With the first one, I get normal ISO-8859-1 encoded keys passed by the X server and some keys in my keymap do nothing (like, dead_macron and others). With the second, I get UTF-8 keys, which means that some key combinations result in more than one byte. And with the third, which is an undefined locale, composition is completely disabled because the X library cannot find a suitable compose map. That means that all dead_* key combinations won't work either.
Is this bug still present in a recent version of KDE, such as 3.5.8 or KDE 4 RC2?
Closing due to no response by reporter. Please reopen if this bug is still present in a current version of KDE (at time of writing, 3.5.8 or 4.0.0).