Bible How Translation Is Done

---
name: bible-how-translation-is-done
description: "Use when you need to know how a Bible translation is actually produced — the governing committee and translation-philosophy document, choosing base texts (BHS and BHQ, NA28/UBS5, the Septuagint for the deuterocanon, the Textus Receptus exceptions), drafting, review and committee votes (the NIV's Committee on Bible Translation, the CSB oversight committee), the recurring disputes (the textual base, word meaning and Barr's root fallacy, gender language, the divine name, loaded terms like doulos and Ioudaioi, textual footnotes, wordplay), translation theory from formal and dynamic equivalence to skopos, relevance theory and foreignizing; or how minority-language field translation works in 2026 — the Wycliffe scale figures, mother-tongue translators and consultants, the eight stages from exegesis through comprehension testing, back translation and consultant check, Paratext, Scripture Forge, Serval AI drafting, and oral and sign-language translation. Skill 3 of 9 of the From Autograph to Your Bible reference."
---

# How the Bible Is Actually Translated

> **Skill 3 of 9** of the *From Autograph to Your Bible: A Deep Dive into the Biblical Languages, Translation, Textual Criticism, Archaeology, and Historical Method* reference
> (plugin `biblical-languages-texts-archaeology-and-history`), carrying source Part II, *How the Bible Is Actually Translated*: §6–§7 — major-language committee translation and minority-language field translation. Sibling skills:
> `bible-hebrew-aramaic-and-greek` (§1–§2 — Biblical Hebrew and Aramaic, Koine Greek and the Septuagint),
> `bible-latin-german-and-english` (§3–§5 — the Latin, German and English Bibles and the registers they created),
> `bible-textual-criticism` (§8–§13 — copying errors, the reasoning, NT and Hebrew Bible textual criticism, the CBGM and the digital tools),
> `bible-archaeology` (§14–§22 — fieldwork, stratigraphy, dating, the science toolbox, epigraphy, the big debates and the 2026 finds),
> `bible-history-and-historical-method` (§23–§28 — the historian's method, ancient history, the historical-critical toolkit, the historical Jesus and reading a consensus),
> `bible-forgeries-looting-and-provenance` (§29–§31 — why provenance matters, the forgery and looting case files, and archaeology and politics),
> `bible-three-verses-through-the-pipeline` (§32–§34 — Isaiah 7:14, Deuteronomy 32:8 and Luke 2:1–2 through every discipline),
> `bible-reference` (front matter, §35–§38 and sources — how to use the reference, learning paths, free tools, the glossary, the open questions and the sources consulted).
>
> Section numbers are **the source's own and shared across the whole set**: a reference written
> as §N → `skill` points into that sibling skill.

> **Confidence markers are the source's own**, and this skill keeps every one where the source
> put it: **\[settled\]** broad consensus across confessional and secular scholarship ·
> **\[majority\]** the mainstream position, with a live minority dissent worth knowing ·
> **\[contested\]** genuinely disputed among competent specialists; no consensus ·
> **\[as of 2026\]** a status fact likely to change (editions in progress, statistics, new
> finds). The source was compiled on September 30, 2026, and its \[as of 2026\] facts were
> checked against live sources that day. They have not been re-checked for this pack — treat
> each as dated, and verify it before relying on it.

> **Pack orientation** (the pack's words, not the source's): Part II of the source, whole: how translation actually happens in the two very different
> worlds the source distinguishes. The textual-criticism decisions a committee inherits in
> §6.2 are made in §8–§13 → `bible-textual-criticism`, and the Hebrew and Greek words it
> argues over are introduced in §1–§2 → `bible-hebrew-aramaic-and-greek`.

## Part II — How the Bible Is Actually Translated

There are two very different worlds of Bible translation, and most popular discussion only knows the first:

1. **Major-language committee translation** — scholarly committees producing (or revising) a Bible in English, German, Spanish, etc., usually for a publisher.
2. **Minority-language field translation** — mother-tongue teams, often with organizations like Wycliffe, SIL, United Bible Societies, Pioneer Bible Translators, or Seed Company, translating into languages that may have no Bible and sometimes little written literature.

## §6 Major-language committee translation: the real workflow

### §6.1 Step 0 — Governance and a translation philosophy document

Before any verse is translated, a sponsor (publisher, Bible society, or church body) sets up a governing committee and a written **translation philosophy**: target readership, reading level, stance on formal vs functional equivalence, how to handle gendered language, the divine name, weights and measures, textual footnotes, and which source texts to use. This document is the constitution translators will argue from for years.

### §6.2 Step 1 — Choosing the base texts (this is where textual criticism enters)

Nearly all modern Protestant and Catholic translations use:

- **Old Testament:** BHS (moving toward BHQ as fascicles appear), with departures when the committee judges the Dead Sea Scrolls, Septuagint, or other versions preserve a better reading. These departures are usually footnoted ("Hebrew *X*; Septuagint *Y*").
- **New Testament:** NA28/UBS5 (with the NA29 changes to come — Part III, §11.1 → `bible-textual-criticism`). Committees can and do depart from the printed Greek, but rarely.
- **Deuterocanon/Apocrypha:** Göttingen or Rahlfs Septuagint; for Sirach, the Hebrew manuscripts from the Cairo Genizah, Qumran, and Masada.

Exceptions: the KJV/NKJV/MEV and some others keep the **Textus Receptus** for the New Testament; Orthodox translations may use the Patriarchal Greek text or the Septuagint as their Old Testament.

### §6.3 Step 2 — Drafting, reviewing, voting

A typical modern pattern (details vary by project):

1. **Book specialists draft.** A scholar expert in (say) Isaiah drafts or revises Isaiah, with exegetical notes explaining every nonobvious decision.
2. **Review teams critique.** Other scholars comment; a second draft emerges.
3. **Stylists and English readers.** Literary consultants read aloud for rhythm, clarity, and suitability for public reading (the KJV companies also read drafts aloud).
4. **The central committee votes.** For the NIV, the Committee on Bible Translation — a self-perpetuating panel of about fifteen scholars first constituted in 1965 — meets annually and votes on proposed changes, reportedly requiring a supermajority of about 70% for a change to pass. The ESV and CSB use oversight committees in a similar role; the CSB's ongoing decisions rest with a ten-member Translation Oversight Committee.
5. **Consultation and testing.** Some projects test drafts with target audiences (children's Bibles, reading-level Bibles, audio Bibles).
6. **Publication — then maintenance.** Translations are living texts. NIV committee annual meetings produce small revisions; publishers "lock" texts for long periods for stability (Crossway has said it does not plan frequent ESV updates).

### §6.4 Step 3 — The problems translators argue about most

**(a) The textual base** — Do we print "only Son" or "only God" at John 1:18? Include Mark 16:9–20 in the main text with a note, or bracket it? (Part III — §11.7 → `bible-textual-criticism`.)

**(b) Word meaning** — Lexical semantics has moved far from 19th-century etymology-driven methods. The landmark critique was **James Barr's** *The Semantics of Biblical Language* (1961), which exposed the **root fallacy** (a word means what its root "originally" meant) and **illegitimate totality transfer** (loading every possible sense of a word into each occurrence). D.A. Carson's *Exegetical Fallacies* popularized these warnings. Modern practice: meaning is determined by **usage in context**, with semantic domains (Louw-Nida) and cognitive/frame semantics.

**(c) Gender language** — Should Greek *adelphoi* be "brothers" or "brothers and sisters" when a mixed audience is plainly addressed? Should *anthrōpos* be "man" or "person"? The TNIV (2002/2005) triggered a major evangelical dispute; the 1997 **Colorado Springs Guidelines** set out a restrictive position. Today, NRSVue, NIV 2011, CEB, and NLT are more inclusive for human referents; ESV, NASB, LSB, and CSB are more conservative (the CSB occupies a middle position). Almost no mainstream translation changes gendered language for God.

**(d) The divine name** — "LORD" (the long tradition), "Yahweh" (LSB, HCSB in some places, Jerusalem Bible), "Jehovah" (ASV; a hybrid form from Hebrew consonants plus the vowels of *Adonai*), "the Eternal."

**(e) Loaded terms** — Greek *doulos*: "slave" or "servant"? *Ioudaioi* in John: "the Jews" or "the Judeans"/"the Jewish leaders"? Paul's *sarx*: "flesh," "sinful nature," "human nature"? *Dikaiosynē theou*: "righteousness of God" or "God's saving justice"? Each choice encodes an exegetical — sometimes theological — position.

**(f) Textual footnotes** — How many to include? Modern readers are often surprised by them, but they are an honesty mechanism.

**(g) Poetry, wordplay, and sound** — Hebrew acrostics (Psalm 119, Lamentations 1–4), puns (Amos 8:2: *qayits*, "summer fruit" / *qets*, "end"), and alliteration are nearly untranslatable; translators choose between notes and creative English equivalents.

### §6.5 Translation theory in one table

| Approach | Key figures | Core idea |
| --- | --- | --- |
| **Formal equivalence** | Tradition from Jerome's claim that in Scripture "even the word order is a mystery" | Preserve source-language words, structures, and ambiguities as far as the target language allows |
| **Dynamic / functional equivalence** | **Eugene Nida**, *Toward a Science of Translating* (1964); Nida & Taber, *The Theory and Practice of Translation* (1969) | The receptor should respond to the translation as the original receptors did; translate meaning, not form |
| **Optimal equivalence** | HCSB/CSB's marketing term, NIV's practice | Formal where possible, functional where necessary |
| **Skopos theory** | Hans Vermeer (1978), Katharina Reiss, Christiane Nord | A translation's purpose (skopos) determines method; Nord adds "loyalty" to the source and its community |
| **Relevance theory** | Ernst-August Gutt, *Translation and Relevance* (1991) | Communication depends on shared context; translators must decide how much implicit information to make explicit — a key issue for minority-language work |
| **Foreignizing vs domesticating** | Friedrich Schleiermacher (1813 lecture); Lawrence Venuti (1995) | Move the reader toward the author (foreignizing: Buber-Rosenzweig, Everett Fox) or the author toward the reader (domesticating: Luther, NLT) |
| **Literary translation** | Robert Alter; Robert Lowth's heirs | Preserve the literary artistry (repetition, leitwörter, terseness) that functional translations flatten |

## §7 Minority-language field translation: how it actually works in 2026

### §7.1 The scale of the task **\[as of 2026\]**

- Wycliffe Global Alliance's 2025 figures (based on ProgressBible data as of August 1, 2025) counted 7,396 living languages, of which **544 still needed translation to begin**, with translation active in about **3,526 languages across 173 countries**.
- More recent Wycliffe New Zealand statistics, marked as updated August 2026, count **805 languages with a full Bible**, **1,842 with only a New Testament**, and **1,520 with only portions**, out of 7,393 known living languages — with 3,229 languages having no known Scripture (many of which are not expected to request it).
  - **\[Pack note: these four figures do not agree with the total beside them. The three
    Scripture categories as printed sum to 4,167 (805 + 1,842 + 1,520); adding the 3,229 gives
    7,396 — the Wycliffe Global Alliance total in the bullet above — not the 7,393 this bullet
    states. The source does not say which figure differs; all are carried exactly as printed,
    and its own caution below — treat all such numbers as approximate — applies.\]**
- Wycliffe USA reports that by the end of 2025 only 541 language communities still needed translation to begin.

(Counts differ between reports by a few languages because of different census dates and definitions. Treat all such numbers as approximate.)

### §7.2 Who does the translating

The model has shifted dramatically since the 1970s. The old image — a Western missionary couple living for decades with a tribe — has largely given way to **mother-tongue translators** (native speakers, often with seminary or linguistic training), supported by **exegetical advisers** and **translation consultants**, with Western organizations playing a supporting role. Many projects run as **clusters** of related languages sharing training and resources.

### §7.3 The stages (a synthesis of published project plans)

A widely used sequence — reflected in the Bible Translation and Literacy (Kenya) process description and in the Paratext project-plan templates (e.g., SIL Compact Plan, Pioneer Bible Translators Base Plan):

1. **Exegesis and preparation.** Study the passage with source texts, translation handbooks (UBS Handbooks, SIL Exegetical Summaries), and key-term lists.
2. **Drafting.** Mother-tongue translators produce a first draft, often orally first.
3. **Team check.** The team reviews for accuracy, clarity, and naturalness.
4. **Preliminary / comprehension testing.** Read the draft aloud to fresh listeners and ask retelling and specific questions (who did what, what does this metaphor mean, what did you infer?). This catches failures that experts never notice.
5. **Back translation.** Someone renders the draft literally into a language the consultant knows (e.g., English, French, Swahili) so the consultant can check meaning without knowing the target language.
6. **Consultant check.** A trained translation consultant reviews the text (via the back translation) with the team, mostly for **accuracy of meaning**; notes are logged directly in the software, and the consultant resolves them once satisfied.
7. **Community review.** Speakers from the community — pastors, teachers, elders — review for naturalness and acceptability (not accuracy).
8. **Final checks and publication.** Automated consistency checks (verse numbering, punctuation, names, key terms), typesetting, audio recording, digital publication (YouVersion, Scripture App Builder), print.

### §7.4 The software stack

- **Paratext** (United Bible Societies and SIL): the industry standard. It displays source texts, commentaries, and handbooks side by side, manages key terms, runs checking tools (missing verses, punctuation, quotation marks, cross-references), and supports project plans and consultant notes.
- **Scripture Forge** (SIL): a web front end for collaborative work and community checking, integrated with Paratext.
- **AI drafting \[as of 2026\]:** SIL's open-source **Serval** machine-translation engine, surfaced through Scripture Forge, generates first drafts — a tools review in August 2026 described it as in use in nearly 500 projects. AI is also used for quality assessment, flagging likely problems for consultants. The consensus in the field is that AI accelerates drafting and checking but does **not** replace comprehension testing, consultants, or community review — and that it raises real questions about ownership, quality, and whether communities feel the translation is theirs. **\[contested — fast-moving\]**
- **Oral Bible translation (OBT)** and **sign-language translation** are growing sectors: many communities are primarily oral, and deaf communities need visual-language Bibles produced in video.

### §7.5 What minority-language translation teaches about translation in general

Field translation exposes assumptions hidden in English: a language with no word for "snow" (Isaiah 1:18), cultures where sheep are unknown, languages that must grammatically mark whether "we" includes the listener, honorific systems that force decisions about how disciples address Jesus, and kinship systems that make "brother" ambiguous. Every one of these forces an explicit decision that English translation lets you leave implicit.

## Where to go next (pack navigation, not source text)

- **Why the base texts differ and how variants are weighed** — §8–§13 → `bible-textual-criticism`.
- **Named translations and their positions on the spectrum** — §4.6, §5.5–§5.6 → `bible-latin-german-and-english`.
- **A translation decision traced end to end** — §32 (Isaiah 7:14) and §33 (Deuteronomy 32:8) → `bible-three-verses-through-the-pipeline`.
- **Translation reading list**, including the NET Bible's translators' notes — §35.3 → `bible-reference`; the role of AI in field translation is open question 9 in §38.