Bug 171767

Summary: Linguistic representation for Indian Languages in System Settings insufficient
Product: [Applications] systemsettings Reporter: Jonathan Thomas <echidnaman>
Component: kcm_keyboard_layoutAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED UPSTREAM    
Severity: wishlist CC: andresbajotierra, karunakar
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jonathan Thomas 2008-09-28 01:42:29 UTC 
Version:            (using KDE 4.1.1)
OS:                Linux
Installed from:    Ubuntu Packages

Originally from https://launchpad.net/bugs/137766



India is a country with 18 officially recognized languages each being spoken by millions of people. Each of these languages need unique representation in the "Keyboard Layout" section of the "Regional & Language" module in System Settings

Steps to notice the problem in KDE 4.1.x:

1) KMenu --> System Settings --> Regional & Language --> Keyboard Layout
2) Under Available Layouts --> India

Now the problem is that one cannot add the Indian Languages separately. A few of the languages spoken in India are Hindi, Tamil, Telugu, Malayalam, Kannada, each being spoken by millions of people.

The only option available is to choose India, Add it to the Active Layouts & Choose the Layout variant.

Want to add another language? Again, choose India and Add to Active Layouts & Choose the Layout variant.

Now in the Layout variant field all languages of India are messed up and a beginner will get confused easily as to choose which layout for his home language.

Now linguistic representation need to be given here.
Comment 1 G Karunakar 2009-10-21 20:51:46 UTC 
Keyboard layouts is using XKB keymaps in Xorg. Earlier X releases had individual keyboard layout files - one for each language, later these were consolidated into one big 'in' map having all Indic keyboard layouts, resulting which one has to select India first and then the variant. Its sure a messy situation, needs to be solved first in Xorg
Comment 2 Jonathan Thomas 2009-11-10 15:03:34 UTC 
Ok, so this is an upstream problem.