Bug 132189 - Backport backspace_deletes_character from HEAD
Summary: Backport backspace_deletes_character from HEAD
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact:
Depends On:
Blocks: 131589
TreeView+ depends on / blocked
Reported: 2004-09-09 19:04 UTC by Owen Taylor
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-21 14:40:13 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Owen Taylor 2004-09-09 19:04:33 UTC
The backspace_deletes_char changes are important for Indic, 
and we should backport them to our GTK+-2.4 package.

(What they do is that if you have a syllable,say:

 <cons> <virama> <cons> <vowel>

with the cursor after hit, and you hit the <Backspace>
key, only the vowel is deleted, not the entire syllable.)

Comment 1 Matthias Clasen 2004-09-10 15:43:38 UTC
The backport is in gtk2-2.4.9-7.

Comment 2 Leon Ho 2004-09-20 10:56:50 UTC
This 'feature' happens to many other scripts as well. Because of this,
our distro may not able to pass openi18n certification any more.

Please see "Assertion 2: Verify this utility can delete per character
in the text encoded in UTF-8" at:

Comment 3 Owen Taylor 2004-09-20 12:55:28 UTC
1) If you can find scripts where the behavior is wrong for *users*
   of the scripts, then we can modify the behavior for those

2) If it's just standards compliance, then if you *first* file
   a defect report against openi18n, then possibly we can 
   add a config flag or environment variable to make Pango
   produce the "desired" behavior.

What that openi18n test about though is testing that delete isn't
deleting bytes; the fact that GTK+ delete is now invariant of 
normalization form is certainly more correct than otherwise.

Comment 4 Leon Ho 2004-09-21 12:10:37 UTC
For example, I would say European and Korean languages are not favor
with this feature. Actually AFAIS, only scripts like Indic, Thai etc
may like this implementation.

Can we do the opposite? We can disable by default, but enable the
script we found that required that feature?

Comment 5 Owen Taylor 2004-09-21 14:40:13 UTC
I don't think you've tried it for European languages...

The code in Pango changes behavior script by script; currently
it has:

&& !GREEK (wc))

For Korean, I suspect if we had sufficiently good input
method integration, user's would prefer delete to work
Jamo by Jamo, but that probably isn't the case now.

(That is, without this change, if I type H-A-N <delete>
then just the N disappears. But if I move after a syllable
'han' and type <delete> then the whole syllable disappears.

With this change, the two cases are consistent, except that
when the N is deleted, I'm not in compose mode, so if I type
N again it starts a new syllable. What should happen is that
deleting the N should put me back into compose mode. I'm
not really sure how to get that working with the current

Can you file a new, separate bug against Pango to modify the
the backspace_deletes_character assignment to skip Korean?
I don't want to retitle and reassign this bug,that's just
too confusing.

Note You need to log in before you can comment on or make changes to this bug.