Skip to content

Main content

Text: Unicode Noncharacter Codepoint Tool

Inspect one Unicode code point for the designated 66 permanent noncharacters; noncharacters remain scalar values and are not necessarily encoding errors.

Loading tool…

Description

Inspect one Unicode code point for the designated 66 permanent noncharacters; noncharacters remain scalar values and are not necessarily encoding errors.

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.

Inspect one Unicode code point for the designated 66 permanent noncharacters; noncharacters remain scalar values and are not necessarily encoding errors.

When to use this tool

Use Text: Unicode Noncharacter Codepoint 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

  1. Enter codepoint. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read result. Expand result to inspect the returned fields.

Flag U+FDD0–FDEF and values ending in FFFE or FFFF within each plane as noncharacter, and return the integer plane inside result.1

Input fieldMeaning and unitsAccepted input
codepointInteger zero through U+10FFFF; this lookup is not a scalar validator.Required. Safe integer.
Output fieldInterpretationReturned shape
resultResultRequired. Object.
json
{
  "input": {
    "codepoint": 1114111
  },
  "output": {
    "result": {
      "noncharacter": true,
      "plane": 16
    }
  }
}

Limitations and assumptions

  • The input gate accepts surrogate integers as well as scalar values. Noncharacter false is not proof of a valid assigned character, safe identifier, or supported glyph.
  • 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

  1. Calculation and input contract: text/unicode-noncharacter-codepoint — tool.io

Similar or alternative tools