Log in

or use your email

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 Requirements bundle

Linguistic Gap Analysis

06 — Linguistic Gap Analysis: 1 Chronicles (German)

Curriculum: 1 Chronicles Destination language: German Source of authority: Baseline Romans translation_memory.json / bible_term_registry.json (German); extended by analysis/08_core_glossary.md and assets/bible_term_registry.json (1 Chronicles-specific) produced in this project. Generated: Phase 1, Step 8 Scope: Full-book coverage, 1 Chronicles 1–29. Core passage 1 Chronicles 17:1–15 (Davidic Covenant Reaffirmed) is the theological anchor for the deepest analysis but is not the boundary of this document’s scope.


0. Method and Full-Book Coverage Statement

This analysis works chapter-block by chapter-block across the entire book, identifying (a) where German lacks a clean one-to-one lexical equivalent for a Hebrew theological term (“missing vocabulary”), (b) where German has a serviceable term but that term already carries competing theological or secular freight from elsewhere in this translation pipeline or from general usage (“crowded semantic neighborhoods” requiring fencing), and (c) where the choice between transliterating a Hebrew form and paraphrasing/translating it materially affects doctrinal clarity.

Chapter coverage ledger (per the full-book-coverage mandate):

ChaptersContentGap-analysis relevance
1–9Genealogies, Adam→Israel’s tribes, post-exilic resettlement listReviewed. Generates the Völker/Heiden fencing issue (§2.1), the toledot pastoral-register issue, and the bene David / dynastic-continuity argument (§4).
10Death of SaulReviewed. Supplies ma’al (unfaithfulness) as the covenant-betrayal foil to 17:13’s chesed; no new lexical gap beyond what is catalogued.
11–12David’s mighty men, supporters at Hebron and ZiklagReviewed. Military-honorific vocabulary (“Helden,” “Kriegsleute”) is stable, low-risk German Bible vocabulary; no gap requiring fencing. Note: 11:3’s anointing of David is the mashiach/Gesalbter anchor (§2.3).
13Ark mishandling, death of UzzaReviewed. Founding negative case for qodesh (heilig) and ka-mishpat (“nach der Ordnung”) — see §2.4 and §3.
14David’s household, Philistine warsReviewed. No new load-bearing terms; standard narrative vocabulary.
15–16Ark procession, Levitical worship organized, David’s psalmReviewed. Generates meshor’rim/kelei-shir, ka-mishpat, and the berit…le’olam covenant-continuity bridge between the Abrahamic and Davidic covenants (§4).
17Davidic Covenant oracle (core passage)Deepest analysis: bayit, avdi, nagid, shem, malkhuto, kisse, ad-olam, covenantal father/son, chesed — see §1 and §4 throughout.
18–20Wars and victories, dedicated spoilsReviewed. Supplies hiqdish (dedicated spoils, 18:11) reinforcing the Temple-preparation thread; no new gap category.
21Census, plague, threshing floor of OrnanReviewed. Generates satan, malakh YHWH, mispar/limnot — see §2.6, §4.
22Temple preparation begins, “a house for my Name”Reviewed. Generates bayit lishmi as the direct fulfillment-citation of 17:11–12 — see §1.1, §4.
23–27Levites, priests, musicians, gatekeepers, treasurers, military/civil officials organizedReviewed. Generates avodah, machlekot, goral, lenabbe (prophesy with instruments) — see §2.5, §2.7.
28–29David’s charge to Solomon and the assembly, tavnit, freewill offerings, David’s deathReviewed. Generates tavnit, qahal, nedavah, levav shalem, ha-mamlakhah, barukh YHWH — see §1, §2, §4.

No chapter block is silently omitted. Chapters generating no new lexical-gap issue beyond what is already catalogued in the Core Glossary are explicitly noted as reviewed above rather than passed over.


1. Doctrine Vocabulary Matrix

