Red Hat Bugzilla – Bug 145431
[bn_IN] backspace changes independent indic characters
Last modified: 2009-07-07 05:07:37 EDT
Description of problem:
when backspace key is hit after a consonant with a dot at the bottom,
the dot vanishes and the result is an independent and unrelated
alphabet. The dot in this case is not a vowel sign, it is a part of
the consonant itself.
The 1st example is of Bengali Yaa - <09DF>. A backspace changes it to
a bengali Ya - <09AF>.
See attached image for example. The image uses the bengali probhat
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start gedit in bengali locale
2. Ctrl+space, F6
3. press 'z' then bkspace
The 'dot' below the yaa character gets deleted, and it becomes a ya.
The complete yaa character should get deleted.
Tested on RHEL4-RC-0107.0 WS
Created attachment 109923 [details]
screenshot of gedit
Are there any plan this this entry?
Reassigning pango bugs to Behdad.
I debug this bug and I find that this bug is not the bug of Pango, but the bug
gtk_entry_backspace( ) and gtk_text_buffer_backspace( ) need be modified.
I will write a patch for this bug.
I filed a new bug of gtk in Gnome bugzilla.
I wrote a patch for this bug.
The patch is below:
Problem still exists in RHEL5 Beta.
Component Version tested :
Package available in the tree :
tested this bug with EL4 also. there tested it with the Component Version :
pango-1.6.0-9.2. Bug is also exists there in EL4.
If any rpm or test RPM available to test the patch mentioned in comment #5, pls
attach it, so that i can test the work done fixing this problem.
LingNing, any update here?
I wrote a patch for fixing this bug and bug217017, bug220805. And this patch
fixed all problems about backspace-delete and cursor moving of all split matras
of all indic scripts.
The patch is:
Rahul, can you review the status of this?
This behavior is due to the Normalization. And as seen on the comments on
upstream bugs, backspace on NFD, is actually an expected behavior. So since this
is what Unicode expects, I am not sure if this should be treated as a bug.