Red Hat Bugzilla – Bug 493556
Deadkeys in Norwegian Nynorsk language setting (kde) doesn't work properly.
Last modified: 2009-05-19 20:47:56 EDT
Description of problem:
Deadkeys in Norwegian Nynorsk language setting doesn't work properly.
Deadkeys doesn't work as they should under KDE using nynorsk (Norwegian Nynorsk)
Version-Release number of selected component (if applicable):
libX11-1.1.5-2 (or earlier)
Steps to Reproduce:
1. Choose "Norsk (nynorsk)(Noreg)"(Norwegian Nynorsk) as language
2. Log in using KDE (should also be possible to see with kde-programs under gnome too)
3. Start e.g kile, konquorer or other kde program (also easily seen with xterm under kde)
4. In some text box/text input mode try to type é, õ or similar combined characters (é being ' + e and õ being ~ + o )
if you get two characters as an output and not the combined, that is an error.
In the file /usr/share/X11/locale/compose.dir you have the following;
$ grep ny_NO /usr/share/X11/locale/compose.dir
$ grep nn_NO /usr/share/X11/locale/compose.dir
and also these (for Norwegian Bokmål)
$ grep nb_NO /usr/share/X11/locale/compose.dir
According to several people I have talked to (also people doing lots of Norwegian translations of Free Software) ny_NO is *NOT* a proper language code for norwegian nynorsk. nn_NO *IS* the proper code.
When editing /usr/share/X11/locale/compose.dir, basically commenting out all
ny_NO entries and adding the two UTF-8 entries for nn_NO the deadkeys started
to work as expected.
Hope this can be fixed soon.
libX11-1.1.5-4.fc10 has been submitted as an update for Fedora 10.
libX11-1.1.5-4.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update libX11'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-4165
libX11-1.1.5-4.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.