Red Hat Bugzilla – Bug 253975
[Indic] - Double cursor showing when Delete by Backspace
Last modified: 2013-07-02 20:45:25 EDT
Description of problem:
Double cursor is appearing when try to delete some specific conjuncts (GSUB)
with backspace. Not applicable for all conjuncts. But Its not appearing if those
specific conjuncts places alone ---- Not within any word. Creating problem only
when those appearing within any word and followed by dependent vowels like Vowel
sign AA (U+0B3E)(inscript 'e') and followed by any other GPOS. This is the
observation result so far.
Version-Release number of selected component (if applicable):
Also present in downgraded version(seen upto pango-1.14.6-2.el5)
Steps to Reproduce:
1. Open gedit in or_IN locale
2. Enable SCIM with CTRL+SPACE
3. Choose inscript IME
4. Type h=<d"ejs
5. Press left-arrow key once
6. Press Bcakespace once (it will delete 'e' char)
7. Press Backspace once again.
8. Double cursor will appear.
Double cursor showing.
It should not show the double cursor and not deleting properly also.
-- Additional comment from firstname.lastname@example.org on 2007-01-08 04:19 EST --
Created an attachment (id=145038)
Screenshot for Double cursor
Example for Hindi,
[(U+0915)+094d+0930+0915+0916] = क्रकख
1. Copy paste in gedit (kedit for correct behavior)
2. goto End word
3. Move to one word Left
4. Press "Del" key
5. now you can check double cursor
Blinking two cursors is actually a special feature and not a bug. When a
conjunct comes in the middle of a word, and you try to use backspace on it, the
following characters start getting combined due to the exposed 'halant'. This
spoils the entire word and makes the user delete the entire word. To stop such a
behavior for indic scripts, the two blinking cursor feature is implemented, so
that even if the backspace is used on a conjunct between a word, it stops
following characters from forming their conjucts and allows user to correct the
later(erased) part of the conjunct. The current behavior that I see is exactly
how it should be. Thus I think this bug should be closed with a resolution NOTABUG.
This bug is same as #288821.
*** This bug has been marked as a duplicate of 288821 ***