Literal Replacement Range Map

Map nonoverlapping literal replacements between original and resulting UTF-16 ranges, without repeatedly replacing inserted text.

Description

Map nonoverlapping literal replacements between original and resulting UTF-16 ranges, without repeatedly replacing inserted text.

Replacement range maps connect original literal matches to their positions after replacement. They are useful for annotations that must move with a predictable textual change.

When to use this tool

Map nonoverlapping literal replacements between original and resulting UTF-16 ranges, without repeatedly replacing inserted text.

  • Prepare the supplied text, needle, replacement 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 text, needle, replacement. 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.ranges. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Find nonoverlapping needle occurrences in the original text. Track cumulative replacement-length delta and return source and target start/end for each match using the literal replacement's UTF-16 length.1

Input fieldMeaning and representationAccepted input
texttext.Text; at most 8,192 UTF-16 code units, subject to the grammar above
needleneedle.Text; at most 8,192 UTF-16 code units, subject to the grammar above
replacementreplacement.Text; at most 8,192 UTF-16 code units, subject to the grammar above
Output fieldInterpretation
resultObject containing the named outputs below.
result.rangesThe ranges list in the ordering and representation described above.
json
{
  "input": {
    "text": "aba",
    "needle": "a",
    "replacement": "xy"
  },
  "output": {
    "result": {
      "ranges": [
        {
          "sourceStart": 0,
          "sourceEnd": 1,
          "targetStart": 0,
          "targetEnd": 2
        },
        {
          "sourceStart": 2,
          "sourceEnd": 3,
          "targetStart": 3,
          "targetEnd": 5
        }
      ]
    }
  }
}

Limitations and assumptions

  • The tool returns ranges rather than the replaced text. Empty needles are rejected, matches are case-sensitive, and overlapping occurrences are skipped after each selected match.
  • Text offsets and lengths use UTF-16 code units unless explicitly described as bytes or code points. CRLF, CR and LF are recognized as line endings; a terminal newline creates a final empty line in the shared line model.
  • 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.
  • Ordinary string lists have at most 128 entries of at most 128 code units each; numeric lists and matrices have separate bounded size checks. 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 parser or language-aware editor when quoting, syntax or nested constructs matter. For plain text transforms, keep UTF-16 offsets, Unicode code points, grapheme clusters and UTF-8 byte offsets distinct; apply changes to the same source version used to calculate spans.

References

  1. Tool behavior and example: Literal Replacement Range Map — tool.io

Similar or alternative tools

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