Soft Wrap Offset Map
Map fixed-width soft-wrap segments in UTF-16 code units per hard line; not word wrapping, grapheme layout or display-cell measurement.
Description
Map fixed-width soft-wrap segments in UTF-16 code units per hard line; not word wrapping, grapheme layout or display-cell measurement.
A fixed-width soft-wrap map partitions line contents without inserting actual newline characters. It can support a simple preview or offset-based layout plan.
When to use this tool
Map fixed-width soft-wrap segments in UTF-16 code units per hard line; not word wrapping, grapheme layout or display-cell measurement.
- Prepare the supplied text, width 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, width. 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.segments. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require a positive integer width. Split each source line into consecutive chunks of at most width UTF-16 units and return their original offsets and one-based line number; represent empty lines with one empty segment.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| text | text. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| width | width. | Integer from 1 to 8192 inclusive |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.segments | The segments list in the ordering and representation described above. |
{
"input": {
"text": "abcde",
"width": 2
},
"output": {
"result": {
"segments": [
{
"line": 1,
"start": 0,
"end": 2
},
{
"line": 1,
"start": 2,
"end": 4
},
{
"line": 1,
"start": 4,
"end": 5
}
]
}
}
}Limitations and assumptions
- This is a storage-unit wrap, not word wrapping or measured rendering. Tabs, wide glyphs, combining sequences and surrogate pairs receive no special width or boundary handling.
- 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
- Code Point Index to UTF-8 Byte Offset
Convert zero-based Unicode scalar index to UTF-8 byte offset; reject unpaired surrogates and count scalars rather than grapheme clusters.
- Line and Column to UTF-16 Offset
Map one-based logical line/UTF-16 content column to offset; columns inside separators are intentionally not accepted.