search

rizwan3d / noto

Automatically exported from code.google.com/p/noto
1 stars 0 forks source link

Some Old Hangul leading consonants are not combined properly : Safari and Chrome 38 on Mac #196

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Almost a verbatim copy of my bug report against webkit (for Safari ; 
https://bugs.webkit.org/show_bug.cgi?id=138618 ) 

OS: Mac OS 10.9
Safari: Version 7.1 (9537.85.10.17.1)
Chrome: 38.x 

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.

After switching to harfbuzz from CoreText, Chrome 40 does not have this problem 
any more. 

This bug is just to keep track of a known issue (even though it's not a font 
bug).

Original issue reported on code.google.com by jungs...@google.com on 11 Nov 2014 at 7:27

GoogleCodeExporter commented 9 years ago 
Left : Chrome 41.x (correct)
Right: Safari (incorrect), Chrome 38 has the same problem.

Original comment by jungs...@google.com on 11 Nov 2014 at 7:28

Attachments:

GoogleCodeExporter commented 9 years ago 
Isn't this simply because these environments do not support the '{l,v,t}jmo' 
GSUB features? Remember that the combining jamo lookups were removed from the 
'calt' GSUB feature for the Version 1.001 fonts.

Original comment by ken.lu...@gmail.com on 12 Nov 2014 at 2:29

GoogleCodeExporter commented 9 years ago 
From the description, sounds like CoreText doesn't support this?  I doubt 
that's the case, given that the fonts work in TextEdit (or so I thought?).  At 
any rate, needs testing and reporting to Apple IMO.

Original comment by behdad@google.com on 19 Nov 2014 at 12:14

GoogleCodeExporter commented 9 years ago 
According to an Apple engineer in the Webkit bug, it does not work in TextEdit 
either.  And, I've just confirmed that it does not on Mac OS 10.9. I'll try 
10.10 later. So, it should be a CoreText issue. Thanks god, we switched to 
harfbuzz in Blink. 

Anyway, they put this into their internal bug tracker (radar).

Original comment by jshin@chromium.org on 11 Feb 2015 at 7:17