Terminal Newline Classifier
Classify the exact terminal CR, LF and CRLF newline sequence without normalization or trimming other whitespace.
Description
Classify the exact terminal CR, LF and CRLF newline sequence without normalization or trimming other whitespace.
A terminal newline classifier describes the entire newline run at the end of text. Repeated or mixed endings can be distinguished from a single final newline.
When to use this tool
Classify the exact terminal CR, LF and CRLF newline sequence without normalization or trimming other whitespace.
- 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.hasTerminalNewline, result.terminalSequence, result.terminalNewlineCount. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Match the final contiguous sequence of CRLF, CR or LF units. Return whether it exists, its exact text and the number of logical newline sequences, treating CRLF as one.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.hasTerminalNewline | Flag for has terminal newline under the exact condition described above. |
| result.terminalSequence | The terminal sequence value under the stated formula or text convention. |
| result.terminalNewlineCount | The terminal newline count value under the stated formula or text convention. |
{
"input": {
"text": "a\r\n"
},
"output": {
"result": {
"hasTerminalNewline": true,
"terminalSequence": "\r\n",
"terminalNewlineCount": 1
}
}
}Limitations and assumptions
- Only the end of the text is examined. Spaces or tabs after a newline mean it is not terminal; internal newline counts and overall newline-style consistency are not reported.
- 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
- Terminal Newline Enforcer
Enforce exactly one supplied terminal newline or none; internal line endings and non-newline suffix whitespace are preserved.
- acronym
Build an acronym from the uppercase first letter of each whitespace-separated word.