Description
Split a search snippet at supplied code-point highlight offsets.
Information records distinguish identifiers, controlled vocabularies, language fallbacks, assertion times and valid times. A supplied inverse predicate differs from an inferred semantic relation. Text offsets require an explicit code-point or code-unit basis, and a metadata count check does not validate field content or an entire schema.
Split a search snippet at supplied code-point highlight offsets.
When to use this tool
Use Search Snippet Highlight Offset Pair when you already have snippetText, startCodePoint, endCodePoint and need to split a search snippet at supplied code-point highlight offsets.
How to use the tool and how it works
- Enter snippetText, startCodePoint, endCodePoint. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read before, highlighted, after. Use the output convention below.
Require safe whole 0<=start<=end<=Array.from(text).length; slice the code-point array into before, highlighted [start,end) and after, then rejoin.1
Supplementary code points occupy two UTF-16 code units. Code-point slicing also differs from grapheme segmentation, so a highlight boundary can split a user-perceived character.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| snippetText | Snippet Text | Required. Text; maximum UTF-16 length 8192. |
| startCodePoint | Zero-based Array.from offset, inclusive; differs from a UTF-16 code-unit offset. | Required. Safe integer; minimum 0. |
| endCodePoint | Exclusive code-point end; no grapheme segmentation or HTML markup is generated. | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| before | Before | Required. Text; maximum UTF-16 length 8192. |
| highlighted | Highlighted | Required. Text; maximum UTF-16 length 8192. |
| after | After | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"snippetText": "Hello world",
"startCodePoint": 6,
"endCodePoint": 11
},
"output": {
"before": "Hello ",
"highlighted": "world",
"after": ""
}
}Limitations and assumptions
- Offsets are code points, not UTF-16 code units, graphemes or rendered width. The helper does not generate HTML or check highlight relevance.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Use the actual record, vocabulary authority and complete metadata schema for semantic or conformance questions. Apply the identifier scheme's real comparison rules and the intended language/offset policy rather than inferring them from a local string operation.
References
Similar or alternative tools
- Retrieval Query Document Pair Label
Encode a query and document identifier as an unambiguous pair key.
- Ontology Label Language Fallback Choice
Choose an ontology label by preferred language then fallback language.