After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 689269 - user can search language only with English language
user can search language only with English language
Status: RESOLVED DUPLICATE of bug 684861
Product: gnome-control-center
Classification: Core
Component: Region & Language
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-11-29 12:23 UTC by anish
Modified: 2012-12-04 02:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description anish 2012-11-29 12:23:24 UTC 
Suppose user is using  Hindi language and he wants to search English or Marathi 
language then he needs to select English as input source.

How to reproduce:-

1: With Marathi input source (other than English) go to "Region and Language setting" .

2: Add language , search language will come up 

3: type "मराठी" which is "Marathi" in English

Result:
Nothing shows up.

Actual Result:
Marathi Language should get displayed/selected 

How to fix: 
CLDR database has mapping of each language into other languages. 
http://cldr.unicode.org/
We need to create db from those xml file.

I can work on it and provide patch.
Comment 1 Mathieu Bridon 2012-11-29 12:29:41 UTC 
That could even help bug 684540: with such a DB, G-C-C could search for the user input in other languages than the current locale.
Comment 2 Matthias Clasen 2012-11-29 23:51:32 UTC 
We have that mapping available - we've had such bilingual language lists in gdm in the past.
Comment 3 Jens Petersen 2012-11-30 06:45:32 UTC 
(In reply to comment #2)
> We have that mapping available - we've had such bilingual language lists in gdm
> in the past.

Yes it would be nice to have it "everywhere".
Comment 4 Matthias Clasen 2012-12-04 02:11:52 UTC 

*** This bug has been marked as a duplicate of bug 684861 ***