For each of the five curriculum doctrines: the German terms available, their specific weaknesses for this book’s material, and the recommended handling strategy. This matrix assumes the baseline Romans package terms as fixed and non-negotiable wherever reused; the “weaknesses” column addresses risk introduced specifically by this book’s OT/genealogical/cultic register, not weaknesses in the baseline terms themselves.

1.1 The Davidic Covenant Reaffirmed (core doctrine, 1 Chr 17:1–15)

Sub-conceptAvailable German term(s)Weakness for this bookRecommended strategy
bayit (“house”)Haus (only serviceable option)German “Haus” carries the household/family sense of Hebrew bayit but does not automatically evoke “royal dynasty” the way the Hebrew wordplay does; a German reader sees three flat repetitions of “Haus” rather than the deliberate palace→temple→dynasty pun that is the chapter’s rhetorical engine.Render “Haus” uniformly (lexical consistency required), but mandate an explicit teaching-material gloss at each occurrence: Palast (17:1) / Tempel (17:4) / Dynastie (17:10,12,14). Do not attempt to solve this by varying the German word — that would destroy the very wordplay the exposition needs to surface.
malkhuto / ha-mamlakhah (“his kingdom” / “the kingdom”)Königreich, Königsherrschaft, Königtum, HerrschaftThe only linguistically “natural” German choice for a triumphant, generations-spanning royal-dominion promise is dangerously close to the fixed baseline phrase Reich Gottes (Kingdom of God), a Critical-risk NT theological term. Collapsing the two would prematurely equate David’s earthly dynasty with the New Testament’s eschatological Kingdom before the canon itself draws that line.Fence absolutely: never “Reich Gottes” for this OT referent. Use “(sein) Königreich” for the dynastic-dominion sense (17:11,14; 28:5) and “das Königtum” / “die Herrschaft” for the doxological, God-owns-everything sense (29:11). Theologian review mandatory for every occurrence; teaching notes may state the real convergence without merging vocabulary.
covenantal father/son (17:13)Vater / SohnThe obvious literal rendering (“Sohn”) sits one short step from the baseline’s fixed, Critical-risk Sohn Gottes (eternal, unique, co-equal divine Sonship of Christ). A German reader trained by this curriculum family’s NT material to hear “Sohn Gottes”-adjacent language as a deity claim is at real risk of importing that category here.Render plainly “Vater” / “Sohn,” with mandatory accompanying exposition stating that Solomon’s sonship is adoptive-covenantal, typological, and (per the very next clause about Saul) revocable in principle — categorically different from Christ’s ontological Sonship. Never construct the German sentence so that “Sohn Gottes” could be read as in apposition to Solomon.
chesed (“mercy/steadfast love,” 17:13)Gnade, Güte, TreueDirect collision with the baseline’s Reformation-freighted Gnade (High risk, reserved for NT unmerited, unilateral, merit-free salvific favor). Chesed here is covenant loyalty within an already-established relationship (contrasted explicitly with its withdrawal from Saul), not the initiating declaration of righteousness Luther’s “sola gratia” protects.Prefer Güte or Treue to reduce collision risk. If “Gnade” is used (defensible; it is the Lutherbibel’s own frequent choice), an explicit disambiguating note is mandatory, not optional. Theologian review required for every occurrence.
ad-olam (“forever,” 17:12,14)auf ewig, für immerHebrew ad-olam can, elsewhere in the OT, denote merely a long indefinite period rather than strict eternity — German “auf ewig” risks either under- or over-translating depending on which sense a translator defaults to.Full eschatological force required here (confirmed by the phrase’s later NT use, e.g. Luke 1:33); render “auf ewig,” never softened to “für lange Zeit.” Flag for theologian review whenever taught alongside NT fulfillment material.
nagid vs melek (“ruler,” 17:7)Fürst vs KönigGerman readers accustomed to “König David” throughout the rest of the canon will not spontaneously notice that Chronicles deliberately withholds “König” here in favor of a distinct term for divinely-commissioned appointment. Without flagging, the distinction simply disappears in translation.Render nagid as Fürst, reserving König for melek; mandatory teaching-material flag explaining the deliberate distinction, since the lexical choice alone will not carry the theological point for an unprimed reader.
avdi (“my servant,” 17:4,7)Knecht vs DienerRisk of conflation with the NT’s universal servanthood-of-all-believers ethical teaching (doulos-derived “Diener/Knecht” material elsewhere in this pipeline). Here it is a specific royal-covenantal office conferred on one man.Render Knecht (established Lutherbibel register: “David, meinem Knecht”), never the flatter “Diener.” Teaching material must distinguish the royal-office sense from the universal-ethical sense taught elsewhere.
shem (“a name,” 17:8) / “house for my Name” (22:10)NameDeuteronomic Name-theology (God’s Name as mode of dwelling-presence, not a claim that the Temple contains the whole of God) has no single German lexical equivalent — it must be taught as a motif, not translated as a discrete term.Keep “Name” lexically identical at both 17:8 and 22:10 so the thread is traceable; supply explicit motif-level teaching material rather than relying on the word alone to carry the theology.
kisse (“throne,” 17:12,14)ThronStraightforward lexically, but carries direct messianic-eschatological freight for any German reader who knows Luke 1:32–33 — risk is over-collapsing OT immediate referent (Solomon and successors) into NT ultimate referent (Christ) without distinguishing them.Render “Thron” plainly; theologian review mandatory whenever taught alongside NT fulfillment texts, to keep both referents present and distinguished.

