RUNIC LETTER LONG-BRANCH-OSS O·U+16AC

Character Information

Code Point
U+16AC
HEX
16AC
Unicode Plane
Basic Multilingual Plane
Category
Other Letter

Character Representations

Click elements to copy
EncodingHexBinary
UTF8
E1 9A AC
11100001 10011010 10101100
UTF16 (big Endian)
16 AC
00010110 10101100
UTF16 (little Endian)
AC 16
10101100 00010110
UTF32 (big Endian)
00 00 16 AC
00000000 00000000 00010110 10101100
UTF32 (little Endian)
AC 16 00 00
10101100 00010110 00000000 00000000
HTML Entity
ᚬ
URI Encoded
%E1%9A%AC

Description

U+16AC (RUNIC LETTER LONG-BRANCH-OSS O) is a unique character from the Unicode standard that represents a specific runic letter in the Old English Futhark alphabet. It holds significant cultural, linguistic, and technical contexts, particularly in the study of Anglo-Saxon history and language. In digital text, U+16AC is typically used to accurately represent the RUNIC LETTER LONG-BRANCH-OSS O, enabling scholars and researchers to engage with historical documents, artifacts, and inscriptions that employ this runic letter. By incorporating this character in digital texts, it ensures the preservation of linguistic and cultural heritage while facilitating a deeper understanding of the past. The RUNIC LETTER LONG-BRANCH-OSS O is part of the Old English Futhark alphabet, which was used by the Anglo-Saxons from approximately the 5th to the 12th centuries. This runic alphabet consists of 24 letters and was primarily inscribed on stones, wood, or metal objects for various purposes such as commemorations, declarations, or identifications. As a result, U+16AC plays an essential role in the transcription and interpretation of these historical artifacts, providing valuable insights into the Old English language, runic tradition, and early Anglo-Saxon culture.

How to type the symbol on Windows

Hold Alt and type 5804 on the numpad. Or use Character Map.

  1. Step 1: Determine the UTF-8 encoding bit layout

    The character has the Unicode code point U+16AC. In UTF-8, it is encoded using 3 bytes because its codepoint is in the range of 0x0800 to 0xffff.

    Therefore we know that the UTF-8 encoding will be done over 16 bits within the final 24 bits and that it will have the format: 1110xxxx 10xxxxxx 10xxxxxx
    Where the x are the payload bits.

    UTF-8 Encoding bit layout by codepoint range
    Codepoint RangeBytesBit patternPayload length
    U+0000 - U+007F10xxxxxxx7 bits
    U+0080 - U+07FF2110xxxxx 10xxxxxx11 bits
    U+0800 - U+FFFF31110xxxx 10xxxxxx 10xxxxxx16 bits
    U+10000 - U+10FFFF411110xxx 10xxxxxx 10xxxxxx 10xxxxxx21 bits
  2. Step 2: Obtain the payload bits:

    Convert the hexadecimal code point U+16AC to binary: 00010110 10101100. Those are the payload bits.

  3. Step 3: Fill in the bits to match the bit pattern:

    Obtain the final bytes by arranging the paylod bits to match the bit layout:
    11100001 10011010 10101100