Length Prefixed Text Record Decoder
Decode complete decimal-length-prefixed UTF-16 text records; reject malformed lengths or incomplete payloads.
Description
Decode complete decimal-length-prefixed UTF-16 text records; reject malformed lengths or incomplete payloads.
A length-prefixed text stream measures record lengths in UTF-16 code units rather than bytes.
When to use this tool
Decode complete decimal-length-prefixed UTF-16 text records; reject malformed lengths or incomplete payloads.
- Prepare the supplied encoded 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 encoded. 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.
Read a canonical decimal count followed by colon, consume exactly that many units and repeat to input end, accepting zero-length records. Reject truncation or more than 128 records.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| encoded | encoded. | 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. |
{
"input": {
"encoded": "3:a:b0:"
},
"output": {
"result": {
"records": [
"a:b",
""
]
}
}
}Limitations and assumptions
- This custom format is not a byte netstring and has no comma terminator. No Unicode normalization or encoded-byte counting occurs.
- 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
- Length Prefixed Text Record Encoder
Encode concatenated decimal-length-prefixed text records using UTF-16 code-unit lengths, not UTF-8 bytes.
- Record Separator Text Joiner
Join unescaped text records with a nonempty separator; separator occurrences in records are rejected for reversibility.