What ﾣ means
It represents ㄳ, a Korean consonant cluster. In modern Korean, this cluster can serve as the final consonant part of a syllable. ﾣ is its halfwidth compatibility form, kept for older text formats.
The encoding history reaches back to Korean computer standards. In 1974, KS C 5601 defined 51 basic Jamo in a 7-bit N-byte scheme. Unicode material traces the later halfwidth arrangement to the 1987/1992 Annex 4 lineage. These forms carried Korean text through older computing formats; their role today is compatibility.
Why does ﾣ change into ㄳ?
Compatibility normalization can change ﾣ to ㄳ. They represent the same Korean consonant cluster in width-related forms. The separate conjoining Jamo are building pieces used to assemble Hangul syllables. Keep the halfwidth form only when a text format needs that distinction.
Why does ﾣ show as a box?
Some fonts lack the right glyph or width handling. A 2020 Noto CJK issue recorded missing-glyph and incorrect-width display on Android 10 with Samsung Note 10, and in Word 2016 on Windows 10. A box or oddly sized mark can be a display problem rather than a different character.
Technical and archival: it belongs to legacy text formats, not ordinary Korean conversation.
Do not use it as ordinary Korean text; it may appear unfamiliar or fail to display.
Part of the collection
Who writes ﾣ
Loading…
Don't confuse it with
1Related characters
2
ㄱㅅ These are two separate Korean compatibility Jamo, the component consonants represented together by the single cluster ㄳ.
Combination ideas
1Questions people ask
1Can I type ﾣ with a Korean keyboard?
No. Standard Korean input methods do not provide a way to enter halfwidth Jamo, so this character is generally encountered in older text or compatibility data.
More like this
10
How to type or find ﾣ
- Search it as
- FFA3 · ㄳ · halfwidth jamo · Korean jamo · N-byte Hangul · legacy Hangul · narrow Hangul
- Shows up in
- Anything that takes text · its shape is whatever your font draws
ﾣ\FFA3Codes and encoding1 code points
A visible symbol can contain several code points. JS .length counts UTF-16 units; UTF-8 counts bytes.