Description
Inspect and visibly replace a soft hyphen at one explicit Unicode-scalar index only, preserving all other text and not inserting visible hyphens generally.
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.
Inspect and visibly replace a soft hyphen at one explicit Unicode-scalar index only, preserving all other text and not inserting visible hyphens generally.
When to use this tool
Use Text: Soft Hyphen Single Position Marker 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 text, codepointIndex. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read result. Expand result to inspect the returned fields.
Inspect one bounded zero-based Unicode codepointIndex. Return softHyphen for U+00AD and replace only that selected occurrence with [SHY] in markedText inside result.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| text | Text | Required. Text. |
| codepointIndex | Zero-based Unicode code-point position, not UTF-16 offset. | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| result | Result | Required. Object. |
{
"input": {
"text": "cooperate",
"codepointIndex": 2
},
"output": {
"result": {
"softHyphen": true,
"markedText": "co[SHY]operate"
}
}
}Limitations and assumptions
- The index is by code points, not UTF-16 units. Other soft hyphens remain unchanged, and this does not choose a line break or normalize the whole string.
- Outputs are nested inside result. 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
- Plain Text Soft Hyphen Visible Break
Count U+00AD soft hyphens and replace every occurrence with a literal hyphen when showBreaks or remove it otherwise.
- Text Zero Width Space Break Marker
Return zero-based UTF-16 indexes of U+200B zero-width spaces and their count.