[HarfBuzz] an issue regarding discrepancy between Korean and Unicode standards

[Behdad Esfahbod]

On 13-04-05 06:45 AM, Dohyun Kim wrote:
> 2013/4/5 Dohyun Kim <nomosnomos at gmail.com>:
>> Sorry for the noise.
>> I have booted on Windows machine and tested uniscribe a bit.  My guess
>> on how uniscribe works on Hangul is:
>>
>> 1. decompose hangul syllables to jamos
>>
>> 2. compose single jamos to composite jamo as possible as can be
>>     eg., U+1100 U+1100 => U+1101
>>     Note:  mapping table for this composition is available at
>>       ftp://ktug.org/ktug/hcr-lvt/composejamotojamo.map
>>
> 
> Well, after a bit more test, it turned out that this second process is
> not what uniscribe does.  Sorry for my wrong information.  I have
> guessed this on the basis of old unicode standard.  Recently unicode
> also does not recommend to use multiple single jamos to get composite
> jamo.
> 
> Instead, uniscribe inserts fillers (U+115F U+1160) around single
> lonely jamo which do not make up syllable block.

Interesting.  So, for a lone T jamo, both 115F and 1160 are inserted?


behdad

>> 3. compose jamos to hangul syllable as possible as can be
>>    Note:  this process complies with KSC 1026-1.  In other words, jamo
>> sequence <L V> in <L V OT> is *not* converted to LV, where L means
>> leading consonant, V means medial vowel, OT means *old* trailing
>> consonant (U+11C3..U+11FF U+D7CB..U+D7FB), and LV means Hangul
>> syllable equivalent to L V.
>>
>> 4. apply opentype layout features
>>
>> It is somewhat complicated but gives perfect result.  It satisfies
>> both the Korean and Unicode standards.  Nevertheless, what current
>> hafbuzz does is quite excellent as well and I am satisfied with it.  I
>> am reporting just for reference.
>>
>> Best,
>>
>> --
>> Dohyun Kim
>> College of Law, Dongguk University
>> Seoul, Republic of Korea
> 
> 
> 
> --
> Dohyun Kim
> College of Law, Dongguk University
> Seoul, Republic of Korea
> 

-- 
behdad
http://behdad.org/