Skip to content

Main content

Translation Omission Span Length

Count tokens in an explicitly annotated half-open translation-omission span; no omission is inferred from text.

Loading tool…

Description

Count a supplied half-open translation omission token span.

Comparative literary records preserve editions, translations, source lines, rhyme classes and editorial omissions. A code-point count differs from a grapheme count, while an aligned token span depends on the supplied text and indexing convention. A source-qualified label does not establish faithful translation, authorship or an interpretation.

Count a supplied half-open translation omission token span.

When to use this tool

Use Translation Omission Span Length when you already have startTokenIndex, endTokenIndexExclusive and need to count a supplied half-open translation omission token span.

How to use the tool and how it works

  1. Enter startTokenIndex, endTokenIndexExclusive. 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 omittedTokenCount. Use the output convention below.

Require safe whole 0<=startTokenIndex<=endTokenIndexExclusive; return end-start.1

Input fieldMeaning and unitsAccepted input
startTokenIndexStart Token IndexRequired. Safe integer; minimum 0.
endTokenIndexExclusiveExcluded end in the caller-defined token index; no source tokens are inspected.Required. Safe integer.
Output fieldInterpretationReturned shape
omittedTokenCountOmitted Token CountRequired. Safe integer.
json
{
  "input": {
    "startTokenIndex": 12,
    "endTokenIndexExclusive": 20
  },
  "output": {
    "omittedTokenCount": 8
  }
}

Limitations and assumptions

  • No source or translation is read, omitted tokens verified, source bounds checked or fidelity established.
  • 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

Read the original passage, translation and relevant editions alongside the stated editorial conventions. Verify context, source locators and attribution when preparing quotations or comparative arguments; local string operations do not make those scholarly judgments.

References

  1. Calculation and input contract: comparative-literature/translation-omission-span-length — tool.io

Similar or alternative tools