Lexical Path Separator Transcoder

Transcode literal path separators only, without drive, UNC, root, escape, symlink or filesystem semantics.

Description

Transcode literal path separators only, without drive, UNC, root, escape, symlink or filesystem semantics.

Changing separator characters is a literal text operation, distinct from converting a full platform path syntax.

When to use this tool

Transcode literal path separators only, without drive, UNC, root, escape, symlink or filesystem semantics.

Prepare the supplied path, fromSeparator, toSeparator 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 path, fromSeparator, toSeparator. 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.path. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Require distinct one-code-unit fromSeparator and toSeparator. Replace every occurrence of the former in path with the latter.^[1]

Input field	Meaning and representation	Accepted input
path	path.	Text; at most 8,192 UTF-16 code units, subject to the grammar above
fromSeparator	from separator.	Text; at most 8,192 UTF-16 code units, subject to the grammar above
toSeparator	to separator.	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.path	The path value under the stated formula or text convention.

json

{
  "input": {
    "path": "a\\b",
    "fromSeparator": "\\",
    "toSeparator": "/"
  },
  "output": {
    "result": {
      "path": "a/b"
    }
  }
}

Limitations and assumptions

No drive, UNC, escaping, normalization or filesystem semantics are interpreted. The result is not validated as a usable destination-platform path.
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

Tool behavior and example: Lexical Path Separator Transcoder — tool.io

Similar or alternative tools

Path Terminal Separator Policy
Enforce a literal POSIX terminal slash policy while preserving absolute root; no directory existence claim.
Path Component Name Budget Checker
Audit lexical POSIX component UTF-8 byte budgets against an explicit limit; not a universal NAME_MAX or filesystem encoding claim.