Encoding Table
This table shows the exact bytes used to represent TIBETAN SIGN RDEL DKAR GSUM in each encoding. Unicode encodings (UTF-8, UTF-16, UTF-32) support every character; legacy encodings only cover a limited character set and show "not supported" when a character falls outside their range.
| Encoding | Bytes (Hex) | Bytes (Decimal) | Byte count |
|---|---|---|---|
| UTF-8 | E0 BC 9C | 224 188 156 | 3 |
| UTF-16 LE | 1C 0F | 28 15 | 2 |
| UTF-16 BE | 0F 1C | 15 28 | 2 |
| UTF-32 LE | 1C 0F 00 00 | 28 15 0 0 | 4 |
| UTF-32 BE | 00 00 0F 1C | 0 0 15 28 | 4 |
| ASCII | not supported | ||
| Latin-1 (ISO-8859-1) | not supported | ||
| Windows-1252 | not supported | ||
| ISO-8859-2 (Latin-2) | not supported | ||
| ISO-8859-5 (Cyrillic) | not supported | ||
| KOI8-R | not supported | ||
| Shift-JIS | not supported | ||
| EUC-JP | not supported | ||
| GBK | not supported | ||
| Big5 | not supported |
Escape Sequences
How to reference this character in source code, markup, and URLs.
View the glyph in different fonts and scripts on our sibling site.
View U+0F1C on CharLookup.com ↗UTF-8 Binary Breakdown
UTF-8 encodes this character as 3 bytes. The leading 1110 prefix on byte 1 signals a 3-byte sequence. Bytes 2 and 3 begin with 10 to mark them as continuation bytes.
Unicode Properties
- Unicode Version
- Introduced in Unicode 2.0
- Bidi Class
- L — Left-to-Right