Record Separator Text Joiner
Join unescaped text records with a nonempty separator; separator occurrences in records are rejected for reversibility.
Description
Join unescaped text records with a nonempty separator; separator occurrences in records are rejected for reversibility.
A literal record separator is unambiguous only when it does not occur inside any record.
When to use this tool
Join unescaped text records with a nonempty separator; separator occurrences in records are rejected for reversibility.
- Prepare the supplied records, separator 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 records, separator. 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.
Require a nonempty separator and every records string free of that substring. Join records with the separator unchanged.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| records | records. | List of strings; at most 128 entries |
| separator | separator. | 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.text | The text value under the stated formula or text convention. |
{
"input": {
"records": [
"a",
"",
"b"
],
"separator": "|"
},
"output": {
"result": {
"text": "a||b"
}
}
}Limitations and assumptions
- No escaping is performed. Empty list and one empty record serialize identically, and byte encodings or line-ending rules are not inferred.
- 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.
- Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
- 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
Choose the exact text grammar before combining serializers and parsers. UTF-16 record lengths, raw separators and custom backslash escapes differ from byte framing, CSV, Markdown and spreadsheet semantics.
References
Similar or alternative tools
- Record Separator Text Splitter
Split literal nonempty record separators preserving empty text records; no quoting or escaping.
- Length Prefixed Text Record Decoder
Decode complete decimal-length-prefixed UTF-16 text records; reject malformed lengths or incomplete payloads.