After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 597812 - [ml_IN] wrong behavior when backspace used with zwj + punctuation
[ml_IN] wrong behavior when backspace used with zwj + punctuation
Status: RESOLVED OBSOLETE
Product: pango
Classification: Platform
Component: indic
1.26.x
Other Linux
: Normal normal
: ---
Assigned To: Pango Indic
pango-maint
: 703856 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-10-08 14:17 UTC by Santhosh Thottingal
Modified: 2018-05-22 12:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Santhosh Thottingal 2009-10-08 14:17:58 UTC 
When [consonant] + [virama] + zwj + [space | punctuation] sequence is present in any text editor and then if backspace is pressed the whole [consonant] + [virama] + zwj + [space | punctuation] sequence get deleted. 
Samples for this squence:
1. അവന്‍ + space 
2. ഞാന്‍?
3. ഇവള്‍!

The expected sequence after backspace is [consonant] + [virama] + zwj 
Qt and ICU gives expected result.

When [consonant] + [virama] + zwj  comes inside a word, for eg: നന്‍മ , there is no problem. So this problem happens only if zwj is followed by punctuation or space.

-
Comment 1 Ani Peter 2009-11-04 11:04:30 UTC 
ping
Comment 2 Pravin Satpute 2013-07-09 10:17:25 UTC 
*** Bug 703856 has been marked as a duplicate of this bug. ***
Comment 3 Pravin Satpute 2013-07-09 10:18:03 UTC 
Tested on Fedora 19

Even 200d get clustered with single Indic unicode characters as well.

Example: "0915 200d" " "

Version: 
pango-1.34.1-1.fc19.x86_64
harfbuzz-0.9.18-3.fc19.x86_64
Comment 4 Akira TAGOH 2015-01-16 07:27:39 UTC 
Similar to Bug#65547, I suppose it is because Pango checks the character classification only to determine what characters should be deleted with the backspace. the behavior at comment#3 explains that.
Comment 5 GNOME Infrastructure Team 2018-05-22 12:53:31 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/pango/issues/164.