Escaped Delimiter Token Joiner
Split or join an explicit backslash-escaped single-character delimiter dialect with control escapes; not CSV, shell or programming-language syntax.
Description
Split or join an explicit backslash-escaped single-character delimiter dialect with control escapes; not CSV, shell or programming-language syntax.
Escaping delimiters preserves token boundaries when tokens contain separators or control characters.
When to use this tool
Split or join an explicit backslash-escaped single-character delimiter dialect with control escapes; not CSV, shell or programming-language syntax.
- Prepare the supplied tokens, delimiter 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 tokens, delimiter. 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.
For each tokens string escape backslash, newline, carriage return, tab and the chosen delimiter, then join with that delimiter.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| tokens | tokens. | List of strings; at most 128 entries |
| delimiter | delimiter. | 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": {
"tokens": [
"a,b",
"c"
],
"delimiter": ","
},
"output": {
"result": {
"text": "a\\,b,c"
}
}
}Limitations and assumptions
- The delimiter is one UTF-16 unit and cannot be backslash or n, r, t. An empty token list and a single empty token both serialize as empty text, so the format alone does not distinguish them.
- All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
- JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.
Alternative or Complementary methods
Use a parser for the actual target format when the task requires CSV, shell, URL, calendar or filesystem semantics. These tools implement the specific small grammars stated here, without adding those surrounding conventions.
References
Similar or alternative tools
- Escaped Delimiter Token Splitter
Split or join an explicit backslash-escaped single-character delimiter dialect with control escapes; not CSV, shell or programming-language syntax.
- Balanced Parenthesis Token Splitter
Split a literal delimiter only outside balanced parentheses; parentheses are retained, quotes and escapes have no special meaning.