Fixed Width Record Padder

Pad caller cells into explicit UTF-16 fixed-width fields; overflow is rejected instead of silently truncated.

Description

Pad caller cells into explicit UTF-16 fixed-width fields; overflow is rejected instead of silently truncated.

Fixed-width text padding aligns fields by code-unit width and must reject content already too long.

When to use this tool

Pad caller cells into explicit UTF-16 fixed-width fields; overflow is rejected instead of silently truncated.

  • Prepare the supplied cells, widths, pad 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

  1. Enter cells, widths, pad. Use the exact text syntax, units and index conventions explained below.
  2. Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
  3. Read result.record. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Require aligned cells/widths and a one-unit pad string. Each width is an integer from 0 to 8,192; right-pad each cell to its width, then concatenate parts.1

Input fieldMeaning and representationAccepted input
cellscells.List of strings; at most 128 entries
widthswidths.List of finite numbers; at most 128 entries
padpad.Text; at most 8,192 UTF-16 code units, subject to the grammar above
Output fieldInterpretation
resultObject containing the named outputs below.
result.recordThe record value under the stated formula or text convention.
json
{
  "input": {
    "cells": [
      "a",
      "bc"
    ],
    "widths": [
      3,
      3
    ],
    "pad": " "
  },
  "output": {
    "result": {
      "record": "a  bc "
    }
  }
}

Limitations and assumptions

  • Widths are UTF-16 units, not display columns or bytes. No truncation, multicolumn glyph handling or left padding is applied.
  • 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

  1. Tool behavior and example: Fixed Width Record Padder — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies