Skip to content

Main content

Text Leading Trailing BOM Distinction Tool

Compute text leading trailing bom distinction from explicit bounded inputs.

Loading tool…

Description

Return leading and trailing U+FEFF flags and zero-based UTF-16 interiorIndices excluding both endpoints.

Text positions can be measured in UTF-16 code units, Unicode code points, grapheme clusters, or modeled display columns. These coordinates are not interchangeable. Invisible markers and delimiter policies can also affect interpretation even when a string looks unchanged, so the chosen representation needs to stay explicit.

Return leading and trailing U+FEFF flags and zero-based UTF-16 interiorIndices excluding both endpoints.

When to use this tool

Use Text Leading Trailing BOM Distinction when you need the stated marker, coordinate, delimiter, or normalization operation under an explicit text representation.

How to use the tool and how it works

  1. Enter text. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read leading, trailing, interiorIndices. Inspect leading, trailing before interpreting the associated values.

Return leading and trailing U+FEFF flags and zero-based UTF-16 interiorIndices excluding both endpoints.1

Input fieldMeaning and unitsAccepted input
textTextRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
leadingLeadingRequired. Boolean.
trailingTrailingRequired. Boolean.
interiorIndicesInterior IndicesRequired. Array of safe integer; maximum items 256.
json
{
  "input": {
    "text": "a"
  },
  "output": {
    "leading": true,
    "trailing": true,
    "interiorIndices": []
  }
}

Limitations and assumptions

  • A single U+FEFF is both leading and trailing with no interior occurrence. Position alone does not establish an actual byte-order mark, encoding, or whether removal preserves meaning.
  • The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.

Alternative or Complementary methods

Choose the coordinate system required by the consumer. Use a full parser, renderer, or segmentation method when a local marker or delimiter rule cannot determine the complete text behavior.

References

  1. Calculation and input contract: text/text-leading-trailing-bom-distinction — tool.io

Similar or alternative tools