Skip to content

Main content

Sentence Terminal Punctuation Pair Rule Tool

Calculate sentence terminal punctuation pair rule from explicit caller-supplied inputs.

Loading tool…

Description

For two supplied period, exclamation, or question-mark tokens return redundant when equal and collapse to one copy if equal, otherwise concatenate both.

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.

For two supplied period, exclamation, or question-mark tokens return redundant when equal and collapse to one copy if equal, otherwise concatenate both.

When to use this tool

Use Sentence Terminal Punctuation Pair Rule 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 first, second. 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 redundant, collapse. Inspect redundant before interpreting the associated values.

For two supplied period, exclamation, or question-mark tokens return redundant when equal and collapse to one copy if equal, otherwise concatenate both.1

Input fieldMeaning and unitsAccepted input
firstFirstRequired. Text; one of ".", "!", "?"; maximum UTF-16 length 8192.
secondSecondRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
redundantRedundantRequired. Boolean.
collapseCollapseRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "first": "!",
    "second": "!"
  },
  "output": {
    "redundant": true,
    "collapse": "!"
  }
}

Limitations and assumptions

  • This is an explicit two-token rule. It does not analyze grammar, abbreviations, quotation context, emphatic punctuation, or ellipsis conventions.
  • 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/sentence-terminal-punctuation-pair-rule — tool.io

Similar or alternative tools