Indentation Run Profiler
Profile literal indentation per logical line; counts tabs separately rather than infer visual indentation width.
Description
Profile literal indentation per logical line; counts tabs separately rather than infer visual indentation width.
Indentation profiles distinguish literal spaces from tabs at the start of each line. Counts of stored characters do not imply a rendered indentation width.
When to use this tool
Profile literal indentation per logical line; counts tabs separately rather than infer visual indentation width.
- Prepare the supplied text fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter text. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.lines. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
For every line, capture the maximal leading run of ASCII spaces/tabs and return the prefix plus separate space and tab counts.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| text | text. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.lines | The lines list in the ordering and representation described above. |
{
"input": {
"text": " a\n\tb"
},
"output": {
"result": {
"lines": [
{
"line": 1,
"prefix": " ",
"spaces": 1,
"tabs": 0
},
{
"line": 2,
"prefix": "\t",
"spaces": 0,
"tabs": 1
}
]
}
}
}Limitations and assumptions
- Tab stops and visual alignment are not measured. Other whitespace characters end the prefix, and empty lines, including a terminal empty line, still receive a row.
- Text offsets and lengths use UTF-16 code units unless explicitly described as bytes or code points. CRLF, CR and LF are recognized as line endings; a terminal newline creates a final empty line in the shared line model.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Ordinary string lists have at most 128 entries of at most 128 code units each; numeric lists and matrices have separate bounded size checks. Nonfinite results and excessively large serialized outputs are rejected.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Use a parser or language-aware editor when quoting, syntax or nested constructs matter. For plain text transforms, keep UTF-16 offsets, Unicode code points, grapheme clusters and UTF-8 byte offsets distinct; apply changes to the same source version used to calculate spans.
References
Similar or alternative tools
- Line Run Length Table
Tabulate consecutive equal hard-line content runs with inclusive one-based line bounds.
- acronym
Build an acronym from the uppercase first letter of each whitespace-separated word.