Record Separator Text Splitter

Split literal nonempty record separators preserving empty text records; no quoting or escaping.

Description

Split literal nonempty record separators preserving empty text records; no quoting or escaping.

Splitting on an exact record separator can preserve empty records between or after separators.

When to use this tool

Split literal nonempty record separators preserving empty text records; no quoting or escaping.

Prepare the supplied text, 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 text, 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.records. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Require a nonempty separator, split text literally and reject more than 128 output records.^[1]

Input field	Meaning and representation	Accepted input
text	text.	Text; at most 8,192 UTF-16 code units, subject to the grammar above
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.records	The records list in the ordering and representation described above.

json

{
  "input": {
    "text": "a||b|",
    "separator": "|"
  },
  "output": {
    "result": {
      "records": [
        "a",
        "",
        "b",
        ""
      ]
    }
  }
}

Limitations and assumptions

Empty input returns one empty record. No escaping, newline normalization or quoted-field grammar is used.
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

Tool behavior and example: Record Separator Text Splitter — tool.io

Similar or alternative tools

Record Separator Text Joiner
Join unescaped text records with a nonempty separator; separator occurrences in records are rejected for reversibility.
Length Prefixed Text Record Decoder
Decode complete decimal-length-prefixed UTF-16 text records; reject malformed lengths or incomplete payloads.