Skip to content

Main content

Translated Paragraph Expansion Gap Tool

Compare aligned paragraph count expansion with an explicit reference factor, without translation quality judgments.

Loading tool…

Description

Compare total translated expansion with a supplied factor.

Comparative-literature annotations connect editions, passages, speakers, structural frames and count units. Literal keys and normalized lengths can support consistent records while textual meaning, translation fidelity and bibliographic authority remain matters for source-aware editorial analysis.

Compare total translated expansion with a supplied factor.

When to use this tool

Use Translated Paragraph Expansion Gap when checking a supplied literary annotation, cross-edition offset or count convention.

How to use the tool and how it works

  1. Enter sourceCounts, translatedCounts, expectedFactor. Keep parallel arrays aligned. 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 sourceTotalDecimal, translatedTotalDecimal, expansion, factorGap. Use the output convention below.

Compare total translated expansion with a supplied factor. Require aligned nonnegative whole count arrays, source total positive and expectedFactor >= 0; sum exactly into decimal strings, expansion = numeric target/source, factorGap = expansion-expected.1

Input fieldMeaning and unitsAccepted input
sourceCountsSource CountsRequired. Array of safe integer; maximum items 256.
translatedCountsTranslated CountsRequired. Array of safe integer; maximum items 256.
expectedFactorExpected FactorRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
sourceTotalDecimalSource Total DecimalRequired. Text; maximum UTF-16 length 8192.
translatedTotalDecimalTranslated Total DecimalRequired. Text; maximum UTF-16 length 8192.
expansionFloating-point translated/source ratio; exact count strings are returned separately.Required. Finite number.
factorGapFactor GapRequired. Finite number.
json
{
  "input": {
    "sourceCounts": [
      10,
      10
    ],
    "translatedCounts": [
      12,
      18
    ],
    "expectedFactor": 1.2
  },
  "output": {
    "sourceTotalDecimal": "20",
    "translatedTotalDecimal": "30",
    "expansion": 1.5,
    "factorGap": 0.30000000000000004
  }
}

Limitations and assumptions

  • Totals remain exact text while ratios use floating point; no alignment, language normalization or translation quality is assessed.
  • 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

Inspect the source editions and their annotation/counting policy for substantive literary, translation or provenance conclusions.

References

  1. Calculation and input contract: comparative-literature/translated-paragraph-expansion-gap — tool.io

Similar or alternative tools