1.2 Genealogy and the Continuity of God’s People

Sub-conceptAvailable German term(s)Weakness for this bookRecommended strategy
toledot (“generations/genealogy”)Geschlechterregister, StammbaumLexically unproblematic; the risk is entirely pastoral/reception-level — German devotional-reading habits (narrative-driven) predispose readers to treat chs. 1–9 as skippable administrative filler.No lexical fix required; mandatory framing note in all teaching material stating explicitly that the genealogy is itself a theological claim (unbroken covenant continuity), not throat-clearing.
ammim/goyim (pre-covenant-contrast “peoples/nations,” ch. 1) vs goyim (covenant-contrast “Gentiles”)Völker vs HeidenBoth Hebrew words can be rendered by the same German lexeme, but the baseline’s Heiden carries an inherited pejorative “uncivilized pagan” register only appropriate where the text itself draws an explicit Jew/Gentile covenant contrast. Chapter 1’s genealogical tables draw no such contrast.Fence strictly: Völker for neutral kinship-table listings (ch. 1); reserve Heiden exclusively for explicit covenant-contrast contexts consistent with the baseline’s gentiles entry. This is a “same source word, two German target words” split that must be governed by context, not left to translator discretion segment-by-segment.
bene David (“sons of David,” ch. 3)die Söhne Davids / die davidische LinieNo lexical gap, but a real conceptual gap: a bare post-exilic genealogical list will not, on its own, signal to a German reader that this is the book’s own narrative proof that the ch. 17 “forever” promise survived the Exile.Mandatory explicit cross-reference in teaching material connecting ch. 3 to ch. 17’s eternal-dynasty promise; the lexical choice itself carries none of this weight unaided.

1.3 Worship and the Levitical Order

