Skip to content

Main content

Quoted Reply Depth Count Tool

Count literal leading reply markers under an explicit ASCII-space policy, without claiming Markdown parsing.

Loading tool…

Description

Strip a literal quoted-reply prefix and return depth.

Communication measurements need an explicit event origin, clock correction, count unit and exposure denominator. Timing and coverage records can be summarized without detecting actual speech, verifying message delivery or determining readability, accessibility or communication quality.

Strip a literal quoted-reply prefix and return depth.

When to use this tool

Use Quoted Reply Depth Count when checking the stated communication timing, rate, representation or coverage convention.

How to use the tool and how it works

  1. Enter line, marker, allowSpaces. 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 depth, content. Use the output convention below.

Strip a literal quoted-reply prefix and return depth. Require marker to be one UTF-16 code unit other than ASCII space; count leading marker occurrences while optionally skipping ASCII spaces, then return remaining content.1

Input fieldMeaning and unitsAccepted input
lineLineRequired. Text; maximum UTF-16 length 8192.
markerOne UTF-16 code unit other than ASCII space; astral symbols are not admitted as a single marker.Required. Text; maximum UTF-16 length 8192.
allowSpacesAllow SpacesRequired. Boolean.
Output fieldInterpretationReturned shape
depthDepthRequired. Safe integer.
contentContentRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "line": "> > hello",
    "marker": ">",
    "allowSpaces": true
  },
  "output": {
    "depth": 2,
    "content": "hello"
  }
}

Limitations and assumptions

  • Only the supplied prefix convention is recognized; tabs, escaping, email grammar and attribution are not parsed.
  • 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.

Alternative or Complementary methods

Use actual synchronized media/message records, appropriate text measurement and user evaluation for complete communication or accessibility assessment.

References

  1. Calculation and input contract: communication/quoted-reply-depth-count — tool.io

Similar or alternative tools