Bug 211576

Summary: 200C (ZWNJ) is missing from Hindi keyboard layout
Product: Red Hat Enterprise Linux 5 Reporter: Rajesh Ranjan <rranjan>
Component: m17n-dbAssignee: Mayank Jain <majain>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0CC: ankit, eng-i18n-bugs
Target Milestone: ---Keywords: i18n, Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 5.0.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-11-29 23:02:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
ZWJ problem in Hindi none

Description Rajesh Ranjan 2006-10-20 07:23:35 UTC
Description of problem:

Sometimes it is needed in Hindi that halant should not be combined with the
charactor next to halant. So for this 200d shd be in our keyboard layout. See
the attachment for the probelm.


Version-Release number of selected component (if applicable):
1.3-32.el file

How reproducible:
Everytime

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Unable to have halant showing with the charactor

Expected results:


Additional info:

Comment 1 Rajesh Ranjan 2006-10-20 07:23:36 UTC
Created attachment 138946 [details]
ZWJ problem in Hindi

Comment 2 Mayank Jain 2006-10-20 07:40:42 UTC
Hi,

I already have a working fix for this, but I need to know that which keys in the
keymaps (inscript, phonetic) should this ZWJ be mapped to.

Rajesh, can you please provide me the keys to which ZWJ be mapped to (for
inscript/phonetic)?

Thanks,
Mayank

Comment 3 Rajesh Ranjan 2006-10-20 08:13:48 UTC
Hi Mayank,

I think it would be better if we can have same keys for inscript and phonetic (
ie  d and f respectively) and by pressing these two times continuously we can
get the resultant halant ie not going to combined with the charactor next to
halant. 

In this way it will be easier to memorise it for user as well not need to
replace or shift any other charactor.

Regards,

Rajesh

Comment 4 Mayank Jain 2006-10-20 08:54:28 UTC
Okay, mapping the following

"dd" to 200d in inscript
"ff" to 200d in phonetic

Thanks,
Mayank

Comment 5 Mayank Jain 2006-10-20 09:27:19 UTC
After mapping, following can be typed (as per in screenshot in comment 1)

द‍्भ

Thanks,
Mayank

Comment 6 Mayank Jain 2006-10-20 09:49:34 UTC
Fixed in

Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
m17n-db-1.3.3-33.el5                      dist-5E               majain


Comment 7 Leon Ho 2006-10-23 07:35:24 UTC
Moving to MODIFIED.

Comment 8 RHEL Program Management 2006-10-24 19:31:58 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 9 A S Alam 2006-10-30 04:11:25 UTC
m17n-db-1.3.3-33.el5 Package fixes this issue and this package is available with
following tree:
RHEL5-Client-20061027.0

Comment 10 Rajesh Ranjan 2006-11-02 11:35:39 UTC
By mistake, Instead of 200c, in keyboard layout 200d is inserted for the
required value.
200c is required for halant to be not connected with the next charactor after
the halant.

http://www.unicode.org/faq/indic.html#16

Comment 11 Mayank Jain 2006-11-02 11:40:38 UTC
Changing the bug summary to 
"200c (ZWNJ) is missing from Hindi keyboard layout"
From
"200d (ZWJ) is missing from Hindi keyboard layout"

Comment 12 Mayank Jain 2006-11-02 11:44:28 UTC
Okay, re-mapping the following

"dd" to 200c in inscript
"ff" to 200c in phonetic

Thanks,
Mayank

Comment 13 Mayank Jain 2006-11-02 12:11:33 UTC
Re-fixed in
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
m17n-db-1.3.3-35.el5                      dist-5E               majain

Moving to modified.

Comment 14 Mayank Jain 2006-11-02 12:29:18 UTC
Similar problem found in dist-fc7 and dist-fc6-updates-candidate hence new builds :-

dist-fc7 - m17n-db-1_3_3-34_fc7
dist-fc6-updates-candidate - m17n-db-1_3_3-32_fc6

Were made.

Thanks,
Mayank

Comment 15 A S Alam 2006-11-07 12:01:34 UTC
m17n-db-1.3.3-35.el5   packages contains the fix, but it is not available in Tree

Comment 16 A S Alam 2006-11-09 12:51:54 UTC
cross check with Rajesh, key-sequence is wrong for halant and ZWNJ
now it is:
A+ZWNJ+Halant+B
but it should be
A+Halant+ZWNJ+B

this is problem of Pango, which is filed in separate bug

Comment 17 Mayank Jain 2006-11-09 13:08:31 UTC
Errounous fix is now fixed in 
m17n-db-1_3_3-37_el5
m17n-db-1_3_3-36_fc7
m17n-db-1_3_3-34_fc6

Comment 18 A S Alam 2006-11-26 15:16:12 UTC
it is ok in following pacakges:
m17n-db-1_3_3-40_el5

Comment 19 A S Alam 2006-11-29 23:02:18 UTC
Package is available in following Tree:
RHEL5-Client-20061129.nightly