Tool
Korean NFC, NFD, and jamo
Text that looks the same can use different code points. This page shows String.normalize output and counts syllables, combining jamo, and compatibility jamo.
Normalization runs in the browser. The paste is not sent to GearDel.
What the counts are
NFC and NFD are String.normalize in this browser. NFC composes Hangul jamo into syllables where Unicode says they compose. NFD splits syllables into jamo.
NFKC/NFKD also fold compatibility characters. Hangul compatibility jamo (U+3130–U+318F), often seen in older encodings or some IMEs, can change under NFKC.
Syllable count is precomposed Hangul syllables (U+AC00–U+D7A3). Combining jamo are U+1100–U+11FF, U+A960–U+A97F, and U+D7B0–U+D7FF. Compatibility jamo are counted separately.
Graphemes use Intl.Segmenter when the browser has it. A composed syllable is one grapheme; a visible syllable made of several jamo is still one grapheme if the segmenter treats it as one.
The code-point dump lists at most 80 characters so the page stays readable. The counts still cover the whole paste, up to 200,000 code points.
What this page does not do
- It does not guess whether a file came from macOS. NFD is common there, but the numbers here are only this paste.
- It does not implement a morphological analyzer or a Korean spell checker.
- It does not encode EUC-KR. Use the character/byte page for that.