Skip to content

Main content

Manuscript Sura Heading Verse Offset Tool

Translate an explicit one-based local manuscript verse index using a supplied heading first-verse number without resolving numbering differences.

Loading tool…

Description

Map a local one-based manuscript verse index to a supplied starting verse.

Textual and archival references depend on the collection, edition, numbering system, date convention and source attribution. A supplied surah/ayah or manuscript partition number is a locator, not verification of canonical limits or content. Permission, beneficiary shares and direction labels require their stated documentary context.

Map a local one-based manuscript verse index to a supplied starting verse.

When to use this tool

Use Manuscript Sura Heading Verse Offset when you already have localVerseIndex, suppliedFirstVerseNumber and need to map a local one-based manuscript verse index to a supplied starting verse.

How to use the tool and how it works

  1. Enter localVerseIndex, suppliedFirstVerseNumber. 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 mappedVerseNumber. Use the output convention below.

Require both inputs positive safe whole numbers; compute localIndex+firstVerse-1 using BigInt and export a safe integer.1

Input fieldMeaning and unitsAccepted input
localVerseIndexLocal Verse IndexRequired. Safe integer; minimum 1.
suppliedFirstVerseNumberSupplied First Verse NumberRequired. Safe integer; minimum 1.
Output fieldInterpretationReturned shape
mappedVerseNumberlocalVerseIndex+suppliedFirstVerseNumber-1; exact integer arithmetic with safe numeric export.Required. Safe integer.
json
{
  "input": {
    "localVerseIndex": 3,
    "suppliedFirstVerseNumber": 10
  },
  "output": {
    "mappedVerseNumber": 12
  }
}

Limitations and assumptions

  • No actual verse numbering or manuscript content is verified; unsafe mapped numbers are rejected.
  • 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

Consult the relevant original edition, manuscript, deed or stated authority for an interpretive or rights question. Use a complete calendar, directional or distribution method when computation is required; local locators and supplied labels do not infer those rules.

References

  1. Calculation and input contract: islamic-studies/manuscript-sura-heading-verse-offset — tool.io

Similar or alternative tools