Log in

or use your email

Search the Library

Keyword search across Doctrine Analysis, Core Glossary, Comparative Theology, and Regional Analysis. Mention a language name for the best results — e.g. "remnant burmese" or "what glossary terms conflict for burmese."

Type at least 2 characters to search.

Work with us

Tell us a bit about how you'd like to work with tri-bible.ai.

Stay informed Get our weekly newsletter. Never sold or shared, unsubscribe anytime.

Let us serve you Church leaders and ministry networks seeking translated curriculum Join our team Volunteers interested in reviewing translations
Download Translation Skill

Linguistic Gap Analysis

Linguistic Gap Analysis — Jonah (English → Spanish)

0. Purpose and Scope

This document executes PRD Phase 1 Step 8 for the Jonah curriculum. It identifies where Spanish’s existing theological vocabulary is (a) genuinely missing a load-bearing distinction the Hebrew text makes, (b) crowded — i.e. a term is doctrinally correct but sits in a semantic neighborhood already occupied by a rival Catholic-popular-piety or folk-religious meaning and must be “fenced” with teaching notes, or (c) a transliteration-vs-paraphrase decision point where the Language Package must commit to one strategy for consistency across all four chapters.

This analysis covers the entire book of Jonah, chapters 1–4, per the full-book-coverage mandate, with Jonah 3:1–10 (the core passage) receiving the deepest treatment as the theological anchor. It does not repeat the full term-by-term detail already recorded in analysis/08_core_glossary.md and the Jonah extension of assets/bible_term_registry.json; instead it supplies the gap-analysis reasoning that justifies the strategic choices those artifacts encode, per the Step 8 mandate: doctrine vocabulary matrix, missing-vocabulary vs. crowded-neighborhood mapping, transliteration/paraphrase decisions, and a ranked ambiguity list.

All renderings below are consistent with, and never contradict, the baseline translation_memory.json (Romans). Where a Jonah term is conceptually adjacent to a baseline term (e.g., nacham vs. baseline’s careful handling of justicia imputada), that parallel is noted explicitly as precedent for the review-routing decision.


1. Doctrine Vocabulary Matrix

For each of the five curriculum doctrines: the available Spanish terms, their inherent weaknesses in the destination language/culture, and the recommended mitigation strategy.

1.1 God’s Compassion for the Nations

Available Spanish termsWeaknessRecommended strategy
”misericordia” (chesed, chus)Broad devotional word; in popular Catholic piety heavily associated with petitions to the Virgin (“Madre de Misericordia”) and the saints rather than God’s own initiating compassion toward outsiders/enemiesAnchor every occurrence explicitly to God as subject and to Nineveh (Gentile/enemy) as object; never let the word float untethered from its referent
”compasión” / “compadecerse de” (chus, 4:10-11)Generic emotional-sympathy word; risks reduction to sentimental feeling rather than covenantal, action-producing compassionUse identical verb for both Jonah’s pity (plant) and God’s compassion (Nineveh) per registry chus_pity; teach the rhetorical parallel explicitly
”Dios clemente y misericordioso” (El channun v’rachum, 4:2)None lexically — this is a fixed, high-register OT formula; risk is that learners hear it as generic praise-language rather than the book’s thesisMatch Reina-Valera’s Exodus 34:6 wording exactly for cross-passage consistency; teach as the book’s theological center, quoted by Jonah as a complaint
”las naciones” / “los gentiles” (cf. baseline gentiles)Baseline already rejects “paganos” as pejorativeReuse baseline’s “gentiles” rejection logic; for Nineveh specifically prefer “las naciones” or the proper name “Nínive” generalized in teaching notes, since Jonah predates the Jew/Gentile terminology Romans uses

Doctrine-level gap: Spanish has no single word that carries “God’s initiating, unearned compassion extended specifically to a feared/hated outsider group.” The gap must be closed by combining “misericordia” + explicit teaching, not by inventing a new term.

1.2 Repentance and Divine Mercy