Sub-conceptAvailable German term(s)Weakness for this bookRecommended strategy
qahal (“assembly”)Versammlung vs. baseline GemeindeThe Septuagint itself sometimes renders qahal with ekklēsia, making a typological OT→NT link theologically legitimate to note — but the baseline’s Gemeinde is fixed, Critical/High-risk, for the NT body-of-Christ doctrine. Using it here would silently equate Israel’s OT convened assembly with that fixed NT category.Render Versammlung exclusively for 1 Chronicles’ qahal (13:2; 28:1; 29:1,10,20); typological continuity may be noted in teaching material but the vocabulary itself must stay fenced apart from Gemeinde.
ka-mishpat (“according to the ordinance,” 15:13)nach der Ordnung, wie es sich gebührtNo lexical gap; the risk is that this reads, absent framing, as an incidental procedural detail of the Uzza narrative rather than the book’s own explicit statement of its central worship-order doctrine.Flag in teaching material as the load-bearing verse for “Worship and the Levitical Order” as a whole, directly parallel to 17:1–2’s warning against human initiative determining the terms of worship.
goral (“lot,” 24:5,31; 25:8; 26:13–14)LosGenuine false-friend risk: contemporary German “Los” primarily evokes the secular lottery (Lotterie, Glücksspiel), which would read the practice as superstitious chance-taking rather than a means of discerning divinely-ordained order.Retain Los (no better single-word alternative exists) but mandate an explicit framing note in every occurrence’s teaching material distinguishing “Los” here from secular lottery/gambling connotations.
lenabbe (“to prophesy [with instruments],” 25:1,3)weissagen (mit Musikinstrumenten)Two failure modes to guard against: (a) flattening to “musizieren” (mere music-making), losing the theological claim entirely; (b) over-reading into ecstatic/occult prophecy, importing an unwarranted charismatic-phenomenology frame.Use the baseline’s Weissagung root explicitly (“weissagen mit Musikinstrumenten”), with a teaching note threading the needle between the two failure modes — this is a distinctive claim about the dignity of ordained worship music, not either extreme.
ohel vs mishkan (17:5)Zelt vs StiftshütteBoth occur in a single verse; collapsing both to a generic “Zelt” erases a distinction the Hebrew text itself makes between ordinary tent-imagery and the specific consecrated wilderness sanctuary structure.Render ohel = Zelt, mishkan = Stiftshütte (established German technical term); never collapse.
avodah (“service/duty/worship-labor,” 23:24,28,32)DienstGerman “Dienst” fortunately spans both the secular “duty” and religious “(Gottes-)Dienst” senses, making it an unusually good match — but German readers will not automatically notice that the Hebrew is deliberately blurring labor and worship rather than simply reusing one convenient word.Retain Dienst; supply a brief teaching note surfacing the deliberate Hebrew blur as a point of theological interest rather than assuming the overlap is self-evident.

1.4 Preparation for the Temple

Sub-conceptAvailable German term(s)Weakness for this bookRecommended strategy
tavnit (“plan/pattern,” 28:11–12,19)Bauplan, VorbildThis is a claim of direct revelatory origin for architectural/organizational design (“by the Spirit,” 28:12), paralleling Exodus 25:9 — a claim in direct tension with the historisch-kritische Methode’s strong influence in German academic theology, which tends to read such claims as human literary/religious construction.Render Bauplan; mandatory theologian review connecting explicitly to the baseline’s inspiration_of_scripture doctrine caution, so the revelatory claim is not silently naturalized in teaching material.
satan (21:1)Satan (transliteration/established proper name)Genuine, unresolved theological tension with the 2 Samuel 24:1 parallel, which attributes the same incitement directly to the LORD’s own anger — a real compatibilism/problem-of-evil question, not a translation problem per se.Transliterate as the established German proper name Satan; theologian review mandatory, presented transparently without forced harmonization the text itself does not supply.
mispar/limnot (“census,” 21:1–8)Zählung, VolkszählungReal over-reading risk: German teaching material could imply census-taking itself is sinful, when Numbers 1 shows Moses commanding one; the culpability here is specifically David’s motive and its national consequence.Render Volkszählung plainly; mandatory framing note distinguishing the act from its specific sinful occasion here.
menuchah (“rest,” 22:9)RuheConceptually adjacent to, but distinct from, the baseline’s peace/peace_with_god = Friede doctrine; risk of conflating a concrete geopolitical precondition-for-building with the NT’s relational peace-with-God-through-justification.Render Ruhe; keep explicitly distinguished from Friede in any comparative teaching material.

1.5 God’s Faithfulness across Generations

