Skip to content

Main content

Plain Text Soft Hyphen Visible Break Tool

Calculate plain text soft hyphen visible break from explicit caller-supplied inputs.

Loading tool…

Description

Count U+00AD soft hyphens and replace every occurrence with a literal hyphen when showBreaks or remove it otherwise.

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.

Count U+00AD soft hyphens and replace every occurrence with a literal hyphen when showBreaks or remove it otherwise.

When to use this tool

Use Plain Text Soft Hyphen Visible Break 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, showBreaks. 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 text, count. Use the output convention below.

Count U+00AD soft hyphens and replace every occurrence with a literal hyphen when showBreaks or remove it otherwise.1

Input fieldMeaning and unitsAccepted input
textTextRequired. Text; maximum UTF-16 length 8192.
showBreaksShow BreaksRequired. Boolean.
Output fieldInterpretationReturned shape
textTextRequired. Text; maximum UTF-16 length 8192.
countCount under the stated input or output convention.Required. Safe integer.
json
{
  "input": {
    "text": "co­operate",
    "showBreaks": true
  },
  "output": {
    "text": "co-operate",
    "count": 1
  }
}

Limitations and assumptions

  • This is a text transformation rather than layout-dependent hyphenation. It does not determine actual break positions, preserve all formatting intent, or sanitize other invisible characters.
  • 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/plain-text-soft-hyphen-visible-break — tool.io

Similar or alternative tools