Bug 571821 - Upper Row Keys in Hindi inscript layout don't work
Summary: Upper Row Keys in Hindi inscript layout don't work
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: m17n-contrib
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Parag Nemade
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-09 16:19 UTC by Ujjwol
Modified: 2010-03-15 15:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-15 06:22:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Picture reporting for the bug. (69.72 KB, image/png)
2010-03-09 16:20 UTC, Ujjwol
no flags Details
Hi-inscript.mim (3.40 KB, patch)
2010-03-14 03:35 UTC, Ujjwol
no flags Details | Diff

Description Ujjwol 2010-03-09 16:19:22 UTC
Description of problem:
It is not possible to type upper numeric words in inscript layout like ज्ञ and others

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

How reproducible:
Insert Hindi/Inscript Keyboard layout. see the keyboard layout and try to type it.
  
Actual results:
It not possible to type.

Expected results:
I should be able to type as shown by layout picture.

Comment 1 Ujjwol 2010-03-09 16:20:43 UTC
Created attachment 398835 [details]
Picture reporting for the bug.

Comment 2 Parag Nemade 2010-03-10 04:23:53 UTC
Working fine for me. 

Explain what you tried and which m17n-contrib you have installed and which editor you tried?

Comment 3 Ujjwol 2010-03-10 17:54:10 UTC
I just selected Hindi and Nepali Language during installation and now add keyboard layout from panel.

Comment 4 Parag Nemade 2010-03-11 03:39:40 UTC
Still I see no bug. Worked fine for me in gedit/kwrite/firefox/openoffice.org applications.

Comment 5 Ujjwol 2010-03-13 02:35:12 UTC
Hey, does the inscript in fedora matches with this http://fedoraproject.org/wiki/I18N/Indic/HindiKeyboardLayouts. ?

Comment 6 Ujjwol 2010-03-13 02:41:57 UTC
Lack of ज्ञ............ and other upper words there makes it not standard as defined in http://www.tdil.mit.gov.in/keyoverlay.htm

Comment 7 Parag Nemade 2010-03-13 16:06:20 UTC
There is a lot of problems here. First decide which Fedora version are you using. Bug is reported against rawhide version and initial comment says its 12.
Again not provided which version are you using of m17n-contrib package.

Attach /usr/share/m17n/hi-inscript.mim from your system here. Also, no mention of where are you not able to type those characters(gedit/kwrite/firefox/ openoffice.org applications). Are you using ibus? Are you using Scim? Are you using xkb?

Provide full details.

Comment 8 Ujjwol 2010-03-14 03:34:18 UTC
Fedora Version: 12

I am not using SCIM and neither ibus, So it must be xkb(I think.It is the one I access from the panel not systray) ?

I was not able to type those characters in gedit and firefox(other application i have not tried) ?

Comment 9 Ujjwol 2010-03-14 03:35:38 UTC
Created attachment 399940 [details]
Hi-inscript.mim

Comment 10 Ujjwol 2010-03-14 03:36:59 UTC
[root@lamichhane ~]# rpm -qa m17n-contrib
m17n-contrib-1.1.10-2.fc12.noarch

Comment 11 Parag Nemade 2010-03-14 04:25:00 UTC
Now I got clear view of what you have and why you are not able to type.

Problem you stated is valid and its valid since years as we need X server to be changed so that xkb can type complex(conjunct) characters.

Remember xkb currently accepts only standard unicode characters and what you are trying to type is not having unicode hex code in Devanagari chart.

I have already raised this issue at https://bugs.freedesktop.org/show_bug.cgi?id=25025

Comment 12 Parag Nemade 2010-03-15 06:22:53 UTC
Closing this as reported description is problem in upstream X server code that unable to handle conjuncts.

Comment 13 Ujjwol 2010-03-15 15:14:07 UTC
Ok then till the bug is fixed in upstream, i will use SCIM which is fine for Inscript Layout. But it would be great if we could see the it fixed by Fedora 13.


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