Sub-conceptAvailable German term(s)Weakness for this bookRecommended strategy
barukh YHWH (doxological “blessed be the LORD,” 16:36; 29:10,20)Gepriesen sei der HERR, Gelobt sei der HERRThe tempting literal-cognate shortcut is “gesegnet” or even “selig” — but selig is the baseline’s fixed, Critical-risk term reserved exclusively for the Matthean Beatitudes’ makarios, a categorically different (state-of-blessedness vs. doxological-ascription) grammatical and theological construction.Never use selig here. Use Gepriesen/Gelobt sei der HERR; German already correctly distinguishes doxological praise from beatitude-blessedness, and this distinction must be actively preserved rather than collapsed for translation convenience.
barakh/berakhah (“bless/blessing,” 4:10; 17:27)segnen, SegenSits in the same crowded neighborhood as barukh above and selig — three related but theologically distinct German words for three distinct categories risk bleeding into one another if not kept fenced.Retain segnen/Segen for the impartation-of-favor sense; keep visibly distinct from both the doxological formula and from selig.
bachar (“elect/choose,” 28:4–6,10; 29:1)Erwählung, erwählen (baseline REUSED)German Reformed and Lutheran communities carry differing systematic emphases (double predestination vs. pastoral-comfort framing); this book narrates a concrete historical selection (Judah, David’s house, Solomon specifically over his brothers) rather than a systematic soteriological claim.Reuse baseline term exactly; theologian review should note that this is narrated historical election, and avoid imposing either tradition’s full systematic apparatus onto the narrative.
ha-kol mi-yadkha (“all things from your hand,” 29:14,16)alles kommt von dir / aus deiner HandNo lexical gap; conceptual risk is that David’s climactic confession, if not connected explicitly to the baseline’s providence/power_of_god doctrines, reads as pious sentiment rather than the theological ground that undercuts any works-righteousness misreading of the chapter’s freewill offerings.Render plainly; mandatory teaching-note linkage to Vorsehung/Kraft Gottes and to the freewill-offering material in the same chapter.

2. Missing Vocabulary vs. Crowded Semantic Neighborhoods

2.1 True Missing-Vocabulary Cases (no adequate single German word exists)

These are cases where German simply has no lexeme that carries the Hebrew concept’s full weight, requiring paraphrase plus mandatory exposition rather than a one-word substitution:

  • bayit polysemy (§1.1): no German word does triple duty as palace/temple/dynasty the way bayit does. “Haus” is retained for lexical consistency, but the theological point itself must be delivered entirely through teaching-material exposition, not through the word choice.
  • Name-theology (shem): German “Name” is the correct cognate but carries none of the Deuteronomic dwelling-presence theology on its own. Must be taught as a motif across 17:8 and 22:10, not translated as a self-explanatory term.
  • tavnit as revelatory architectural blueprint: “Bauplan” is adequate for the concrete referent but carries no inherent sense of “received by direct revelation” — German readers will need explicit exposition to avoid reading this as David’s own design genius.
  • The avodah labor/worship blur: German “Dienst” is a fortunate near-match (see §1.3) but the deliberateness of the Hebrew ambiguity is not self-evident and needs surfacing.
  • The chesed/covenant-loyalty concept generally: German has no single word that means “steadfast, relationship-internal covenant loyalty” as opposed to either merit-based reward or unilateral unmerited grace. Every occurrence needs case-by-case judgment between Güte, Treue, and (with mandatory gloss) Gnade.

2.2 Crowded Semantic Neighborhoods Requiring Fencing

These are cases where German does have a usable word, but that word is already claimed, in this translation pipeline or in general usage, by a different theological concept — creating collision risk that must be actively fenced rather than left to default usage:

