Skip to content

Main content

Text Leading Space Indentation Width Tool

Compute text leading space indentation width from explicit bounded inputs.

Loading tool…

Description

Count initial ASCII spaces and tabs until another character occurs.

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.

Count initial ASCII spaces and tabs until another character occurs.

When to use this tool

Use Text Leading Space Indentation Width 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 line, tabWidth. 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 columns, characters. Use the output convention below.

Count initial ASCII spaces and tabs until another character occurs. Return characters consumed and columns, expanding each tab to the next positive tabWidth stop from column zero; tabWidth is one through 32.1

Input fieldMeaning and unitsAccepted input
lineLineRequired. Text; maximum UTF-16 length 8192.
tabWidthTab WidthRequired. Safe integer; minimum 1; maximum 32.
Output fieldInterpretationReturned shape
columnsWidth under the supplied tab-stop model.Required. Safe integer.
charactersNumber of initial ASCII spaces and tabs consumed.Required. Safe integer.
json
{
  "input": {
    "line": " \tx",
    "tabWidth": 4
  },
  "output": {
    "columns": 4,
    "characters": 2
  }
}

Limitations and assumptions

  • Characters count indentation tokens while columns reflect the supplied stop model. Other Unicode whitespace and actual terminal display, font metrics, and mixed-line indentation are not processed.
  • 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/text-leading-space-indentation-width — tool.io

Similar or alternative tools