Terminal Newline Enforcer
Enforce exactly one supplied terminal newline or none; internal line endings and non-newline suffix whitespace are preserved.
Description
Enforce exactly one supplied terminal newline or none; internal line endings and non-newline suffix whitespace are preserved.
A terminal newline policy can require exactly one chosen ending or none. This differs from replacing every newline inside the document.
When to use this tool
Enforce exactly one supplied terminal newline or none; internal line endings and non-newline suffix whitespace are preserved.
- Prepare the supplied text, newline, enabled 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, newline, enabled. 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.text. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Remove the complete trailing run of CRLF, CR and LF sequences. When enabled, append exactly the supplied newline, which must be LF, CR or CRLF; otherwise leave the stripped base.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| text | text. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| newline | newline. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| enabled | Explicit choice for enabled; supply a boolean rather than a text label. | true or false |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.text | The text value under the stated formula or text convention. |
{
"input": {
"text": "a\n\n",
"newline": "\r\n",
"enabled": true
},
"output": {
"result": {
"text": "a\r\n"
}
}
}Limitations and assumptions
- Internal line endings are preserved. Trailing spaces after a newline prevent that newline from being terminal for this operation; an empty input becomes one newline when enabled.
- 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 Classifier
Classify the exact terminal CR, LF and CRLF newline sequence without normalization or trimming other whitespace.
- acronym
Build an acronym from the uppercase first letter of each whitespace-separated word.