German word/rootCompeting claimantsFencing rule
HausOrdinary household; royal palace; Temple; dynasty; (unrelated) “das Haus Israel” idiom elsewhere in OT usageFence by explicit parenthetical gloss at every 1 Chr 17 occurrence (Palast/Tempel/Dynastie); never let context alone carry the disambiguation.
Königreich / ReichBaseline’s fixed Reich Gottes (Kingdom of God, NT)Absolute fence: 1 Chronicles’ malkhuto/ha-mamlakhah NEVER rendered “Reich Gottes.” Use Königreich/Königtum/Herrschaft exclusively.
SohnBaseline’s fixed Sohn Gottes (eternal divine Sonship of Christ)Absolute fence: 17:13’s covenantal father/son language rendered plainly “Sohn,” explicit exposition that this is NOT “Sohn Gottes.”
GnadeBaseline’s fixed NT unmerited-favor doctrine (Reformation “sola gratia”)Fence via preference for Güte/Treue at 17:13; if Gnade used, mandatory disambiguating note every time.
HerrEveryday German “Mr.” address form (no protective honorific exists, per baseline caution) — intensified here by ch. 17’s unusually dense first-person divine speechExisting baseline caution applies with added force: flag ch. 17 specifically as a passage where the flattening risk is compounded by direct divine first-person discourse.
seligBaseline’s fixed Matthean Beatitudes’ makariosAbsolute fence: never for barukh (doxological) or barakh (impartation-blessing). Use gepriesen/gelobt or segnen respectively.
GemeindeBaseline’s fixed NT ekklesia/body-of-Christ doctrineAbsolute fence: OT qahal rendered Versammlung exclusively; typological continuity noted, vocabulary not merged.
MessiasBaseline’s fixed eschatological Anointed OneAbsolute fence: OT royal anointing of David/Solomon (mashiach) rendered Gesalbter, never “Messias,” within the book’s own narrative text.
PriesterContemporary German Catholic/Protestant clerical-office connotationsFence via teaching note distinguishing hereditary Aaronic cultic office from modern denominational office; no lexical substitute needed, just framing.
LosSecular Lotterie/Glücksspiel connotationFence via mandatory framing note (see §1.3); no better lexical alternative exists, so the fence must be exposition-based rather than word-choice-based.
Engel des HERRNPopular-culture “guardian angel” folk pietyFence via teaching note: this is a specific theophanic judgment/mercy agent tied to the Temple site’s identification, not generic protective-angel imagery.
ZeltBoth ohel (ordinary tent) and mishkan (technical Tabernacle term) if collapsedFence: Zelt for ohel only; Stiftshütte reserved for mishkan.
VaterOrdinary genealogical patriarch sense vs. 17:13’s specific covenantal-adoptive divine fatherhood senseFence via context-flagging at 17:13 specifically, paired with the Sohn/Sohn-Gottes fence above.

2.3 Genuinely Absent Concepts (no gap resolution needed, only awareness)

  • The distinction between nagid and melek has no felt equivalent gap in German (Fürst/König both exist and are usable) — the risk here is not vocabulary absence but reader default-blindness to a distinction the source text draws deliberately. This is a teaching-material problem, not a lexical one.
  • Similarly, the OT “Spirit came upon” episodic-empowerment formula (ruach, 12:18; 28:12) has an adequate German rendering (Heiliger Geist, reused from baseline) but readers moving between this OT curriculum and NT curricula in the same pipeline risk importing the NT’s permanent indwelling doctrine backward into these OT texts, or vice versa flattening the NT doctrine into episodic terms. Flag, do not attempt a different German word.

3. Transliteration vs. Paraphrase Decisions

