Re: Another --> Re: GtkMovementStep of GtkTextView

Hi Owen, ....

] > 
] > So, I think that, in arabic script, users like to have <backspac> to delete
] > the previous key typed. This is the same as Thai/Indic/Korean/Vietnamese...
] > One difference in arabic is that those base letter with diacritic
] > (U+0622..U+0626) will be treated as a single letter and that is also typed
] > by one key stroke. The <backspace> algorithm still works with those letters
] > because they have their own codepoints. <backspace> algorithm is just 
] > one codepoint from logical stream...
] > For lam+alif case, <backspace> algorithm (if it's just removing one logical
] > codepoint before the current cursor) will just remove "alif" first and this
] > should satify arabic users as well...., I guess.....
] lam+alif is different than, e.g., Thai because while (in Pango
] terminology) the two characters form a "cluster", they aren't a single
] grapheme.  It is possible to position the cursor between them.  (The
] cursor is displayed halfway through the glyph).

I'm just realizing that lam+alif case, the cursor can be in between.
This is different than the hindi ligature which cursors couldn't be
placed in the middle. If this isn't correct, anyone please clearify ?

Just want to make sure that I understand the point, in Pango technology,
we are  trying to sepearate between the "display" algorithm and "cursor
movement" algorithm. So, in this lam+alif case, the cursor can be moved/placed
in between lam and alif but it's not because of 2 characters forms one cluster
and they aren't one single grapheme. It shouldn't be matter because the
display algorithm and cursor movement algorithm are seperate. Right ?

Chookij V.

] Regards,
]                                         Owen
] _______________________________________________
] gtk-i18n-list mailing list
] gtk-i18n-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]