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 96314 - Add jamo normalization to hangul-fc shaper
Add jamo normalization to hangul-fc shaper
Status: RESOLVED NOTABUG
Product: pango
Classification: Platform
Component: hangul
1.1.x
Other Linux
: Normal normal
: 1.6.0
Assigned To: Changwoo Ryu
pango-maint
Depends on:
Blocks:
 
 
Reported: 2002-10-20 14:07 UTC by Jungshik Shin
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jungshik Shin 2002-10-20 14:07:30 UTC
My working patch for bug 95708 includes normalize_jamo() in hangul-xft.
Eventually, this routine and associated functions have to be put in a 
sepate file and be made
accessible from rendering functions in both hangul-x.c and hangul-xfs.c.

normalize_jamo() does (copied from bug 95708) :

  - gunichar* normalize_jamo(const gunichar* in, int *len):
    1. Normalize (regularize) a jamo sequence to put it in a regular
       syllable form defined Unicode 3.2 section 3.11 to the extent
       that it's useful in rendering by render_func's().

    2. Replace a compatibly decomposed Jamo sequence (unicode 2.0 
       definition) with a 'precomposed' Jamo cluster (with codepoint
       of its own in U+1100 block). For instance, a seq.
       of U+1100, U+1100 is replaced by U+1101. It actually
       more than Unicode 2.0 decomposition map suggests.
       For a Jamo cluster made up of three basic Jamos
       (e.g. U+1133 : Sios, Piup, Kiyeok), not only
        a sequence of Sios(U+1109), Piup(U+1107) and 
       Kiyeok(U+1100) but also two more sequences,
       {U+1132(Sios-Pieup), U+1100(Kiyeok) and {Sios(U+1109),
        U+111E(Piup-Kiyeok)} are mapped to U+1133.

    3. the result is returned in a newly malloced(g_new'd)
       gunichar*. A calling function has to g_free it.
Comment 1 Jungshik Shin 2002-10-20 14:09:42 UTC
Like bug 96300, I prefer to put this off until bug 95708 is resolved
partly because I want to introduce too much interdependency among
bugs. However, I'm open to a different opinion. 
Comment 2 Owen Taylor 2002-11-02 05:42:48 UTC
Moving bugs to new hangul component
Comment 3 Noah Levitt 2003-11-14 01:23:28 UTC
Is this a dup of bug 100456?
Comment 4 Changwoo Ryu 2003-11-14 11:42:36 UTC

*** This bug has been marked as a duplicate of 100456 ***
Comment 5 Changwoo Ryu 2003-11-14 11:44:27 UTC
oops sorry marked RESOLVED DUPLICATE by mistake..
Comment 6 Noah Levitt 2003-11-14 15:29:56 UTC
Can someone clarify the status of this bug in light of:

 - hangul-x.c no longer existing
 - hangul-xft.c having been moved to hangul-fc.c
 - bug 100456
 - bug 123406
 - this bug not having been touched in a year
Comment 7 Owen Taylor 2004-02-21 18:33:19 UTC
I think this is still relevant, bug 95708 has been WONTFIX'ed,
so this needs to be extracted from there.