Bug 218264 - Too many russian keyboard layouts offered by anaconda installer
Summary: Too many russian keyboard layouts offered by anaconda installer
Alias: None
Product: Fedora
Classification: Fedora
Component: rhpl
Version: 6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Chris Lumens
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-12-04 09:15 UTC by Victor Ashik
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-12-05 15:11:32 UTC

Attachments (Terms of Use)

Description Victor Ashik 2006-12-04 09:15:40 UTC
Description of problem:

Anaconda installer offers too many variants of Russian keyboard layout.
I think all but one of them are obsolete variants of KOI8-R layout, and should
be removed or hidden, because only UTF-8 layout (Russian) works after setup.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot from setup media
2. Choose Russian language
Actual results:
Offers many variants of russian keyboard layouts.
Only one variant (default one) will work after setup.

Expected results:
Only one variant offered.

Additional info:

Comment 1 Chris Lumens 2006-12-04 21:31:41 UTC
The ru.map.utf8ru keyboard layout (labeled as "Russian (utf8ru)") is the only
working one?

Comment 2 Victor Ashik 2006-12-04 22:37:39 UTC
No, ru.map.utf8ru is missing: system-config-keyboard gives me "cannot open file
ru.map.utf8ru" message, and find /lib/kbd -name 'ru*' proves it.

The only working one is ru.map, labeled Russian.

Comment 3 Victor Ashik 2006-12-04 22:44:23 UTC
I must note, that there are still some cases for using single byte encodings
KOI8-R and windows-1251 with Fedora. So I think we should not remove keyboard
layouts completely, just hide them from installer and system-config-keyboard to
save regular user from encodings hell.

Comment 4 Chris Lumens 2006-12-05 15:11:32 UTC
This will be fixed in the next build of rhpl.  Thanks for the information.

Note You need to log in before you can comment on or make changes to this bug.