Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
Summary: [te_IN][pango]GSUB delete key can't delete the whole char in f10,but works well in rhel5.3
https://bugzilla.redhat.com/show_bug.cgi?id=499790
Summary: [te_IN][pango]GSUB delete key can't delete the whole char in f10,but works well in rhel5.3 Product: Fedora Version: 10 Platform: i386 OS/Version: Linux Status: NEW Severity: medium Priority: low Component: pango AssignedTo: besfahbo@redhat.com ReportedBy: kxiong@redhat.com QAContact: extras-qa@fedoraproject.org CC: besfahbo@redhat.com, fedora-fonts-bugs-list@redhat.com Classification: Fedora Target Release: ---
Description of problem: GSUB press Delete key to delete the whole char,it can't delete the whole char in f10,but works well in rhel5.3. I think it is a regression bug.
Version-Release number of selected component (if applicable): pango-devel-1.22.1-1.fc10.i386 pango-1.22.1-1.fc10.i386 pangomm-2.14.0-2.fc10.i386
How reproducible: always
Steps to Reproduce: 1.In gedit input U+0C15 U+0C4D U+0C15 2.Press Delete key to delete the char 3.
Actual results: It can't delete the whole char,it will delete part of the char
Expected results: It will delete the whole char.
Additional info: All of chars in [te_IN][GSUB] has the same problem. But in rhel 5.3 they work well. So I think it is a regression problem.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=499790
Lawrence Lim llim@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |llim@redhat.com Summary|[te_IN][pango]GSUB delete |[te_IN][pango]GSUB delete |key can't delete the whole |key can't delete the whole |char in f10,but works well |char in f10 |in rhel5.3 |
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=499790
A S Alam aalam@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |i18n CC| |aalam@redhat.com, | |fedora-i18n-bugs@redhat.com
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=499790
--- Comment #2 from koka xiong kxiong@redhat.com 2009-05-11 03:04:13 EDT --- Description of problem: GSUB press Delete key to delete the whole char,it can't delete the whole char in f10
Version-Release number of selected component (if applicable): pango-devel-1.22.1-1.fc10.i386 pango-1.22.1-1.fc10.i386 pangomm-2.14.0-2.fc10.i386
How reproducible: always
Steps to Reproduce: 1.In gedit input U+0C15 U+0C4D U+0C15 2.Press Delete key to delete the char 3.
Actual results: It can't delete the whole char,it will delete part of the char
Expected results: It will delete the whole char.
Additional info: All of chars in [te_IN][GSUB] has the same problem.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=499790
--- Comment #3 from Bug Zapper fedora-triage-list@redhat.com 2009-11-18 06:54:52 EDT ---
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=499790
Pravin Satpute psatpute@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |psatpute@redhat.com Version|10 |rawhide
--- Comment #4 from Pravin Satpute psatpute@redhat.com 2009-11-24 00:20:20 EDT --- i guess it will get fixed auto with harfbuzz and pango merger, moving to rawhide
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=499790
Parag pnemade@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |pnemade@redhat.com Version|13 |rawhide
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=499790
Akira TAGOH tagoh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |tagoh@redhat.com Flag| |needinfo?
--- Comment #6 from Akira TAGOH tagoh@redhat.com 2011-09-09 04:31:38 EDT --- No upstream bug for this?
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=499790
Fedora Admin XMLRPC Client fedora-admin-xmlrpc@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|behdad@fedoraproject.org |mclasen@redhat.com Flag|needinfo? |
--- Comment #7 from Fedora Admin XMLRPC Client fedora-admin-xmlrpc@redhat.com 2012-01-10 10:43:41 EST --- This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=499790
Fedora Admin XMLRPC Client fedora-admin-xmlrpc@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|mclasen@redhat.com |tagoh@redhat.com
--- Comment #9 from Fedora Admin XMLRPC Client fedora-admin-xmlrpc@redhat.com --- This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
https://bugzilla.redhat.com/show_bug.cgi?id=499790
Akira TAGOH tagoh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- External Bug ID| |GNOME Desktop 710695
https://bugzilla.redhat.com/show_bug.cgi?id=499790
Akira TAGOH tagoh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |NOTABUG Last Closed| |2014-10-09 05:16:55
--- Comment #10 from Akira TAGOH tagoh@redhat.com --- After taking a look at UAX#29 and the Pango code, current behavior is following the Unicode standard unfortunately.
Here is the details how the text segmentation is decided in Pango according to the standard:
First, the character type for the above characters are: U+0C15 OTHER LETTER U+0C4D NON SPACING MARK
Pango is looking at the grapheme boundary rule to decide if a character should be deleted by backspace key. it's defined as following in UAX#29:
* Break at the start(GB1) and end(GB2) of text. * Do not break between a CR and LF(GB3). Otherwise, break before(GB4) and after(GB5) controls. * Do not break Hangul syllable sequences(GB6,GB7,GB8). * Do not break between regional indicator symbols(GB8a). * Do not break before extending characters(GB9).
Only for extended grapheme clusters: * Do not break before SpacingMarks(GB9a), or after Prepend characters(GB9b). * Otherwise, break everywhere.
According to the table 2 in UAX#29, non-spacing mark is categorized into Extend. so it doesn't break *before* U+0C4D. but no rules to not break *after* Extend.
At this point, there are no standard that the software can refers the material to prevent that behavior. maybe good to escalate this to Unicode.org then.
fonts-bugs@lists.fedoraproject.org