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 684222 - add API to access unicode grapheme break property
add API to access unicode grapheme break property
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: i18n
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks: 689791
 
 
Reported: 2012-09-17 14:06 UTC by Christian Persch
Modified: 2018-05-24 14:34 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christian Persch 2012-09-17 14:06:42 UTC
We should add API to access the unicode character's GraphemeBreakProperty. 

This will be neccessary for the update to PCRE 8.32 (which uses this character property to implement \X ) and also be useful for pango.

Proposed API on wip/unicode-graphemebreak branch, using the same approach as the line break property API.
Comment 1 Behdad Esfahbod 2012-09-25 13:30:39 UTC
Looks good in general.  Two points:

1. The Hangul values can be calculated algorithmically.  That would be a huge saving and worth trying IMO.

2. In general I'm hesitant about adding more Unicode properties to glib, but that's a lost battle...  Grapheme break is useful to a wide variety of applications, so I like this proposal.
Comment 2 Behdad Esfahbod 2012-12-20 05:53:40 UTC
FWIW, I need this, and WordBreak and SentenceBreak properties for pango_break() rework.  I was thinking about adding them in Pango privately, but seems like maybe there's more use to them?
Comment 3 Christian Persch 2012-12-20 12:23:12 UTC
IMHO if we're going to have those tables in our stack, we might just as well have them in glib :-)

I'm not sure when I'm going to have time to work on this patch again, however, so if you need them *now* and don't want to work on glib, it should be fine to add them to pango first and later change to use glib once the API's there.
Comment 4 Behdad Esfahbod 2012-12-20 20:36:03 UTC
I'm in no rush either.  If I end up wanting to hack on it during the holidays, I'll go ahead and push them into glib.  The problem with these types is, they are really only relevant to the specific algorithms using them, which are in pango.  But who care...  The extra api is not gonna kill anyone.
Comment 5 Matthias Clasen 2014-06-28 17:02:04 UTC
Christian, do you have an updated branch for 7.0 ?
Comment 6 Christian Persch 2014-06-29 09:37:14 UTC
I haven't worked on this since the original wip branch, so no, I don't have an updated branch. The patch also needs work to at least handle hangul algorithmically (comment 1).
Comment 7 GNOME Infrastructure Team 2018-05-24 14:34:16 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/glib/issues/603.