Length Prefixed Text Record Encoder
Encode concatenated decimal-length-prefixed text records using UTF-16 code-unit lengths, not UTF-8 bytes.
Description
Encode concatenated decimal-length-prefixed text records using UTF-16 code-unit lengths, not UTF-8 bytes.
Text records can contain arbitrary separators when each length is explicitly declared.
When to use this tool
Encode concatenated decimal-length-prefixed text records using UTF-16 code-unit lengths, not UTF-8 bytes.
- Prepare the supplied records 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. 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.encoded. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Emit each records string as its UTF-16 length, colon and unchanged content, concatenating the records without another separator.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| records | records. | List of strings; at most 128 entries |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.encoded | The encoded value under the stated formula or text convention. |
{
"input": {
"records": [
"a:b",
""
]
},
"output": {
"result": {
"encoded": "3:a:b0:"
}
}
}Limitations and assumptions
- No byte encoding or netstring comma is added. Empty list produces empty text, while one empty record produces 0:.
- 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 Decoder
Decode complete decimal-length-prefixed UTF-16 text records; reject malformed lengths or incomplete payloads.
- Record Separator Text Joiner
Join unescaped text records with a nonempty separator; separator occurrences in records are rejected for reversibility.