[Webkit-unassigned] [Bug 138618] New: Some Hangul consonants (U+114C, U+112B, etc) are not combined with other Hangul combining jamos

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=138618

            Bug ID: 138618
           Summary: Some Hangul consonants (U+114C, U+112B, etc) are not
                    combined with other Hangul combining jamos
    Classification: Unclassified
           Product: WebKit
           Version: 528+ (Nightly build)
          Hardware: Unspecified
                OS: Mac OS X 10.9
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Layout and Rendering
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: jshin at chromium.org
                CC: behdad at google.com, mmaxfield at apple.com

Created attachment 241364
  --> https://bugs.webkit.org/attachment.cgi?id=241364&action=review
Left: correct (Chrome 41), Right: Incorrect (Safari 7.1)

OS: Mac OS 10.9
Safari: Version 7.1 (9537.85.10.17.1)

Reproduction step:

1. Install 'NotoSansCJK' (either SuperOTC or Regular OTC) available at http://www.google.com/get/noto/cjk.html
2. Start Safari
3. Go to the following URL
   data:text/html;charset=utf-8,<span%20style="font-family:%20Noto%20Sans%20CJK%20KR;">ᅌᅥᆫᄫᅳᆯ&#x1147;&#x116e;</span>

Expected (see the attachment) 

You see three syllables the first which are made up of three Hangul combining Jamos and the last of which is made of two Hangul Jamos 

Actual (see the screenshot )
Three Jamos enumerated linearly for the first two syllables and two Jamos enumerated linearly for the last syllable. 

Additional information:

Jamos in the step 3 are:

U+114C U+1165 U+11AB
U+112B U+1173 +U11AF
U+1147 U+116E

A more comprehensive example is found at http://ko.wikisource.org/wiki/훈민정음언해 where most combinations are rendered correctly, but some syllables starting with consonants such as U+114C, U+112B and U+1147 are incorrectly shaped. (there are a couple of other issues, but I'll file them separately)

Chrome 38.x (that also uses CoreText) has the same issue, but Chrome 40.x (that switched to use harfbuzz) does not have this issue any more.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20141111/93e7a256/attachment-0002.html>