TermDecisionRationale
Satan (21:1)Transliterate (Satan)Established German proper-name convention; no paraphrase improves clarity, and the term’s identity as a specific agent (not an abstract force) is best preserved by treating it as a name.
Abba (not in this book’s Hebrew text, but relevant boundary note)N/A — not applicable to 1 Chronicles’ own textIncluded only to note that this book contains no Aramaic intimacy-term equivalent; no decision required.
mashiach (royal anointing, 11:3; 29:22)Paraphrase (Gesalbter), NOT transliterate/borrow “Messias”Transliteration-adjacent borrowing here would import the baseline’s fixed eschatological term into a purely historical royal-installation narrative; paraphrase preserves the historical-typological distinction.
nagid (17:7)Paraphrase (Fürst), not transliterateNo benefit to transliterating a common royal-title noun; the theological point (distinct from melek) is carried by choosing a distinct existing German royal title, not by importing a foreign term.
tavnit (28:11–12,19)Paraphrase (Bauplan/Vorbild)A transliterated “Tavnit” would communicate nothing to a German reader; the architectural-blueprint sense translates cleanly enough that paraphrase plus theological framing is sufficient.
chesed (17:13)Paraphrase (Güte/Treue, or glossed Gnade), NOT transliterateTransliterating “Chesed” (as is sometimes done in specialist theological literature) would be opaque to this curriculum’s general lay/mixed-confession audience; paraphrase with mandatory disambiguation note is the better fit for the target reading level (see baseline’s “Die Zeit feature-article register” standard).
goral (24:5,31; 25:8; 26:13–14)Paraphrase (Los)“Los” is the natural, already-idiomatic German rendering; transliteration would serve no purpose.
Proper names (Nathan, Ornan/Arnan, Zadok, Ahimelech, Asaph, Heman, Jeduthun, etc.)Transliterate using established German Bible forms (Lutherbibel 2017 / Einheitsübersetzung conventions)Consistency with the baseline’s existing transliteration-standards section; do not innovate new German spellings for names already fixed in German Bible tradition.
bayit lishmi (“house for my Name,” 22:10)Paraphrase (ein Haus für meinen Namen), not a fixed idiom transliterationThis is a full clause, not a single lexeme; paraphrase that preserves the bayit and shem vocabulary already fixed elsewhere is required for cross-reference traceability to 17:11–12.
qahal (13:2; 28:1; 29:1,10,20)Paraphrase (Versammlung), not “Gemeinde,” not transliterationSee §2.2 fencing rule; a German-native word correctly distinguishes this from the fixed NT term without needing a foreign borrowing.
ad-olam (17:12,14)Paraphrase (auf ewig)A calque/transliteration is neither possible nor desirable for this common adverbial phrase; the risk lies entirely in degree of German rendering (see §1.1), not in translit-vs-paraphrase mode.

General rule derived from this table: 1 Chronicles contains almost no cases where transliteration is the correct choice for a common-noun theological term (Satan is the sole clear exception, and it is a proper name, not a common noun). Every other genuine gap in this book is best handled by careful German paraphrase plus mandatory exposition, never by importing an unglossed Hebrew loanword — this differs somewhat from other curricula in this pipeline (e.g., Abba, Immanuel, Ich bin) where transliteration-plus-translation was the established pattern, because those NT terms already carry fixed liturgical German reception history that this book’s OT technical vocabulary does not share.


4. Ranked List of Highest-Risk Ambiguities

