Bug 18724 - Incorrect conjoining for Middle Korean jamo
Summary: Incorrect conjoining for Middle Korean jamo
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Text (show other bugs)
Version: 528+ (Nightly build)
Hardware: Macintosh OS X 10.5
: P2 Minor
Assignee: Nobody
URL: http://i18nl10n.com/korean/jamo.html
Keywords: InRadar
Depends on:
Reported: 2008-04-24 16:58 PDT by Chris Johnson
Modified: 2016-04-13 09:15 PDT (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Chris Johnson 2008-04-24 16:58:08 PDT
Middle Korean jamo (the individual parts of a hangul syllable block) that are not used in modern Korean are not conjoined correctly.  The initial consonant and vowel are combined into a syllable block, but any final consonant is left as a stray jamo.

Example: ᄫᆞᆼ (U+112B,U+119E,U+11BC)

With the correct fonts, this should be rendered as a single syllable block, but instead Webkit renders it as two units.

Cocoa text fields seem to get this right.  In fact, Safari renders the syllable block correctly in the location and search fields, just not in actual web content.

This is a minor issue of mostly academic/scholar interest.  However, the modern Jeju dialect does use one vowel not found in standard Korean, ㆍ(arae-a).  Thus, I get rendering errors for "Welcome", "daughter", and "man" on: http://en.wikipedia.org/wiki/Jeju_dialect

(On the test page I linked to above, Webkit also incorrectly renders the incomplete modern syllables.  This is a related but different issue - which Cocoa text fields appear to get wrong as well.)
Comment 1 Alexey Proskuryakov 2008-04-28 11:09:47 PDT
What are the fonts needed to display these characters? As far as I can tell, Mac OS X 10.5 doesn't have such.
Comment 2 Chris Johnson 2008-04-28 12:26:55 PDT
Sorry about that.  I should have included a link:


UnBatang has the relevant characters.
Comment 3 Chris Johnson 2008-04-28 15:20:48 PDT
(In reply to comment #2)

> UnBatang has the relevant characters.

(It's in the "un-fonts-core" package.)
Comment 4 Alexey Proskuryakov 2008-07-28 01:49:10 PDT
Comment 5 Myles C. Maxfield 2016-04-13 09:15:55 PDT
Using the UnBatang font on OS X El Capitan seems to show that this now works.

Is that correct, Chris?

I'll close this as resolved if I don't hear anything in a week or so.