Available Spanish termsWeaknessRecommended strategy
”arrepentirse” (used for BOTH shuv, human turning, and nacham, divine relenting)This is the single largest lexical gap in the book. Hebrew uses two distinct roots; Reina-Valera tradition collapses both into one Spanish verb familyKeep the Reina-Valera lexical choice (fixed by tradition and register) but mandate a clarifying teaching note at every divine occurrence (3:9, 3:10, 4:2) distinguishing “se vuelva/se arrepienta” (human, from sin) from “se arrepintió” (divine, anthropopathic change of announced course, not repentance from sin)
“ayuno,” “cilicio,” “cenizas”Latin American Catholic-influenced culture reads penitential acts as potentially meritorious (cf. promesas, Lenten penance, indulgence-adjacent folk piety)Teach explicitly: these are the outward expression of an inward turning God already perceives (3:10), not a payment that earns divine relenting — direct parallel to baseline’s grace-vs-merit caution
”maldad” / “el desastre,” “la calamidad” (ra’ah wordplay)Spanish has no single word spanning “moral evil” and “impending calamity” the way Hebrew ra’ah does; the required two-term solution risks losing the wordplay’s causal logic (their evil → the disaster)Use “maldad/mal camino” for the moral sense and “el desastre/la calamidad” for the judgment sense within the same verse (3:10), with an explicit note that one Hebrew word underlies both, and that removing the first removed the second
”perecer”None significantStandard; low risk

Doctrine-level gap: No missing vocabulary per se, but a collision of two distinct source concepts into one Spanish lexical family (arrepentirse) is the doctrine’s central translation challenge.

1.3 Human Reluctance versus God’s Universal Love

Available Spanish termsWeaknessRecommended strategy
”huyó” (barach)Bare verb; conveys the action but not the motiveTeaching notes must supply Jonah’s actual motive (resisting Gentile mercy, made explicit only in 4:2), since the verb alone reads as generic disobedience or fear
”se enojó grandemente” / “se disgustó” (charah)Natural tendency to soften intensity in formal registerPreserve full intensity; the book’s rhetorical shock depends on disproportionate anger at mercy, not at personal harm
”de la presencia de Jehová” (millifnei YHWH)Risk of flattening into “se fue lejos de Jehová,” which reads as simple distance rather than relational/vocational withdrawalRetain the “presencia” idiom; teach that this is not a claim of successful escape from an omnipresent God (reinforces Sovereignty doctrine)

Doctrine-level gap: No missing vocabulary; risk is entirely in under-teaching motive and intensity that the bare lexical choices do not themselves convey.

1.4 The Sovereignty of God over Creation

Available Spanish termsWeaknessRecommended strategy
”dispuso” / “preparó” (manah, used 4x: fish, plant, worm, wind)Spanish offers many synonyms (mandó, hizo venir, envió, causó) that a stylistically minded translator will be tempted to vary for eleganceFence this term rigidly: use exactly one verb across all four occurrences (1:17, 4:6, 4:7, 4:8) to preserve the deliberate structural refrain; stylistic variation here is a translation error, not an improvement
”tempestad” / “viento” (sa’ar/ruach)Passive constructions (“hubo una tempestad”) are natural and idiomatic in Spanish narrative styleActively resist the idiomatic pull toward passive voice; preserve “Jehová envió/hizo levantar” as active divine causation
”echaron suertes” (goral)Living cultural collision: cartomancy, Santería-adjacent divination, and popular “echar la suerte” practices remain active in parts of Latin America and the CaribbeanTeach as a one-time instance of God overruling a pagan practice for his own purposes, not an endorsement of divination
”una planta” (qiqayon)Genuine botanical-lexical gap — no settled Spanish equivalent exists across translation traditions (calabacera, ricino, hiedra all compete)Do not resolve the ambiguity; render generically with a translator’s note on species uncertainty, since the object lesson does not depend on botanical identity

Doctrine-level gap: The refrain-verb (manah) is not a missing-vocabulary problem but a discipline problem: Spanish’s rich synonym set is itself the risk, because it invites well-intentioned stylistic variation that destroys a deliberate structural signal.

1.5 Jonah as a Sign Foreshadowing Christ’s Resurrection

Available Spanish termsWeaknessRecommended strategy
”un gran pez” (dag gadol)Severe cultural-crowding risk: “Jonás y la ballena” is near-universal in Spanish-language popular culture, children’s Bibles, and casual reference, with zero textual basis in Hebrew or GreekRender strictly “un gran pez” / “un pez enorme”; explicitly correct “ballena” in every teaching note touching 1:17, since learners will arrive already carrying the false rendering
”tres días y tres noches”None lexically — the phrase is simple and stable in SpanishThe risk is entirely one of softening under stylistic pressure (e.g., “varios días,” “un tiempo”); this must never be paraphrased, since Matthew 12:40’s typological argument depends on the exact span
”el Seol”Overlap risk with “el infierno” (hell), a later, more theologically loaded NT/systematic categoryRetain transliterated “el Seol”; do not translate as “infierno,” which would import categories foreign to Jonah’s own OT horizon and overstate the text
”resurrección” (baseline reuse, cross-referenced conceptually, not textually present in Jonah itself)None — this is a baseline term applied typologically, not textually rendered within JonahWhen teaching material draws the Matthew 12:40 connection, reuse the baseline resurrection/resurrección entry exactly; do not coin a separate rendering for the typological connection

