V
The Platform That Makes It Possible
Paratext: The Sherman Tank
of Bible Translation
Every revolutionary weapon system in history has depended on a platform — a dependable, interoperable, massively deployable foundation upon which specialized capabilities could be mounted, combined, and coordinated. In the Second World War, that platform was the M4 Sherman tank. It was not the most heavily armored vehicle on the battlefield. The German Tiger outclassed it in any one-on-one engagement. But the Sherman won the war for a different reason: it could be built by the thousands, shipped anywhere, maintained in the field by ordinary mechanics, and — crucially — it could carry attachments. It was the platform everything else mounted on.
In the battle to bring Scripture to every language on earth, that platform is Paratext.
Developed jointly by SIL International and the United Bible Societies and now used by virtually every major Bible translation organization worldwide, Paratext presents itself modestly as a word processor for translators. This is the equivalent of describing the Sherman as "a vehicle with a gun." What Paratext actually is — under its editor surface — is one of the most sophisticated linguistic, textual, collaborative, and computational environments ever assembled for the explicit purpose of putting the Word of God into human language.
Why the Sherman, Not the Tiger
The Tiger tank was more powerful in isolated combat. But it required specialized parts, broke down frequently, and could not be produced in sufficient numbers to be everywhere at once. The Sherman was standardized, interoperable, maintainable, and omnipresent. Paratext is the Sherman: not the most glamorous tool in any single dimension, but the platform already deployed in thousands of translation projects across every continent, already trusted by every major translation organization, and already structured to receive new capabilities as they arrive. The AI revolution did not have to build a new vehicle. It mounted its weapons on the Sherman.
What Paratext actually contains
To grasp why Paratext matters so profoundly, one must look beneath the visible editor to the infrastructure it has quietly assembled over decades. It is not a document; it is a living, interconnected graph of linguistic knowledge:
The hull — visible editor
The translation workspace where mother-tongue translators draft, edit, and review. What the translator sees. Beneath this surface lies everything else.
Critically structured Hebrew, Greek, and Septuagint texts with full morphological tagging — lemma, parsing, tense, voice, mood, person, number — accessible with a single click on any word in the source text.
Hebrew and Greek lexicons woven directly into the text. Every word links to its dictionary form, usage examples, and semantic range. Project glossaries track how the team has rendered each term — so that chesed rendered "lovingkindness" in Genesis remains so in Isaiah.
A theological terminology management system tracking how key terms — God, Lord, Messiah, Spirit, Covenant, Priest, Temple, Atonement — are rendered throughout the entire project. A doctrinal guardrail built into the infrastructure of translation itself.
Every previously translated passage retained and cross-referenced. When a phrase appears again — in a different book, years later — Paratext surfaces how the team rendered it before, maintaining consistency across a translation spanning decades of collaborative work.
Paratext aligns source-language words to target-language words, building a machine-readable mapping of how each concept in Hebrew or Greek is rendered in the vernacular. Over thousands of verses, this becomes an enormous bilingual database — and the raw material that AI translation models train on.
Hundreds of automated linguistic checks: spelling, punctuation, pronoun antecedents, participant tracking, name consistency, verse structure. These run continuously, catching errors that human review alone would miss across hundreds of chapters.
A parallel workspace where the vernacular draft is rendered back into a major consultant language — with structural relationships maintained between source, translation, and back translation — enabling consultants to evaluate faithfulness without speaking the target tongue.
The deepest structural layer: every chapter, verse, poetic line, footnote, cross-reference, heading, and character style encoded in Unified Standard Format Markers — a machine-readable structure that makes the entire translation usable by publishing systems, apps, audio pipelines, and AI training datasets.
Because the text is structured in USFM, Paratext connects directly to print Bible production, digital Scripture platforms, audio recording workflows, mobile apps, and web distribution — a complete path from first draft to finished Scripture product in the hands of readers.
Taken together, this is not a word processor. It is one of the largest and most carefully annotated multilingual parallel corpora ever assembled — a living archive of how human languages render the Word of God. Every translation project that has ever run through Paratext has contributed to this corpus, enriching the linguistic intelligence available to every project that follows.
7,000+
Human languages — the scope of the unfinished task Paratext is structured to address
Decades
Of accumulated multilingual alignments, terminology data, and translation memories built into the platform
Every major org
SIL, Wycliffe, UBS, illumiNations — all working on the same platform toward the same 2033 horizon
Hobart's Funnies: the specialized weapons the Sherman now carries
In June 1944, when Allied forces landed on the beaches of Normandy, they faced obstacles that standard tank formations could not overcome: beach obstacles, minefields, flooded terrain, fortified walls. General Percy Hobart's solution was inspired: take the dependable Sherman platform and mount specialized attachments — flail chains to detonate mines, folding bridges to cross ditches, flame projectors, amphibious screens, earth-moving blades. These became known as Hobart's Funnies. They looked strange. Some soldiers laughed at them on the parade ground. But on D-Day they were the difference between breakthrough and catastrophe.
The American commanders who declined to deploy Hobart's Funnies on Omaha Beach suffered devastating casualties. The British and Canadian forces who used them on Gold, Juno, and Sword broke through. The platform was the same Sherman. The funnies were what turned it from a combat vehicle into a beachhead-breaker.
The AI revolution has given Paratext its funnies. The Sherman was already in the field. The new attachments transform it:
Machine learning — the engine upgrade
Machine learning does not replace Paratext's existing linguistic intelligence — it draws on it. The decades of word alignments, translation memories, and morphological data that Paratext has accumulated become the training corpus for AI models. The Sherman's accumulated mileage becomes fuel for a new engine.
Scripture Forge — the flail tank
Like the flail tank that beat a path through minefields so infantry could follow, Scripture Forge's AI drafting clears the most difficult opening obstacle: the blank page in a low-resource language. It generates Draft 0 so translators can evaluate and refine rather than originate from nothing. It mounts directly on Paratext.
Community checking — the bridge layer
Hobart's bridge-layer tanks extended the Sherman's reach across obstacles that stopped it. Community checking extends the translator's reach into the actual language community — village elders, oral learners — who review drafts by audio on a mobile device. The bridge connects the professional team to the people the translation is for.
AI back translation — the ARK carrier
The Armoured Ramp Carrier allowed vehicles to scale sea walls they could not breach alone. AI-generated back translation allows the consultant to do their work far faster — reviewing more projects, approving more books, advancing the whole force toward completion.
LLM terminology checks — the mine detector
Hidden inconsistencies in theological terminology are the landmines of translation work — invisible until a community reading their Bible stumbles on a key term rendered three different ways across three books. LLM-powered consistency checking detonates these mines before the text reaches the reader.
Oral AI tools — the Crocodile
The most fortified obstacle in global Bible translation is the oral community with no written tradition. Speech-to-speech AI, mounted on Paratext's USFM audio pipeline, attacks this position directly: bringing the Word to those for whom reading was never the primary channel.
The Crucial Strategic Lesson of Hobart's Funnies
The commanders who suffered most on D-Day were not those who lacked the Sherman tank — they had it. They were those who declined the specialized attachments because the attachments looked unfamiliar, experimental, even absurd. The tank alone was necessary but not sufficient. The funnies were what converted a landing into a breakthrough. For Bible translation organizations in the AI era, Paratext alone — as powerful as it is — is the Sherman without its funnies. The machine learning, the Scripture Forge drafting, the community audio checking, the LLM consistency tools: these are not exotic experiments. They are available now. The beach is the same. The obstacle is the same. The question is only whether the funnies will be deployed.
William Tyndale died before his translation work was complete, but the English Bible that followed was built on what he had done. The translators who spent decades painstakingly entering data into Paratext — checking terms, aligning words, writing back translations — may not have known they were also building the training data for the AI revolution in Bible translation. But they were. And the harvest of their faithfulness is now available to every language community still waiting for the Word.
"One soweth, and another reapeth."
John 4:37 — The Paratext generation sowed. The AI generation is beginning to reap — and to sow for those who come after.