Skip to content

Main content

Word Joiner Versus No Break Space Tool

Calculate word joiner versus no break space from explicit caller-supplied inputs.

Loading tool…

Description

Classify a valid scalar as word-joiner for U+2060, no-break-space for U+00A0, or other.

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 a valid scalar as word-joiner for U+2060, no-break-space for U+00A0, or other.

When to use this tool

Use Word Joiner Versus No Break Space 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 scalar. 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 kind, visibleSpace, preventsBreak. Inspect visibleSpace, preventsBreak before interpreting the associated values.

Classify a valid scalar as word-joiner for U+2060, no-break-space for U+00A0, or other. Set visibleSpace only for U+00A0 and preventsBreak only for those two recognized scalars.1

Input fieldMeaning and unitsAccepted input
scalarScalarRequired. Safe integer.
Output fieldInterpretationReturned shape
kindKindRequired. Text; maximum UTF-16 length 8192.
visibleSpaceVisible SpaceRequired. Boolean.
preventsBreakTrue only for the two recognized scalars; not a complete line-break decision.Required. Boolean.
json
{
  "input": {
    "scalar": 8288
  },
  "output": {
    "kind": "word-joiner",
    "visibleSpace": false,
    "preventsBreak": true
  }
}

Limitations and assumptions

  • These flags cover two characters only. False preventsBreak is not a complete line-break permission, and actual wrapping requires surrounding text and a line-breaking implementation.
  • 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/word-joiner-versus-no-break-space — tool.io

Similar or alternative tools