Description of problem: The (French) Belgian keyboard is unavailable for installation (not in the drop down list propose) Version-Release number of selected component (if applicable): - Fedora 18 Nightly compose 20121030 - desktop livecd i686 - anaconda.i686 18.19-1.fc18 How reproducible: Steps to Reproduce: 1. Launch the F18 livecd 2. click on "install to hard drive" icon 3. select "keyboard"; in the drop down list the (french) belgian keyboard is unavailable Actual results: (french) belgian keyboard is not listed Expected results: (french) belgian keyboard should be listed Additional info:
Where do you see a 'French (Belgian)' keyboard? We are getting the list of available layouts directly from the X server.
In the previous Fedora releases the selection for the keyboard was easy : Belgian. In Fedora 18, there is no such option. I just see German (Belgian). As I do not speak German I suppose there should be a "French (Belgian)" keyboard (and even a "Dutch (Belgian)" keyboard).
(In reply to comment #2) > In the previous Fedora releases the selection for the keyboard was easy : > Belgian. > In Fedora 18, there is no such option. I just see German (Belgian). > As I do not speak German I suppose there should be a "French (Belgian)" > keyboard (and even a "Dutch (Belgian)" keyboard). In the previous Fedora releases there was a list of layouts with names "invented" in system-config-keyboard. We now get the list of layouts directly fromt the X server. You can run the testing script from: http://vpodzime.fedorapeople.org/layouts_list.py Which gives me these results: ./layouts_list.py|grep '\[be' French (Belgian) [be] French (Belgian (alternative)) [be (oss)] French (Belgian (alternative, latin-9 only)) [be (oss_latin9)] French (Belgian (alternative, Sun dead keys)) [be (oss_sundeadkeys)] French (Belgian (ISO alternate)) [be (iso-alternate)] French (Belgian (eliminate dead keys)) [be (nodeadkeys)] French (Belgian (Sun dead keys)) [be (sundeadkeys)] French (Belgian (Wang model 724 azerty)) [be (wang)] German (Belgian) [be] German (Belgian (alternative)) [be (oss)] German (Belgian (alternative, latin-9 only)) [be (oss_latin9)] German (Belgian (alternative, Sun dead keys)) [be (oss_sundeadkeys)] German (Belgian (ISO alternate)) [be (iso-alternate)] German (Belgian (eliminate dead keys)) [be (nodeadkeys)] German (Belgian (Sun dead keys)) [be (sundeadkeys)] German (Belgian (Wang model 724 azerty)) [be (wang)] Dutch; Flemish (Belgian) [be] Dutch; Flemish (Belgian (alternative)) [be (oss)] Dutch; Flemish (Belgian (alternative, latin-9 only)) [be (oss_latin9)] Dutch; Flemish (Belgian (alternative, Sun dead keys)) [be (oss_sundeadkeys)] Dutch; Flemish (Belgian (ISO alternate)) [be (iso-alternate)] Dutch; Flemish (Belgian (eliminate dead keys)) [be (nodeadkeys)] Dutch; Flemish (Belgian (Sun dead keys)) [be (sundeadkeys)] Dutch; Flemish (Belgian (Wang model 724 azerty)) [be (wang)] So, as it can be seen, Belgian layouts are in the lists of multiple languages. But the value in [] is the value that can be given to X server, so these are the same layouts (not language specific).
Created attachment 638889 [details] French selection
Created attachment 638890 [details] Belgian selection
- Below the output of the command on my livecd Fedora 18 system. - In attachment the screenshots of the "keyboard" selection during the F18 installation -> 1 screenshot for search with "French" => no French (Belgian) -> 1 screenshot for search with "Belgian" => Only German (Belgian) Drop down list search problem in anaconda? --- [liveuser@localhost ~]$ ./layouts_list.py | grep '\[be' French (Belgian) [be] French (Belgian (alternative)) [be (oss)] French (Belgian (alternative, latin-9 only)) [be (oss_latin9)] French (Belgian (alternative, Sun dead keys)) [be (oss_sundeadkeys)] French (Belgian (ISO alternate)) [be (iso-alternate)] French (Belgian (eliminate dead keys)) [be (nodeadkeys)] French (Belgian (Sun dead keys)) [be (sundeadkeys)] French (Belgian (Wang model 724 azerty)) [be (wang)] German (Belgian) [be] German (Belgian (alternative)) [be (oss)] German (Belgian (alternative, latin-9 only)) [be (oss_latin9)] German (Belgian (alternative, Sun dead keys)) [be (oss_sundeadkeys)] German (Belgian (ISO alternate)) [be (iso-alternate)] German (Belgian (eliminate dead keys)) [be (nodeadkeys)] German (Belgian (Sun dead keys)) [be (sundeadkeys)] German (Belgian (Wang model 724 azerty)) [be (wang)] Dutch; Flemish (Belgian) [be] Dutch; Flemish (Belgian (alternative)) [be (oss)] Dutch; Flemish (Belgian (alternative, latin-9 only)) [be (oss_latin9)] Dutch; Flemish (Belgian (alternative, Sun dead keys)) [be (oss_sundeadkeys)] Dutch; Flemish (Belgian (ISO alternate)) [be (iso-alternate)] Dutch; Flemish (Belgian (eliminate dead keys)) [be (nodeadkeys)] Dutch; Flemish (Belgian (Sun dead keys)) [be (sundeadkeys)] Dutch; Flemish (Belgian (Wang model 724 azerty)) [be (wang)]
First of all, 'French (Belgian)', 'German (Belgian)' and 'Dutch; Flemish (Belgian)' are all the same layout -- 'be' with description 'Belgian'. Because the string in square brackets is the only thing you can pass to the X server as a layout specification. It specifies layout and in some cases also variant (string in parentheses). Now, the difference between layouts_list.py and Anaconda is that while layouts_list.py goes through all languages and stores lists of layouts for each particular language and then prints layouts for each language in 'LANGUAGE (LAYOUT DESCRIPTION)' format, Anaconda stores a list of all available layouts ('be', 'be (oss), 'be (wang)',...) which are displayed in a human readable way using the same format as layouts_list.py. That's why 'be' is listed in Anaconda only as 'German (Belgian)' and not also as 'French (Belgian)' and 'Dutch; Flemish (Belgian)'. Listing it three times (for each language it is related to) would complicate things quite a lot. Having it as it is now means that only a rendering function displaying 'LANGUAGE (LAYOUT DESCRIPTION)' instead of the layout name ('be') has to be used. Storing and listing layouts as layouts_list.py does would mean converting 'LANGUAGE (LAYOUT DESCRIPTION)' back to the layout name every time it is used (setting runtime X layouts, writing X configuration, writing kickstart etc.). The other major problem is that only kickstart data structure is passed between spokes (screens) and layout names have to be used in this structure (otherwise kickstart text installations would need an X server running for the conversion and some other problems). Also you would end up choosing 'French (Belgian)' in the installation and getting e.g. 'German (Belgian)' in the system because it is the same layout and different tools can use different ways to display the layout description. I hope that this explanation is understandable and the output is that 1) no layout is missing in the list displayed by Anaconda 2) it is not easy to use the same list as layouts_list.py The only thing I could do here is, that there would items like Dutch; Flemish, French, German (Belgian) in the list, but I believe you too see it would be confusing and would result in problems with searching for a particular layout because of the ordering. Thus I'm closing this bug as CANTFIX. If you still think this could be fixed and if you have and idea how to do that, reopen this bug please.