Ranked by combined severity (doctrinal centrality × probability of silent misreading by a German lay reader), drawing on §1–3 above:

  1. דָּתן malkhuto/ha-mamlakhah vs. Reich Gottes (17:11,14; 28:5; 29:11) — Critical. The single highest-consequence fencing decision in the book: collapsing OT dynastic promise into the fixed NT eschatological phrase would flatten a developing biblical-theological argument the canon itself develops gradually.
  2. Covenantal father/son (17:13) vs. Sohn Gottes — Critical. Direct risk of importing this curriculum family’s own NT Christological vocabulary backward into an OT adoptive-covenant idiom.
  3. bayit polysemy across 17:1–14 — Critical. The chapter’s central rhetorical reversal (David wants to build God a house; God will build David a house) depends entirely on a wordplay German “Haus” does not automatically carry.
  4. chesed vs. Gnade (17:13) — Critical. Reformation-freighted German vocabulary sits directly on top of a distinct OT covenant-loyalty concept; mishandling here risks either trivializing chesed or over-freighting it with sola-gratia doctrine it does not carry in this verse.
  5. “a house for my Name” (22:10) as fulfillment-citation of 17:11–12 — Critical. If the bayit/shem vocabulary threads are not kept identical across these two passages, German readers lose the book’s own clearest self-referential proof of covenant fulfillment.
  6. ad-olam eternality (17:12,14) — Critical. Softening risk (“für lange Zeit”) would blunt the eschatological force that later canonical usage (Luke 1:33) depends on.
  7. Herr/Mr. flattening, intensified by ch. 17’s first-person divine speech density — Critical. The existing baseline caution applies with unusual force here because so much of the chapter is God speaking in his own voice through Nathan; a flattened “Herr” undercuts the entire oracle’s gravity.
  8. qahal vs. Gemeinde (13:2; 28:1; 29:1,10,20) — High. A single wrong lexical choice would silently equate Israel’s OT convened assembly with the fixed NT ekklesia doctrine this pipeline has carefully built elsewhere.
  9. nagid vs. melek/König (17:7) — High. The distinction is real and deliberate in the source but invisible to a German reader unless actively flagged; risk of complete loss without any translation “error” occurring.
  10. Anointed (Gesalbter) vs. Messias (11:3; 29:22) — High. Readers primed by other curricula in this pipeline to hear “Messias”-adjacent material as an eschatological claim may misread routine OT royal installation as messianic in the full sense.
  11. Throne (17:12,14) — OT immediate referent vs. NT ultimate referent — High. Requires deliberate double-teaching (Solomon and Christ) rather than collapsing into either alone.
  12. word of God (17:3) vs. Nathan’s own opinion (17:2) — High. If German phrasing doesn’t clearly mark the shift from human counsel to divine revelation, the chapter’s most basic narrative-theological hinge disappears.
  13. tavnit as revelation, not human design (28:11–12,19) — High. Direct collision with German academic theology’s historisch-kritische default reading habits.
  14. Satan/adversary (21:1) vs. 2 Samuel 24:1’s divine-incitement account — High. Genuine unresolved theological tension requiring transparent, non-harmonized presentation.
  15. Angel of the LORD (21:12–30) vs. folk “guardian angel” piety — High. Popular-culture default association actively works against the text’s specific theophanic sense.
  16. Völker vs. Heiden fencing in the genealogical tables (ch. 1) vs. covenant-contrast passages elsewhere — Medium-High. Using the wrong one imports either false neutrality or unwarranted pejorative freight.
  17. barukh YHWH vs. selig (16:36; 29:10,20) — Medium (but conceptually load-bearing for doctrinal precision across the whole pipeline’s Beatitudes vocabulary). Easy to get right once flagged, easy to get silently wrong if not.
  18. goral (Los) vs. secular lottery association (24:5,31; 25:8; 26:13–14) — Medium. Real false-friend risk in ordinary contemporary German usage.
  19. Census (21:1–8) — act vs. motive culpability — Medium-High. Risk of implying the wrong entity (the census itself, rather than David’s specific motive) bears the guilt.
  20. ohel vs. mishkan (17:5) — Medium. Low doctrinal stakes individually, but a clean test case for whether translators are attending to single-verse internal Hebrew distinctions at all.

5. Summary Recommendation for Phase 2 Handoff

The 1 Chronicles curriculum’s linguistic risk profile differs structurally from the NT-only baseline curricula already processed in this pipeline: instead of primarily new vocabulary requiring fresh German coinage, the dominant risk pattern here is boundary maintenance — keeping a comparatively small set of already-fixed, high-value German theological words (Reich Gottes, Sohn Gottes, Gnade, Gemeinde, selig, Messias) from being pulled, by superficial lexical similarity or thematic proximity, into OT contexts where the baseline has deliberately reserved them for later NT fulfillment. Phase 2 segment translation must therefore treat every occurrence of bayit, malkhuto/ha-mamlakhah, the covenantal father/son idiom, chesed, qahal, mashiach (royal sense), and the doxological barukh formula as an automatic theologian-review trigger regardless of whether the individual sentence “reads fine” in isolation — the risk in this book is systemic vocabulary-boundary erosion across many small, individually low-stakes-looking decisions, not a small number of single catastrophic mistranslations.

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