[kde] [Bug 161945] grave deadkey doesn't work in KDE apps
David
bugzilla_noreply at kde.org
Mon Nov 5 18:30:19 GMT 2018
https://bugs.kde.org/show_bug.cgi?id=161945
--- Comment #4 from David <lassi_surinen at yahoo.ca> ---
This bug is still valid. I did a fresh install of both Debian 9.5 and Kubuntu
18.04 on the weekend and noticed that KDE still exhibited odd behaviour around
dead keys. Depending on exact locale settings, I would have no dead keys, or
dead key combinations would insert incorrect characters.
However! I was able to solve the problem by modifying certain locale-specific
files outside of KDE. I will describe below.
In my specific instance:
Keyboard: Canadian Multilingual
Locale: Esperanto
Solution:
add the following lines to /usr/share/X11/locale.alias (package libx11-data):
eo.UTF-8 eo_XX.UTF-8
eo_XX.UTF-8 eo_XX.UTF-8
eo_EO.UTF-8 eo_EO.UTF-8
add the following lines to /usr/share/i18n/SUPPORTED (package locales):
eo ISO-8859-3
eo.UTF-8 UTF-8
eo_XX UTF-8
eo_XX.UTF-8 UTF-8
The above changes make sure that both locales and libx11-data are harmonized in
terms of what encodings to use for EO locales. KDE is no longer confused. If
other people are having problems with their dead keys in KDE, they should check
the encoding definitions in the above 2 files, and, as an extra measure make
sure that /etc/default/locale defines a default system locale that uses UTF-8
(in my case system default is now eo.UTF-8).
As a concluding note, since the solution for me was outside KDE, this may not
be a KDE bug, however it is worth remembering that it is mostly KDE
applications (specifically Qt applications) that are affected by mismatched
locale definitions, and Gnome and other environments don't seem to have a
problem.
I hope this is helpful.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list