Description
Locate an offset relative to caller-supplied grapheme boundaries; no Unicode segmentation is inferred.
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.
Locate an offset relative to caller-supplied grapheme boundaries; no Unicode segmentation is inferred.
When to use this tool
Use Grapheme Boundary Side Token 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
- Enter offset, boundaries. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read atBoundary, leftBoundary, rightBoundary. Inspect atBoundary before interpreting the associated values.
For a strictly increasing nonnegative integer boundaries list starting at zero, report atBoundary and the nearest supplied boundaries on either side of a bounded offset.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| offset | Offset | Required. Safe integer; minimum 0. |
| boundaries | Boundaries | Required. Array of safe integer; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| atBoundary | At Boundary | Required. Boolean. |
| leftBoundary | Left Boundary | Required. Safe integer. |
| rightBoundary | Right Boundary | Required. Safe integer. |
{
"input": {
"offset": 2,
"boundaries": [
0,
1,
3,
5
]
},
"output": {
"atBoundary": false,
"leftBoundary": 1,
"rightBoundary": 3
}
}Limitations and assumptions
- At an exact boundary both returned sides equal offset. No text is provided, so the positions are not verified as grapheme or encoding boundaries.
- 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
Similar or alternative tools
- Grapheme Edge Slice Boundary
Slice caller-segmented grapheme clusters and report UTF-16 edge offsets; segmentation correctness belongs to the caller.
- Grapheme Cursor Mid Cluster Flag
Segment text using Intl.Segmenter with locale en and grapheme granularity.