Numbered Filename Suffix Formatter
Format a parenthesized unsigned decimal filename suffix with minimum digit width; exact decimal text avoids unsafe numeric conversion.
Description
Format a parenthesized unsigned decimal filename suffix with minimum digit width; exact decimal text avoids unsafe numeric conversion.
A parenthesized numeric filename suffix can retain an explicit zero-padding width without converting a large number to floating point.
When to use this tool
Format a parenthesized unsigned decimal filename suffix with minimum digit width; exact decimal text avoids unsafe numeric conversion.
- Prepare the supplied prefix, numberDecimal, digitWidth, suffix 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 prefix, numberDecimal, digitWidth, suffix. 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.name. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Canonicalize numberDecimal as unsigned decimal digits, left-pad to digitWidth 1 to 1,024 and compose prefix+(digits)+suffix. Validate the resulting single POSIX filename.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| prefix | prefix. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| numberDecimal | number decimal. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| digitWidth | digit width. | Integer from 1 to 1024 inclusive |
| suffix | suffix. | 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.name | The name value under the stated formula or text convention. |
{
"input": {
"prefix": "report",
"numberDecimal": "7",
"digitWidth": 3,
"suffix": ".txt"
},
"output": {
"result": {
"name": "report(007).txt"
}
}
}Limitations and assumptions
- digitWidth is a minimum, not a maximum. No filename is created, collision check performed or extension automatically relocated.
- 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.
- String lists have at most 128 entries of at most 128 code units; matrices have at most 128 rows and columns. Larger numeric lists and parsed JSON have separate bounded budgets. Nonfinite results and excessively large serialized outputs are rejected.
- 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
Use a filesystem-aware implementation with appropriate platform semantics for actual file operations. Literal slash components, Unicode comparison and filename plans do not resolve symlinks or atomically reserve a destination.
References
Similar or alternative tools
- Numbered Filename Suffix Parser
Parse a terminal parenthesized unsigned decimal filename suffix before a parentheses-free extension tail; preserve digit width and exact decimal value.
- Filename Casefold Collision Table
Audit the bounded ASCII case-insensitive filename branch; rejects non-ASCII rather than pretend lowercasing implements full Unicode case folding.