Literal Token Spacing Audit
Audit ASCII-space runs around every overlapping literal token; document edges pass, tabs are not counted as spaces.
Description
Audit ASCII-space runs around every overlapping literal token; document edges pass, tabs are not counted as spaces.
Spacing around a literal token can be audited without changing the text. A narrow definition of space keeps the pass/fail rule predictable.
When to use this tool
Audit ASCII-space runs around every overlapping literal token; document edges pass, tabs are not counted as spaces.
- Prepare the supplied text, token, minimumSpaces 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, token, minimumSpaces. 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.matches. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
At every overlapping token occurrence, count consecutive ASCII spaces immediately to its left and right. Compare each count with minimumSpaces, treating the beginning or end of the entire text as an automatic pass on that side.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| text | text. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| token | token. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| minimumSpaces | minimum spaces. | Integer from 0 to 128 inclusive |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.matches | The matches list in the ordering and representation described above. |
{
"input": {
"text": "a + b",
"token": "+",
"minimumSpaces": 1
},
"output": {
"result": {
"matches": [
{
"offset": 2,
"leftSpaces": 1,
"rightSpaces": 1,
"leftPass": true,
"rightPass": true
}
]
}
}
}Limitations and assumptions
- Tabs and other whitespace do not count as spaces. Text boundaries differ from line boundaries; the tool does not insert spaces, tokenize a language or ignore quoted occurrences.
- 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
- Whole Token Literal Replacer
Replace whole tokens under an explicit ASCII letter/digit/underscore boundary rule; Unicode word segmentation is not inferred.
- Enclosing Literal Wrapper Stripper
Strip one complete nonoverlapping enclosing literal wrapper, never internal or partial matches.