Doctrine-level gap: No missing vocabulary; the entire risk is cultural intrusion (the whale) and softening under paraphrase pressure (the three-day span), both requiring active correction rather than new terminology.


2. Missing Vocabulary vs. Crowded Semantic Neighborhoods

2.1 Genuine Missing-Vocabulary Gaps (Spanish lacks a precise equivalent)

Hebrew conceptGapWhy it is a true gap, not just a risk
רָעָה (ra’ah) — moral evil / calamity, single wordSpanish has no word spanning both senses; “mal” alone is too generic to carry either sense with precision, and “maldad” (moral) / “desastre” (calamity) are lexically unrelated to each otherThe wordplay linking Nineveh’s sin to Nineveh’s threatened judgment literally cannot be reproduced with one Spanish word; the connection must be made by teaching note, not lexical choice
נָחַם (nacham, of God) vs. שׁוּב (shuv, of humans)Spanish’s “arrepentirse” family covers both; there is no separate established Spanish theological term for “compassion-driven change of God’s announced course that is not repentance from sin”This is the deepest gap in the book: not merely a crowded neighborhood but an actual absence of a distinct target-language lexeme for a distinct source-language concept
קִיקָיוֹן (qiqayon)No settled Spanish (or English, or any modern language) botanical equivalent exists; the Hebrew itself is a hapax legomenon of uncertain speciesGenuine referential gap, not a doctrinal one; resolved by generic rendering + note, not by resolving the ambiguity artificially

2.2 Crowded Semantic Neighborhoods Requiring Fencing

These are cases where Spanish does have a workable term, but that term already carries strong associations from Catholic popular piety, folk religion, or secular popular culture that must be explicitly fenced off.

TermCrowding sourceFencing strategy
”Jehová”Must remain visually/lexically distinct from baseline’s fixed “Señor” (used for Christ’s kyrios in Romans) so learners do not casually flatten the OT covenant name into the NT lordship title, even though Christian theology ultimately unites themNever mix “Jehová” and versalita “SEÑOR” in the same document; use “Jehová” with total consistency throughout Jonah materials
”se arrepintió” (of God)Crowded by everyday Spanish “arrepentirse” = to feel sorry for one’s own sin/wrongdoingMandatory clarifying note at every occurrence (3:9, 3:10, 4:2); this is the OT-book counterpart to the baseline’s Critical handling of justicia imputada vs. infundida — a fixed lexical choice whose theological meaning must be actively taught, never assumed
”ayuno” / “cilicio” / “cenizas”Crowded by Lenten/penitential Catholic practice, where such acts can be popularly read as meriting forgiveness (promesas, indulgence-adjacent folk piety)Teach explicitly as outward signs of a turning God already sees, not payment; direct structural parallel to baseline’s grace-vs-merit-cooperation caution
”un gran pez”Crowded almost totally by “ballena” in popular culture and even in casual Christian usageActive correction required in every teaching note referencing 1:17; do not assume learners arrive without the false association
”misericordia”Crowded by devotional usage centered on the Virgin and the saints (“Madre de Misericordia,” “obras de misericordia” as meritorious acts)Anchor grammatically and contextually to God as sole subject and to Nineveh/Gentiles as object every time it renders chesed/chus
”echaron suertes”Crowded by living divinatory/cartomantic practice in parts of Latin America and the CaribbeanOne-time providential use, not endorsement; brief note required at 1:7
”proclama” / “pregona” (qara)Adjacent to, but must be fenced from, baseline’s “evangelio”Jonah’s message is judgment-proclamation, a distinct concept from the Pauline euangelion, even though the repentance-result foreshadows gospel dynamics; never substitute “evangelio” for Jonah’s qara
”creyeron a Dios” (he’eminu)Adjacent to, but must be fenced from, a weak “se impresionaron” / “tuvieron miedo” reading, and from the baseline’s Hindi/Spanish caution on inherited cultural religiosity vs. genuine “fe”Teach alongside baseline’s fe doctrine note: this is trust-that-produces-repentant-action, the OT’s clearest anticipation of Gentile faith apart from covenant history

