Formatting: Thin Space Unit Join Policy Tool

Description

Require nonempty value/unit strings without CR or LF and select thin, narrow-nobreak, space or none as the separator.

A unit label is text describing a quantity's intended scale. Joining tokens, adding powers or choosing spacing changes presentation; it does not convert the quantity, validate dimensional compatibility or verify a unit registry entry.

Require nonempty value/unit strings without CR or LF and select thin, narrow-nobreak, space or none as the separator.

When to use this tool

Use Formatting: Thin Space Unit Join Policy when you need a specific quantity-and-unit text convention.

How to use the tool and how it works

Enter valueText, unitText, spacing. 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.

Require nonempty value/unit strings without CR or LF and select thin, narrow-nobreak, space or none as the separator.^[1]

Input field	Meaning and units	Accepted input
valueText	Value Text	Required. Text. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units.
unitText	Unit Text	Required. Text. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units.
spacing	Spacing	Required. Text; one of "thin", "narrow-nobreak", "space", "none". Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units.

Output field	Interpretation	Returned shape
result	Object containing the calculated members; expand to inspect the fields below.	Required. Object.
result.label	Literal label; no independent factual or authorization verdict.	Calculated result member: string.

json

{
  "input": {
    "valueText": "12",
    "unitText": "m",
    "spacing": "thin"
  },
  "output": {
    "result": {
      "label": "12 m"
    }
  }
}

Limitations and assumptions

This joins text without numerical parsing or unit validation. Thin space and narrow no-break space differ in wrapping behavior and actual rendering depends on the destination.
Outputs are nested inside result. 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

Use a unit-aware calculation for actual conversion and dimensional checks. Select a destination-appropriate typography and retain the intended unit meaning when preparing labels.

References

Calculation and input contract: format/thin-space-unit-join-policy — tool.io

Similar or alternative tools

Measurement Unit Product Dot Policy
Join tokens with a middle dot or ordinary space.
Measurement Square Bracket Unit Token
Append it inside square brackets after value.