Line Length Limit Audit
Audit UTF-16 hard-line content length against an inclusive caller limit; not grapheme or display-cell width.
Description
Audit UTF-16 hard-line content length against an inclusive caller limit; not grapheme or display-cell width.
Line-length limits can be enforced on text storage units independently of the way a font renders it. The audit reports only lines that exceed a chosen bound.
When to use this tool
Audit UTF-16 hard-line content length against an inclusive caller limit; not grapheme or display-cell width.
- Prepare the supplied text, maximumCodeUnits 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, maximumCodeUnits. 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.violations. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Split CRLF, CR and LF line endings, excluding them from line contents. For each line longer than maximumCodeUnits, return its one-based line number, UTF-16 length and excess.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| text | text. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| maximumCodeUnits | maximum code units. | Integer from 0 to 8192 inclusive |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.violations | The violations list in the ordering and representation described above. |
{
"input": {
"text": "abc\nx",
"maximumCodeUnits": 2
},
"output": {
"result": {
"violations": [
{
"line": 1,
"length": 3,
"excess": 1
}
]
}
}
}Limitations and assumptions
- A line exactly at the limit passes. Tabs and surrogate pairs are counted as code units, not display columns or grapheme clusters; the tool does not wrap or truncate text.
- 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.
- average word length
Calculate the mean character length of whitespace-delimited words in text.