2.3 Cross-Cutting Observation

Compared to the Romans baseline — where the dominant risk pattern was doctrinal collision (a Spanish word already carrying a rival Catholic-doctrinal meaning, e.g. “santos,” “intercesión,” “justicia”) — Jonah’s dominant risk pattern is structural and typological loss: the danger is less that a term will be doctrinally misread by a rival theological system, and more that (a) a single Hebrew lexical signal (manah, ra’ah, nacham/shuv) will be smoothed away by natural Spanish stylistic variation, or (b) a popular-culture intrusion (the whale) will simply overwrite the text. Only three Jonah terms — Jehová, se arrepintió, and the misericordia/ayuno family — carry the Romans-style doctrinal-collision risk profile; the rest are narrative-integrity risks.


3. Transliteration vs. Paraphrase Decisions

TermDecisionRationale
יְהוָה (YHWH)Transliterate/render as “Jehová” (not paraphrase as “el Señor” or “Dios”)Matches this Language Package’s RV1960/RVA2015 register anchor; preserves visual/lexical distinction from baseline’s “Señor” (Christ’s kyrios); Critical risk, zero deviation permitted
שְׁאוֹל (Sheol)Transliterate as “el Seol” (not paraphrase as “el infierno”)Avoids importing later NT/systematic categories into an OT term; matches most Spanish Bible traditions
קִיקָיוֹן (qiqayon)Paraphrase generically as “una planta” (not transliterate, not commit to a specific botanical term)No stable transliteration tradition exists in Spanish Bibles; false precision (calabacera/ricino/hiedra) would mislead more than a frank “uncertain species” note
נִינְוֵה (Nineveh)Use established Spanish Bible transliteration “Nínive”Standard across all Spanish Bible traditions; no ambiguity; doctrinal work is done by teaching notes generalizing to “the nations,” not by the term itself
תַּרְשִׁישׁ (Tarshish)Use established transliteration “Tarsis”Standard proper name; no risk
דָּג גָּדוֹל (dag gadol)Paraphrase as “un gran pez” / “un pez enorme” (explicitly reject transliteration or the popular “ballena”)The Hebrew is a common noun phrase, not a proper name; a literal, non-specific paraphrase is both accurate and the necessary corrective to the “whale” intrusion
אַבָּא-style retention (cf. baseline “Abba”)No direct Jonah equivalentNoted for completeness: Jonah contains no Aramaic term-of-intimacy comparable to Romans 8:15’s Abba; no transliteration decision needed here
אֵל חַנּוּן וְרַחוּם (El channun v’rachum)Paraphrase using the fixed Reina-Valera Exodus 34:6 formula “Dios clemente y misericordioso” (not a fresh translation)Preserves cross-passage Old Testament consistency for a recognizable liturgical/confessional formula rather than generating a novel, unfamiliar phrase
חֲרוֹן אַף (charon aph)Paraphrase as “su ardiente ira” / “el furor de su ira” (not a literal “el ardor de su nariz,” which would be unintelligible and comic in Spanish)Idiom requires functional paraphrase; literal transliteration/calque of a body-part idiom fails entirely in the target language
נָחַם / שׁוּבParaphrase only, both within the existing “arrepentirse” family per Reina-Valera precedent — no invented neologismIntroducing a novel Spanish term to distinguish the two roots would break register consistency with the established Bible-translation tradition this Language Package anchors to; the distinction must be carried by teaching notes, not new vocabulary

General principle applied: transliteration is reserved for proper names and one fixed covenant-name/afterlife-term pair (Jehová, Seol) where the target tradition already has a stable transliterated form; paraphrase is used everywhere else, including for idioms (charon aph) and referentially uncertain terms (qiqayon), following the same method the baseline used for “Abba” (retain) versus “gracia,” “fe,” etc. (paraphrase into the established Spanish equivalent).


4. Ranked List of Highest-Risk Ambiguities

