Pre-1933 Orthography Korean sample

This document is out of date. I've put a lot of efforts into Mozilla to make it render Korean text represented in U+1100 Korean letters and Mozilla 1.4.1 and Mozilla 1.5 (not yet released) will have a much better Korean support than any other browsers.

Below are 5 Hangul syllables (4 middle and 1 modern) represented using Hangul Jamos in U+1100 block. Currently, only Mozilla for Unix/X11 with Hangul fonts for Korean xterm ( Hanterm) available here can render them correctly.

The relevant file in Mozilla source is intl/uconv/ucvko/nsUnicodeToX11Johab.cpp adapted from Hanterm source and its adapation to Java.

ᄊᆞᆷ ᄒᆞᆫ글 ᄀᆞᇹ ᄫᆞᆼ

MS IE 5.5 and MS IE 6.0 may be able to render this page correctly if Old Hangul fonts (available on Korean MS Word/Office 2000/2002 plus-pack CD or here) are installed.

Some other examples

Modern incomplete syllables such as ᅟᅥᆻ (U+115F U+1165 U+11BB) and ᅟᅡᆻ (U+115F U+1161 U+11BB) are not rendered as intended by most web browsers. The only browser that gets this right is Mozilla for Unix/X11 and Mozilla/Windows with UnBatang opentype font by PARK Won-kyu.

Comparison of various normalization forms applied to modern Hangul syllables
Normalization Form
NFC/NFKC
U+AE4DU+AD11 U+AD1CU+CC2E
NFKD(old) ᄀ각 고ᅡᆼ 고ᅡᅵᆫ 찬ᇂ
U+1100 U+1100 U+1161 U+11A8 U+1100 U+1169 U+1161 U+11BC U+1100 U+1169 U+1161 U+1175 U+11AB U+110E U+1161 U+11AB U+11C2
NFKD(new) 깍광괜 찮
U+1101 U+1161 U+11A8 U+1100 U+116A U+11BC U+1100 U+116B U+11AB U+110E U+1161 U+11AD
NFD 깍광괜 찮
U+1101 U+1161 U+11A8 U+1100 U+116A U+11BC U+1100 U+116B U+11AB U+110E U+1161 U+11AD

In NFC, modern complete syllables are represented with precomposed characters in the Hangul syllable block beginning at U+AC00. On the other hand, NFD and NFKD represent Hangul syllables with Hangul conjoining jamos in U+1100 block. Because compatibility decomposition of consonant clusters and vowel clusters into basic consonants (14 modern and 3 obsolete) and basic vowels (10 modern and 1 obsolete) has been removed from the Unicode standard by the request of RoK, NFD and NFKD are identical in Unicode 3.0. However, that was not the case in Unicode 2.0 where complex Jamos are compatibly decomposed into basic Jamos.

Screenshots

Valid HTML 4.01!