Parenthesized Korean Character O Hu Letter
㈞ is a parenthesized Korean character form with codepoint U+321E.
U+321E
㈞ is a specific Unicode character: “PARENTHESIZED KOREAN CHARACTER O HU” (U+321E). It’s useful when you need this exact enclosed symbol for text, UI labels, or typographic design. Below you’ll find copy options and practical ways to use it.
Parenthesized Korean Character O Hu Letter Meaning
㈞ (U+321E) is an enclosed, parenthesized Korean character symbol. In Unicode terms, it’s represented by the name “PARENTHESIZED KOREAN CHARACTER O HU,” and it belongs to the “Enclosed & Circled” category. Practically, its meaning is usually tied to precise typography or to systems that require a particular precomposed symbol rather than separate characters. Because it’s a standalone Unicode character, using it directly helps preserve the intended glyph shape across platforms that support it. When you need the exact look in documents, web content, game UI, or icon-like typography, copying this single character avoids rendering inconsistencies.
Common uses
- •Typography: keeping a specific precomposed enclosed glyph in layouts
- •UI labels: using the exact symbol in buttons, badges, or menus
- •Document publishing: matching a reference document that uses this character
- •Social posts: sharing the exact Unicode glyph without substitution
- •Developer use: inserting the character reliably via Unicode codepoint
Examples
㈞ PARENTHESIZED KOREAN CHARACTER O HU
- ㈞Status: ㈞
- ㈞Option ㈞ selected
- ㈞Ref: ㈞
- ㈞Menu item (㈞)
- ㈞Korean label ㈞
Variations
Technical codes
| Unicode | U+321E | |
| HTML Entity | ㈞ | |
| HTML Code | ㈞ | |
| CSS | \321E |
FAQ
What is the Unicode codepoint for ㈞?
㈞ is Unicode codepoint U+321E.
How can I copy ㈞ reliably in code?
Use its codepoint or escapes: HTML entity ㈞, CSS escape \\321E, or JavaScript escape \\u{321E}.
What does “PARENTHESIZED KOREAN CHARACTER O HU” mean?
It is the Unicode character name for this specific parenthesized enclosed Korean character glyph.
Why doesn’t it look right on my device?
The font you’re using may not support this glyph. Try a Unicode-capable font or verify codepoint U+321E is being rendered.