Description
Decode one four-digit nonsurrogate properties-style Unicode escape.
Parsing depends on the chosen grammar, character encoding, offset unit, and treatment of escapes and delimiters. UTF-16 code-unit positions, Unicode code points, and UTF-8 byte offsets are not interchangeable. A boundary or token check supplies one part of a parser rather than validating an entire file.
Decode one four-digit nonsurrogate properties-style Unicode escape.
When to use this tool
Use Properties Unicode Escape Four Digits when you need the stated token boundary, offset, prefix, delimiter, or count component inside a larger parsing workflow.
How to use the tool and how it works
- Enter token. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read codeUnit, character. Use the output convention below.
Accept exactly backslash-u followed by four ASCII hex digits, reject UTF-16 surrogate values, and return codeUnit plus String.fromCharCode(codeUnit).1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| token | Complete literal token in the grammar stated above. | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| codeUnit | Nonsurrogate UTF-16 code unit only; surrogate escapes are rejected. | Required. Safe integer. |
| character | Decoded character or preserved original token as described above. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"token": "\\u0041"
},
"output": {
"codeUnit": 65,
"character": "A"
}
}Limitations and assumptions
- This handles one nonsurrogate UTF-16 code unit. Paired surrogate escapes, repeated-u forms, general Java properties syntax, and file-level encoding/continuations are unsupported.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Choose a parser for the intended complete grammar when context, nesting, encodings, or semantic validation matters. Keep byte, code-unit, and code-point coordinates explicit when combining results.
References
Similar or alternative tools
- Shell Dollar Quote Unicode Width
Inspect a supplied Bash ANSI-C quoting Unicode escape without executing shell text.
- Comment Prefix Byte Count
Count the UTF-8 bytes of an explicit comment prefix without language-specific comment parsing.