Line Pair Zipper
Zip hard-line content positionally; missing lines are null, not empty strings or dropped rows.
Description
Zip hard-line content positionally; missing lines are null, not empty strings or dropped rows.
Zipping two texts by line makes positional comparison explicit. A missing line is distinct from an existing empty line.
When to use this tool
Zip hard-line content positionally; missing lines are null, not empty strings or dropped rows.
- Prepare the supplied left, right 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 left, right. 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.pairs. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Parse both texts and produce pairs through the larger line count, with one-based line numbers and each side's content. Use null when one side has no corresponding line.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| left | left. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| right | right. | 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.pairs | The pairs list in the ordering and representation described above. |
{
"input": {
"left": "a\nb",
"right": "c"
},
"output": {
"result": {
"pairs": [
{
"line": 1,
"left": "a",
"right": "c"
},
{
"line": 2,
"left": "b",
"right": null
}
]
}
}
}Limitations and assumptions
- Line endings are omitted from pair values. Empty input still represents one empty line, and a terminal newline adds an empty final line; no diff alignment is inferred.
- 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
- Consecutive Duplicate Line Collapser
Collapse only consecutive identical line contents, retaining each kept line separator; nonadjacent duplicates remain.
- Single Pair Delimiter Repair Hints
Provide literal single-pair delimiter insertion hints with unmatched offsets; quotes, escapes and cross-type nesting are outside scope.