Created attachment 345574 [details] gdm-language-selection-list Description of problem: In F-11 gdm language selection list, I found that for locales ks_IN and ks_IN@devanagari are showing same language name "Kashmiri (India)". Both of these locales are for India country but divided based on scripts. ks_IN uses Perso-Arabic script whereas ks_IN@devanagari uses Devanagari script. Version-Release number of selected component (if applicable): gdm-2.26.1-10.fc11.x86_64 How reproducible: always Steps to Reproduce: 1. look into gdm language selection list 2. 3. Actual results: Both locales shows same language name and confuses which language is selected. Expected results: Can we have some way to identify which locale is selected or Can we have some kind of change in language list? Additional info:
It's supposed to show the language name in the native language and script. There must not be good enough translation coverage in the iso-codes package. Reassigning.
*** Bug 502984 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > It's supposed to show the language name in the native language and script. > There must not be good enough translation coverage in the iso-codes package. > Reassigning. Is this really translation issue? But as per https://bugzilla.redhat.com/show_bug.cgi?id=502984#c2, it looks language name construction issue.
nope, you're right, moving back to gdm.
looks like a broken regex. This: --- a/gui/simple-greeter/gdm-languages.c +++ b/gui/simple-greeter/gdm-languages.c @@ -123,7 +123,7 @@ gdm_parse_language_name (const char *name, error = NULL; re = g_regex_new ("^(?P<language>[^_.@[:space:]]+)" "(_(?P<territory>[[:upper:]]+))?" - "(.(?P<codeset>[-_0-9a-zA-Z]+))?" + "(\\.(?P<codeset>[-_0-9a-zA-Z]+))?" "(@(?P<modifier>[[:ascii:]]+))?$", 0, 0, &error); if (re == NULL) { should fix it.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
if this fix is applied then can we close this bug?