𑒼

Tirhuta Vowel Sign O

U+114BC
SMP Unicode 7.0
Character 𑒼
Decimal 𑒼
Hex 𑒼

Classification

Unicode properties assigned to this character by the Unicode Consortium. The codepoint is its unique numeric identifier. Category, block, and script determine how text systems render and process it.

Codepoint
U+114BC
Decimal
70844
Plane
SMP — Supplementary Multilingual Plane
Category
Spacing Mark (Mc)
Block
Tirhuta
Script
Tirhuta
Bidi class
L Left-to-Right
East Asian Width
N Narrow
Properties
Alphabetic ID Continue

Looks Like (Confusables)

Characters that are visually similar — relevant for security, font design, and homoglyph detection.

Encodings & Escape Sequences

Every Unicode character can be represented in multiple ways depending on context. HTML entities let you embed it safely in web pages. UTF-8 bytes are what gets stored on disk and sent over the network. Escape sequences let you reference it in source code without pasting the raw glyph. All formats below refer to the same character — Tirhuta Vowel Sign O.

Click the copy icon to copy any value.

Format Value
HTML Decimal
𑒼
HTML Hex
𑒼
UTF-8 Hex Bytes
F0 91 92 BC
UTF-16 Hex Bytes
D8 05 DC BC
UTF-32 Hex
000114BC
CSS Escape
\114BC
JavaScript Escape
\uD805\uDCBC
Python Escape
\U000114BC
URL Encoded
%F0%91%92%BC
Have a string containing this character? Decode it to see every codepoint. UnicodeDecoder →

Normalization Forms

Unicode defines four normalization forms that affect how characters with diacritics, compatibility variants, and combining marks are represented. This character has a non-trivial normalization — the forms below differ from its codepoint. Mismatched normalization is the most common cause of failed string comparisons across systems.

NFC = Canonical Decomposition then Canonical Composition (preferred for storage) · NFD = Canonical Decomposition · NFKC/NFKD = Compatibility forms (fold variants like fi → fi)

Decomposition

This character can be broken down into a sequence of simpler Unicode codepoints. This is a canonical decomposition — the character and its components are semantically identical and interchangeable in NFC/NFD normalization.