Ranked by combined severity of doctrinal consequence and likelihood of translator/learner error, for this book specifically.

  1. נָחַם applied to God (“se arrepintió”) — Critical. The fixed Reina-Valera lexical choice collides with everyday Spanish “arrepentirse” (= repent of one’s own sin), risking either the implication that God sinned, or that God is capricious/unreliable in his word. Requires a mandatory clarifying note at every occurrence (3:9, 3:10, 4:2). Highest-risk item in the entire book; direct OT counterpart to the baseline’s Critical justicia imputada fault line.

  2. רָעָה wordplay (moral evil / calamity, 3:8, 3:10) — Critical. Spanish structurally cannot carry both senses in one word; requires two different renderings within the same short passage, risking either the loss of the wordplay (if rendered identically) or the loss of the causal link between sin and judgment (if rendered too divergently). Concentrated entirely within the core passage (3:1-10).

  3. “Un gran pez” vs. “una ballena” — High. Not an ambiguity in the source text but a near-universal destination-culture intrusion; every learner arrives with the wrong image pre-loaded from popular culture and children’s media, making this a correction task rather than a mere translation choice.

  4. שׁוּב vs. נָחַם lexical collapse (“arrepentirse” for both) — High. Two distinct Hebrew roots (human moral turning vs. divine compassion-driven course-change) collapse into one Spanish verb family across 3:8-10 and 4:2, creating a standing risk that learners will read divine “repentance” as structurally identical to human repentance from sin.

  5. “Jehová” vs. baseline “Señor” — Critical (consistency risk, not doctrinal-content risk). Because the Romans baseline has already fixed “Señor” as the rendering of Christ’s kyrios, any drift toward using “Señor” for YHWH in Jonah materials — or mixing “Jehová” with versalita “SEÑOR” — would create cross-curriculum inconsistency at the exact point (the divine name) where consistency matters most.

  6. “tres días y tres noches” — Critical, but low ambiguity in the source; the risk is entirely translator-side softening under stylistic pressure (“varios días,” “un tiempo”). Ranked above pure vocabulary problems because any deviation here severs the New Testament’s own typological argument (Matthew 12:40).

  7. “misericordia” (chesed, 2:8) — referent ambiguity — Medium-High. Genuinely debated among interpreters whether the referent is Jonah’s own covenant loyalty or God’s mercy; must be recorded as alternatives_considered and flagged for native speaker review rather than silently resolved.

  8. “echaron suertes” (goral, 1:7) — Medium. Low doctrinal stakes in the text itself, but real risk of unintended endorsement given active divinatory folk practice in parts of the Spanish-speaking world; requires a brief but explicit disclaiming note.

  9. “ayuno” / “cilicio” / “cenizas” as potential merit-language — Medium. Individually low-risk standard vocabulary, but cumulatively they form the passage’s most Catholic-popular-piety-adjacent cluster and must be anchored to 3:10’s “God saw” (inward reality precedes/produces the outward sign) to avoid a merit-cooperation reading.

  10. “dispuso”/“preparó” (manah) stylistic drift — Medium (structural, not doctrinal, but severity elevated because it is easy to miss). No single occurrence is individually high-risk, but inconsistent rendering across the four occurrences (1:17, 4:6, 4:7, 4:8) silently destroys the book’s clearest lexical argument for God’s sovereignty over all scales of creation, from worm to storm.


5. Summary Table: Gap Type by Doctrine

DoctrineDominant gap typePrimary mitigation
God’s Compassion for the NationsCrowded neighborhood (misericordia vs. Marian/saint piety)Anchor grammatically to God-as-subject, Gentiles-as-object
Repentance and Divine MercyTrue missing vocabulary (nacham/shuv collapse; ra’ah wordplay)Mandatory teaching notes; fixed lexical choices retained
Human Reluctance vs. God’s Universal LoveUnder-determination (bare verbs lack motive/intensity)Explicit motive/intensity teaching, not new vocabulary
Sovereignty of God over CreationStructural refrain at risk from Spanish’s synonym richnessRigid single-verb consistency rule (manah)
Jonah as a Sign Foreshadowing Christ’s ResurrectionCultural intrusion (ballena) + softening risk (three days)Active correction of popular culture; zero-tolerance on paraphrase softening

Cross-reference: analysis/08_core_glossary.md for the full term-by-term glossary this analysis justifies, and assets/bible_term_registry.json (Jonah extension) for the formal registry entries. This analysis assumes and never contradicts the baseline translation_memory.json (Romans) as the controlling language authority.

Library content is free and openly licensed under CC BY-NC-SA 4.0 — share and adapt it for non-commercial use, with attribution to tri-bible.ai.

Give feedback

How would you rate this page?

0 / 500 words