Description
Classify the three Unicode private-use areas without assigning character semantics or confusing supplementary-plane terminal noncharacters with private use.
Text positions can be measured in UTF-16 code units, Unicode code points, grapheme clusters, or modeled display columns. These coordinates are not interchangeable. Invisible markers and delimiter policies can also affect interpretation even when a string looks unchanged, so the chosen representation needs to stay explicit.
Classify the three Unicode private-use areas without assigning character semantics or confusing supplementary-plane terminal noncharacters with private use.
When to use this tool
Use Text: Unicode Private Use Plane Label when you need the stated marker, coordinate, delimiter, or normalization operation under an explicit text representation.
How to use the tool and how it works
- Enter codepoint. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read result. Expand result to inspect the returned fields.
Label integer codepoint as BMP, plane-15, or plane-16 private use within the implemented ranges, or none otherwise, returning privateUse and area inside result.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| codepoint | Integer zero through U+10FFFF; the numeric lookup also accepts surrogate integers. | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| result | Result | Required. Object. |
{
"input": {
"codepoint": 57344
},
"output": {
"result": {
"privateUse": true,
"area": "BMP"
}
}
}Limitations and assumptions
- The numeric gate accepts values zero through U+10FFFF, including surrogate integers that simply return none. Private-use status does not define meaning, assignment, glyph support, or interchange agreement.
- Outputs are nested inside result. The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
Alternative or Complementary methods
Choose the coordinate system required by the consumer. Use a full parser, renderer, or segmentation method when a local marker or delimiter rule cannot determine the complete text behavior.
References
Similar or alternative tools
- Text: Bidi Control Visible Name Label
Name one of the twelve Unicode Bidi_Control code points for visible inspection, without applying the bidirectional layout algorithm.
- Text: Unicode Bom Vs Zw Nobreak Label
Distinguish positional interpretations of Unicode FEFF without claiming a decoded scalar proves a byte-level BOM; internal FEFF is a legacy ZWNBSP use.