Description
Split an iCalendar TEXT-list only at unescaped commas, then decode defined TEXT escapes; repeated empty elements remain explicit.
iCalendar separates content-line framing, property values, parameters and component nesting. TEXT escaping protects separators, while line folding is based on encoded octets. DATE, floating time, UTC and named-zone representations carry different information; a token-level operation does not resolve a timezone or expand recurrence rules.1
Split an iCalendar TEXT-list only at unescaped commas, then decode defined TEXT escapes; repeated empty elements remain explicit.
When to use this tool
Use this tool to split an iCalendar TEXT-list only at unescaped commas, then decode defined TEXT escapes; repeated empty elements remain explicit.
How to use the tool and how it works
- Enter text using the field definitions below.
- Run the operation. Correct input errors before interpreting an output.
- Read result.values. Use the ordering, boundary rules and absence conditions described below.
Split at unescaped commas, preserving escaped pairs during the scan, then unescape each resulting TEXT value.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| text | TEXT-value or folded-content text under the stated operation; JSON escapes show actual backslashes and line endings. | Text, at most 8,192 UTF-16 code units; the operation’s grammar also applies. |
| Output field | Interpretation |
|---|---|
| result | Object containing the named fields below. |
| result.values | Decoded TEXT list values in order, retaining empty entries. |
{
"input": {
"text": "a\\,b,c"
},
"output": {
"result": {
"values": [
"a,b",
"c"
]
}
}
}Limitations and assumptions
- Empty items remain present; invalid escape spellings are input errors rather than silently retained.
- Content spans use zero-based UTF-16 offsets; fold limits use UTF-8 bytes including the continuation space. Token helpers handle the stated subset only, without a timezone database, recurrence engine or calendar import.
- Every declared top-level input field is required and unexpected fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
- Numeric outputs must be finite and no larger in absolute magnitude than the safe-integer limit; operations returning exact large integers use decimal text. Positions are zero-based and spans end exclusively unless the operation explicitly states a different convention.
Alternative or Complementary methods
Keep content-line syntax, value escaping and timezone interpretation separate. Use a complete iCalendar implementation for recurrence expansion, timezone transitions and property-specific validation.
References
Similar or alternative tools
- iCalendar Text List Value Joiner
Format a literal iCalendar TEXT-list with per-value escaping, preserving empty elements and source order; no property-specific semantics.
- iCalendar Text Value Escaper
Escape iCalendar TEXT backslash, comma, semicolon and newline; lone CR is rejected, no colon or parameter encoding.