Work with us

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

Translation Landscape

Translation Landscape

Existing English Bible translations

Unlike every other Language Package in this pipeline, English has an enormous and mature landscape of Bible translations spanning several distinct philosophies: formal-equivalence translations (ESV, NASB, KJV/NKJV) that preserve source-language structure and traditional theological vocabulary closely; dynamic-equivalence translations (NIV, NLT) that prioritize natural contemporary English readability; and paraphrases (The Message) that prioritize idiomatic accessibility over formal precision. Per this repo’s site-wide copy rule, all scripture references in published site material use the NLT specifically.

Why this curriculum must still flag translation-landscape risk

  • No translation choice can fix a false-friend problem that exists in the receptor culture, not the receptor language: formal-equivalence translations retain “justification” and “propitiation” with maximum precision but do nothing to correct a reader’s independently-acquired everyday definition of “justify.” Dynamic-equivalence translations sometimes paraphrase around a term (e.g. rendering some grace-language more periphrastically) but at the cost of losing the technical vocabulary needed for careful doctrinal teaching later in the same book. Neither approach alone solves the problem this Language Package documents, because the problem is not the translation’s wording but the reader’s independently-acquired secular definition of the English word regardless of which translation supplies it.
  • English translations do not, and cannot, adjudicate denominational disagreement: no published English Bible translation takes a side on whether “being saved” is a datable past event or a lifelong process, or on the relationship between grace and works — these are downstream interpretive questions every English translation leaves to the reader’s own theological tradition, which is exactly why this curriculum’s doctrine_risk_registry.json must state its own position transparently rather than assume the translation itself settles the question.
  • Existing translations were not designed to name secular-culture false-friend risk explicitly: no mainstream English Bible translation’s translator’s preface anticipates that “election” will be read through a political-voting lens, or that “providence” will register mainly as a Rhode Island place name; this is a gap specific to this curriculum’s pedagogical purpose, not a flaw in the underlying translations themselves.

Readiness assessment

English is, in one sense, maximally “ready” for this curriculum, since there is no foreign-language rendering task at all. But this Language Package’s central finding is that readiness at the word level (every term is already in perfectly correct English) does not guarantee readiness at the meaning level — several of Romans’ most theologically load-bearing English words have been quietly colonized by secular, legal, or denominational meanings that this curriculum must actively name and correct rather than assume settled by the mere presence of the “correct” word on the page.