Description
Classify only ordinary space U+0020 and no-break spaces U+00A0/U+202F into their Unicode line-break classes; not a full Unicode line-breaking engine.
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 only ordinary space U+0020 and no-break spaces U+00A0/U+202F into their Unicode line-break classes; not a full Unicode line-breaking engine.
When to use this tool
Use Text: Whitespace Nobreak Vs Breakable 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 U+00A0 and U+202F as GL-no-break and U+0020 as SP-breakable; return knownSpace for those three cases and other otherwise. Validate a Unicode scalar and return fields inside result.1
Unicode line-break properties classify spaces, while actual break opportunities also depend on surrounding text and algorithm rules.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| codepoint | Codepoint | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| result | Result | Required. Object. |
{
"input": {
"codepoint": 160
},
"output": {
"result": {
"knownSpace": true,
"lineBreakClass": "GL-no-break"
}
}
}Limitations and assumptions
- The lookup is deliberately limited, not a complete Unicode line-break property table. It does not decide every break opportunity or measure a rendered space.
- 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
-
Calculation and input contract: text/whitespace-nobreak-vs-breakable-label — tool.io
-
Unicode Standard Annex #14: Line Breaking Algorithm — Unicode Consortium
Similar or alternative tools
- 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.
- 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.