Assemblies of God AFI Applied Linguistics Institute
Before the landing: the briefing. Read why we fight, then hit the beach. Skip to the course

An exhibit of Artists for Israel International

Two Battle Plans Normandy, June 1944 & Every Tongue, 2033

“For we wrestle not against flesh and blood, but against principalities, against powers, against the rulers of the darkness of this world, against spiritual wickedness in high places.” Ephesians 6:12

Operation Overlord

The Supreme Headquarters plan for the liberation of Europe

What the plan was called

The whole campaign to break into Nazi-occupied France was code-named Operation Overlord. Its opening assault — the Channel crossing, the airborne drops, and the landings themselves — was Operation Neptune. The day the assault began was D-Day, Tuesday, 6 June 1944. Wrapped around both was a deception plan, Operation Fortitude (part of a larger scheme called Bodyguard), designed to convince Hitler that the real blow would fall at the Pas-de-Calais, not Normandy.

Who wrote it

The plan was written before its commander existed. In the spring of 1943, with no Supreme Commander yet appointed, British Lieutenant General Frederick E. Morgan was named Chief of Staff to the Supreme Allied Commander (designate) — COSSAC. Working from a single borrowed room in Norfolk House, St James’s Square, London, his combined British–American staff produced the Outline Overlord Plan, completed on 27 July 1943. It chose Normandy over the obvious Pas-de-Calais, set a target date of 1 May 1944, and — because the Combined Chiefs would give him so little — used only three assault divisions.

When General Dwight D. Eisenhower was named Supreme Commander in December 1943, COSSAC was folded into his new headquarters, SHAEF (Supreme Headquarters Allied Expeditionary Force). His ground commander, General Bernard Montgomery, judged Morgan’s front too narrow and widened it from three beaches to five, with three airborne divisions on the flanks. Eisenhower backed him, and the date slipped to June to find the extra landing craft. The naval plan, Neptune, was drafted under Admiral Sir Bertram Ramsay; the air plan under Air Chief Marshal Sir Trafford Leigh-Mallory, with Air Chief Marshal Sir Arthur Tedder as Eisenhower’s deputy and Lt. Gen. Walter Bedell Smith as chief of staff. Morgan stayed on as Bedell Smith’s deputy.

So the answer to “who wrote the plan” is: Morgan drafted it, Montgomery and the service commanders reshaped it, and Eisenhower owned it — and, as he wrote privately, took the blame for it if it failed.

What it looked like

On paper, Overlord was a library: Morgan’s outline digest, then the Neptune naval orders running to well over a thousand pages, with annexes for every beach, convoy lane, minesweeping channel and tide table. In the room, it was a map. On 15 May 1944, at St Paul’s School — Montgomery’s 21st Army Group headquarters and his own old school — Eisenhower held the final review before King George VI, Winston Churchill and the assembled commanders. On the floor lay an enormous painted map of the Normandy coast, and the generals walked across it as they briefed, unit by unit, beach by beach.

Schematic of the Overlord assault, 6 June 1944 The English Channel lies to the north. From west to east the five beaches are Utah and Omaha (American), Gold and Sword (British), and Juno (Canadian) between them. American airborne divisions dropped behind Utah; the British 6th Airborne dropped east of the Orne River near Caen. Cherbourg Cotentin Carentan Bayeux Caen Orne UTAH OMAHA GOLD JUNO SWORD from the English Channel — Neptune convoys US 82nd & 101st Airborne British 6th Airborne American sectors British & Canadian sectors airborne drop zones
The plan as the commanders saw it on the floor at St Paul’s School: five beaches, two airborne flanks, and the sea behind them. Schematic, not to scale.

What the plan entailed

  1. Deceive the enemy. Fortitude invented a phantom army in southeast England under General Patton, with dummy tanks, fake radio traffic and double agents, so that German armour waited at Calais for weeks after D-Day.
  2. Isolate the battlefield. The air forces’ Transportation Plan smashed the railways and bridges of northern France so reinforcements could not reach Normandy quickly.
  3. Seize the flanks by night. Three airborne divisions dropped in the early hours of 6 June to hold bridges, causeways and crossings on either end of the landings.
  4. Cross and bombard. Neptune’s armada swept the mines, then battleships and cruisers shelled the coastal defences at dawn.
  5. Land and hold a lodgement. At H-Hour, infantry and armour went ashore on Utah, Omaha, Gold, Juno and Sword to link up into one continuous beachhead.
  6. Supply the breakout. Two prefabricated Mulberry harbours were towed across the Channel and fuel was pumped under the sea, so the army could grow faster than the enemy could gather against it — and then break out toward Paris, the Rhine and Berlin.

How it was put together

Overlord was assembled the way a cathedral is: by many hands under one design. The strategy came down from Roosevelt, Churchill and the Combined Chiefs of Staff through a chain of conferences — Casablanca (January 1943), Washington (May 1943), Quebec (August 1943) and Tehran (November 1943). The intelligence came up from below: Ultra decrypts of German signals, French Resistance reports, beach-gradient surveys by commandos who swam ashore at night to collect sand samples, and millions of holiday snapshots and postcards of the French coast sent in by the British public after a BBC appeal. Planners counted tides, moonlight and landing craft; meteorologist Group Captain James Stagg watched the weather. When Stagg forecast a brief break in a Channel storm, Eisenhower — on the morning of 5 June — gave the word to go.

SUPREME HEADQUARTERS
ALLIED EXPEDITIONARY FORCE

Soldiers, Sailors and Airmen of the Allied Expeditionary Force!

You are about to embark upon the Great Crusade, toward which we have striven these many months. The eyes of the world are upon you. The hopes and prayers of liberty-loving people everywhere march with you.

[…]

Good luck! And let us all beseech the blessing of Almighty G-d upon this great and noble undertaking.

— Dwight D. Eisenhower

Our landings in the Cherbourg-Havre area have failed to gain a satisfactory foothold and I have withdrawn the troops. My decision to attack at this time and place was based upon the best information available. The troops, the air and the Navy did all that bravery and devotion to duty could do. If any blame or fault attaches to the attempt it is mine alone.

— pencilled by Eisenhower before the invasion, and kept in his wallet

Both documents are public-domain records of the U.S. government; the originals are held by the National Archives and the Eisenhower Presidential Library.

From the beaches to the nations

7,000
ships of the Neptune armada crossed one narrow sea
7,000
living languages of mankind wait for a landing of the Word

Eleven months after Normandy, on 12 April 1945, Eisenhower walked through the camp at Ohrdruf and ordered that everything be photographed and recorded, so that no one could ever say it had not happened. Overlord opened the gates of the camps and freed a continent in the flesh. This exhibit points past that liberation to a greater one: the freeing of every soul still held captive in darkness, by the Word of Hashem placed in their own heart language.

“The Ruach of Adonoi Hashem is upon me… to proclaim liberty to the captives, and the opening of the prison to them that are bound.” — Isaiah 61:1

The All Access Goals

Every Tribe Every Nation’s battle plan for the year 2033

What the plan is called

The alliance is Every Tribe Every Nation (ETEN), its name taken from the multitude of Revelation 7:9. Its battle plan is the All Access Goals, set for 2033. Beyond 2033 lies the long-range objective ETEN calls Every Verse Current: the whole Bible, kept accurate and up to date, in every language people understand best. Its sister movement, illumiNations, is the public face that raises prayer and funding; ETEN describes itself as the operating engine and illumiNations as the advancement engine.

Why 2033? ETEN’s own pages give the answer two ways — 2,000 years since Shavuot (Pentecost), when the Besuras HaGeulah first went out in many tongues, and 2,000 years since the resurrection of Moshiach and the giving of the Great Commission. Either way, the date is a faith goal, not a calculation.

Who wrote it

As with Overlord, no single hand wrote it. The vision was first cast in 2010 by Oklahoma City businessman Mart Green of Hobby Lobby, who asked what it would take for every nation to have G-d’s Word by 2033. That year the major Bible agencies and a circle of Christian philanthropists agreed to stop working in separate silos and pool their data, plans and money. The alliance went public in 2012, with American Bible Society, Biblica and Wycliffe USA announcing it alongside the Digital Bible Library.

Today the plan is governed by a Steering Committee of the chief executives of the implementing agencies plus five core resourcing partners, chaired by Gary Nelson of the Nelson Family Foundation, with Mart Green, the Maclellan Foundation and others at the table. The implementing partners are:

  • American Bible Society
  • Biblica
  • Deaf Bible Society
  • Lutheran Bible Translators
  • Pioneer Bible Translators
  • Seed Company
  • SIL Global
  • The Word for the World
  • unfoldingWord
  • United Bible Societies
  • Wycliffe Bible Translators USA

Two “affinity tables” fight on specialized fronts: the 55 Table for sign-language translation, and the Oral Bible Translation Table (including Faith Comes By Hearing, Spoken Worldwide and YWAM) for communities that hear rather than read.

What it looks like

Where Overlord had a floor map of five beaches, the All Access Goals are drawn as four objectives across the whole human population, tracked language by language on ETEN’s public data dashboard.

95%

of the world’s population with access to a full Bible

99.96%

with access to a Brit Chadasha (New Testament)

100%

with access to at least some portion of Scripture

100

most strategic written languages with two viable translations

What the plan entails

  1. One shared picture of the battlefield. Partners pool their data on every language — who is working where, what is finished, what has not been started — so no language is skipped and none is fought over twice.
  2. A common framework. ETEN works on the “Collective Impact” model: shared goals, coordinated strategy, and a backbone staff, put in place in 2018, that keeps the alliance aligned.
  3. New weapons. An Innovation Lab, formed in 2021, tests and scales faster methods: AI-assisted drafting and checking, better shared software, and oral and sign-language translation.
  4. The local church on the front line. Translation is shifting from something done for a community, to something done with it, to something done by it.
  5. Supply lines. illumiNations mobilizes prayer and giving so that funding, not willingness, is never the reason a language waits.
ETEN’s own comparison of typical translation timelines
ProductWhen the 2033 vision was castToday
Full Bible15–25 years7–15 years
New Testament7–10 years3–7 years
Portions3–5 years1–2 years

How it was put together

Like COSSAC’s staff in Norfolk House, ETEN began by admitting the plan could not succeed on the resources then in hand. When the alliance formed, projections showed a gap of some 75 years between the 2033 vision and the likely reality; one estimate had the last language not even starting translation until 2150. The partners agreed on measurable goals, sized by people group, and handed the counting to a common data service, ProgressBible, which reconstructed the record back to 1988 and forecast the road to 2033. From that baseline they set priorities, shared tools, and kept revising — just as Montgomery widened Morgan’s three beaches to five once he saw the ground. The alliance describes the date itself as an act of faith: a goal that looked unreasonable on paper and was adopted anyway.

ORDER OF THE DAY
FROM THE SUPREME COMMANDER

All authority in Shomayim and on ha'aretz has been given to me. Go therefore and make talmidim of all nations, giving them a tevilah in the Name of the Av and of the Ben and of the Ruach Hakodesh, teaching them to keep all that I have commanded you.

And I am with you all the days, until the end of the age.

— Moshiach Yeshua (Matthew 28:18–20, paraphrased in the OJB register)

One war, two fronts

Reading Overlord as a parable of the spiritual battle

In 1946 the Swiss theologian Oscar Cullmann reached for this same picture in Christ and Time. The decisive battle of a war, he wrote, can be fought and won long before the war is over; after D-Day, victory was certain, though the fighting went on until V-E Day. So it is with the death and resurrection of Moshiach. The enemy’s defeat was settled at Golgotha and the empty tomb. What remains is the long advance inland — and the Word of G-d in every tongue is how the ground is taken.

Each element of the 1944 plan, and its counterpart in the campaign for the nations
Overlord, 1944The Great Commission, to 2033
General Eisenhower, Supreme Commander, Allied Expeditionary ForceMoshiach Yeshua, Sar Tzva Hashem, “captain of the host of Hashem”Joshua 5:14; Matthew 28:18
The plan drawn by COSSAC before the commander was namedThe plan of redemption, drawn before the foundation of the worldEphesians 1:4; Revelation 13:8
The Order of the Day, read to every soldier before embarkingThe Great Commission, given to every talmidMatthew 28:19–20
D-Day, 6 June 1944: the decisive blowThe resurrection, and the Shavuot when the Ruach Hakodesh came and the Good News went out in many tonguesActs 2:1–11
Operation Fortitude: deceiving the enemyThe enemy’s deception, which the Word unmasks: “the god of this world hath blinded the minds of them which believe not”2 Corinthians 4:4
Nearly 7,000 vessels crossing one seaSome 7,000 languages, each a shore still to be reached
The beachhead: a first foothold on occupied groundThe first portion of Scripture in a heart language
The Mulberry harbours and fuel lines that fed the advanceBible societies, digital libraries, audio and video Scripture, and the prayers and gifts that sustain them
The breakout from Normandy across EuropeThe New Testament, then the whole Bible: from portion to Brit Chadasha to the full Word of G-d
The weather window that Stagg foresawThe fullness of time, appointed by HashemGalatians 4:4
The gates of the camps opened, 1945Liberty proclaimed to the captivesIsaiah 61:1; Luke 4:18
V-E Day, 8 May 1945“A great multitude… of all nations, and kindreds, and people, and tongues, stood before the throne, and before the Lamb”Revelation 7:9
“For the weapons of our warfare are not carnal, but mighty through G-d to the pulling down of strong holds.”
2 Corinthians 10:4

Why this is a spiritual battle

Overlord was fought against an enemy you could see: concrete bunkers, panzer divisions, a regime that built death camps. The campaign for the nations is fought against an enemy you cannot see — the powers named in Ephesians 6 — and its weapon is “the sword of the Ruach, which is the word of G-d” (Ephesians 6:17). A person without Scripture in a language he understands is like a town behind the Atlantic Wall: the liberating army exists, the victory has been won, but the news has not yet reached him. Every translation is a landing. Every heart language reached is ground taken from the prince of this world.

At Babel, Hashem scattered the languages in judgment (Genesis 11). At Shavuot He began to gather them in mercy, every man hearing in his own tongue (Acts 2:6). The All Access Goals are one generation’s attempt to finish what that day began. AFII stands in that line: the Orthodox Jewish Bible, the Yiddish Triglot, and our work toward all 7,000 of the world’s languages are our sector of the beach.

“And this gospel of the kingdom shall be preached in all the world for a witness unto all nations; and then shall the end come.” — Matthew 24:14

For further study

Every Tribe Every Nation
Operation Overlord
  • Stephen C. Kepher, COSSAC: Lt. Gen. Sir Frederick Morgan and the Genesis of Operation Overlord (Naval Institute Press, 2020)
  • Frederick Morgan, Overture to Overlord (1950)
  • Forrest C. Pogue, The Supreme Command (U.S. Army in World War II series)
  • Gordon A. Harrison, Cross-Channel Attack (U.S. Army in World War II series)
  • Dwight D. Eisenhower, Crusade in Europe (1948)
  • National Archives: Eisenhower’s D-Day statement to soldiers
Theology
  • Oscar Cullmann, Christ and Time (1946; English trans. 1950) — the D-Day / V-Day analogy
  • The Orthodox Jewish Bible, Artists for Israel International

ἐπαγωνίζεσθαι

epagōnizesthai — “to contend earnestly for the faith once delivered to the kedoshim” (Yehuda 3)

Your Order of the Day

Yehuda wrote his letter as a summons to battle. The verb he chose in verse 3 is built on agōn, the struggle of the arena and the field, and it appears nowhere else in the Brit Chadasha. Eisenhower’s soldiers trained for months before they ever saw the sand. So will you.

This is your beach: twenty-five verses, four hundred sixty-one words of Koine Greek, and the same Paratext and PTXprint tools the translation agencies use. Every word you master here is a round chambered for the 7,000 languages still waiting for a landing of the Word.

Hit the beach
The Dean’s Chair · A/G AFI Applied Linguistics Institute
ΙΟΥΔΑ
יְהוּדָה
Yehuda · ΙΟΥΔΑ

The Yehuda Course — The Greek of Jude, Word by Word

The best way to lovingly confront Lubavitchers is with the truth. Twenty-five verses. Four hundred sixty-one words. A short letter carrying a long warning — taken apart, word by word, in the Jewish Greek that witnesses to the Resurrection Empty Tomb of the Brit Chadasha kehillah.

For this course, Yehuda ben Yosef ben Dovid — Jude, a man with royal Davidic blood, also a brother of the Jerusalem leader the Shaliach Ya’akov as well as an eved of Yeshua HaMoshiach — stands as dean: every page below is spent inside his own sentences, learning Koine Greek the way he actually wrote it.

461Greek Words
25Verses
187Study Pages

ΙΟΥΔΑ · The Full Text, Kept Open For Reference (see link verse 7)

For the fuller treatment of these 461 words — parsed, transliterated, and explained one by one — see all 187 pages of the course below.

Open the interactive course
הספרThe Course, Page by Page

A 187-Page Word-by-Word Study

Pages 1–6 hold the whole text and its numbering; the word-by-word study itself opens on page 7. Turn the pages below, or download the source PDF.

Course page 7
Page of 187

Open the source PDF

Go to the School Library

Reversing the World's Babel of 7000 Languages

Learn to Be a Linguistics Prospector

Understand finishing Martyr Jim Elliott's Work

Volunteer to Finish Martyr Jim Elliott's work

Technology has brought a sea change to the Great Commission: the goal of giving every language group in the world access to the whole Bible, long out of reach, is now within practical view.

Frontier of Machine Learning Using Rich-Resourced Languages to Generate Native-Speaker-Reviewed Drafts for their Poor-Resourced Language Cousins.

חברות נוספותAlso At the Yeshiva

The Rest of the Curriculum

The Yehuda course sits at the center of the school this term. The rest of the AFI Institute program remains fully open below.

Reason for the Existence of the School

Need for thorough but rapid training of Bible translators and exegetes.

Hebrew Course

Foundations of Biblical Hebrew for reading the Tanakh in its own language.

Introduction to the Tanakh

A survey course through the Hebrew Scriptures.

Introduction to the Brit Chadasha

A survey course through the New Covenant writings.

Arts & Cross-Cultural Communication

Also consult the music and drama sections of the site.

Scripture Translation

Also consult the Critique of the Elicitation-based Bible Translation Model and UBS Dictionary of Biblical Hebrew and Greek and Web Image Collection. Also Jude in French and Jude in Ladino and Jude in Spanish and Jude in Russian and Jude in Hebrew and Jude in Yiddish and Jude in Urdu and Jude in Pashto and Jude in Bahasa (Indonesian) and Jude in Farsi and Jude in Bengali and Jude in Arabic and Jude in a Muslim-friendly English Translation.

Downloads

פרוטפרקסטTools For Translators

GETTING STARTED WITH PARATEXT TRANSLATION SOFTWARE AND PTXPRINT TYPESETTING AND DRAFT PRINTING

Paratext is quite accessible, and no formal academic credentials are required for a student to get started on their own.

Getting the software and a basic license

Anyone can register and install Paratext themselves. Paratext is completely free, and if you leave the organization field blank on your user registration, you immediately receive a code for the Basic Tier. That gives access to Bible study, research, or a personal translation project using any of the open-access resources — there is no check at this level.

If the student wants to do real Bible-translation work into an underserved language, 1) accessing a particular language community as to whether they can work with Scripture in a neighboring or trade language, or do they need their own, 2) estimating a language that's losing ground to a dominant language may get a different strategy (oral storying, a single Gospel) than a vital one getting a full NT, 3) visiting the places where the languages are spoken rather than working from secondhand data, 4) investigating phonology, morphology, syntax, and discourse structure — before or alongside translation itself, as documented in the classic Amele case study in Papua New Guinea. Therefore in registering for a license code you would need not the Basic Tier, but the Translator Tier, which requires declaring an organizational affiliation and contacting pgoble@gmail.com to get permission to use AFII as his or her declared organizational affiliation. These Translator Tier features — access to model Resource Texts in over 1,730 languages, project backup on the Paratext server, and team synchronization — are available when you select your organization during registration, or by registering a new organization. Since Artists for Israel International is already a recognized Bible translation/school organization, the student could simply select Artists for Israel International as his/her organization during registration and an AFII administrator could approve/sponsor him/her.

Getting started with Paratext

Getting Started for New Users — the full playlist page, in the exact sequence Paratext.org presents it:
🔗 https://paratext.org/videos/en/paratext-features-training-videos/new-user-videos/

The sequence on that page is:

Each of the above has its own thumbnail/video embedded directly on that page — clicking any thumbnail plays it in place.

Beyond this beginner set, Paratext also has a much larger structured curriculum needed next:

Full Paratext 9 Training series (deeper, feature-by-feature): https://paratext.org/videos/en/paratext-9/
Feature-Specific Videos (topic-by-topic reference, e.g. Drafting, Checking Tools, Biblical Terms): https://paratext.org/videos/en/paratext-features-video-training/
Written Training Manual: https://paratext.org/training-manual-en

the full Paratext 9 core training list — it's a large curriculum (70+ videos) that picks up right where "Getting Started" leaves off. Unlike the PTXprint series (which had a companion blog post with embedded direct links), this page's individual videos are loaded dynamically and don't expose separate clickable URLs per video — only the page itself is directly linkable.

Full series page: https://paratext.org/videos/en/paratext-9/

Sequence (grouped by topic, in the order presented):

Interface Basics
What is Paratext?

Why Change the Menus → How the Windows Work (Pt 1 & 2nd Part of the video Pt 2) → Quick Reference Window → Change User Interface Language → Basics of Projects/Resources → Finding Menu Items → Arranging Windows → Text Collections → Scroll Groups → Set Keyboard per Project → Swap Text in a Window → More Window Tips → Viewing Non-Biblical Texts → Navigate to a Reference → Find Help

Resources & Sharing
Download/Install Resources → What is Send & Receive → Receive a Project First Time → Keep Project in Sync → Avoiding Conflicts → Enhanced Resources Intro, Linking, short cut keys Found/Problem Terms, Biblical Terms List Setting, Searching)

Drafting Basics
My Tasks → Understanding USFMs → Standard View → Formatted View → Basic View → Unformatted View → Preview → Backslash Key Workaround → Adding Verse Numbers → Non-Biblical Text Markers → Show All Chapters → Zoom/Text Size → Required Paragraph Markers


How to Use Checking Tools → Marking Tasks Complete → Conflict Notes

Footnotes, Glossary, also inserting. and editing Illustrations
Insert/Edit glossary entries Characters Inventory → Book Introductions → Punctuation Inventory

Spell Check
Approve Spelling of Common Words → Spell Check Current Book → Common Typos Check → Wordlist Tool Features → Edit a Verse from Wordlist → Display Spelling Errors

Biblical Terms Introduction → Identify a Rendering → Edit/Delete a Rendering → Comparative Texts → Achieving Consistency → Custom Filters & Guess Renderings

Print Draft with PTXprint.

Notes
Insert Notes → Comment/Assign/Edit/Tag/Delete → Show Changes/Resolve → Notes List → Filter/Sort Notes → Search & Hashtags → Reattach Note

Back Translation
What Is It / What Makes a Good One → Prepare & Create Project → Draft & Mark Finished → Status Boxes → Ready for Consultant

Interlinearizer
How to Start → How to Use It

Basic Checks (deep dive)
References → Quotations → Quoted Text (Footnote Quotes) → Unmatched Punctuation → Numbers → Capitalization → Repeated Words → Exceptions

Collaboration
Paratext Lite → Optional checks

Reference Tools and also Chorus Hub
Book Name USFMs → Parallel Passages Filters

Getting Started Printing a Draft of the Beginnings of Your Translation

Intro
Introduction to PTXprint — overview of printing draft translations, why to run basic checks first.

The following are the basic checks: How to Use Checking Tools → Marking Tasks Complete → Conflict Notes

Footnotes, Glossary, also inserting. and editing Illustrations
Insert/Edit glossary entries Characters Inventory → Book Introductions → Punctuation Inventory

Spell Check
Approve Spelling of Common Words → Spell Check Current Book → Common Typos Check → Wordlist Tool Features → Edit a Verse from Wordlist → Display Spelling Errors

Biblical Terms

1 — Install your software PTXprint
How to Install PTXprint — exporting a draft translation in Paratext, installing PTXprint, and initial setup

2 — Make Initial PDF
Print an Initial Draft — using Project menu > Export Draft PDF (PTXprint) to generate your first PDF and additional copies from Paratext's settings and fonts

3 — Adjust Settings
Adjust Settings in PTXprint — customizing margins, adding custom footer text, using the search function to find settings

4 — Booklet Printing
Print a Booklet — producing a ready-to-print booklet layout with correctly ordered pages

5 — Reopen PDF to Reprint
Print or Share Additional Copies — locating a previously created PDF to print more copies or share via email/USB

6 — Check for Updates
— "How to Update PTXprint" on the same Paratext blog post, which just points you to the update icon inside PTXprint and the download page rather than a standalone video.

All six-plus-intro are also collected as a playlist here: PTXprint Video Series.

Work That May Need to Be Done When the Translation is Finished

Digital Bible Library (library.bible / DBL) is UBS's archiving-and-licensing platform for Scripture assets. It does three core jobs:

  • Metadata — every entry (text, audio, video, print, braille) needs a full metadata record before it can be uploaded. For text, this comes from the Global Bible Catalogue (GBC), which Paratext's uploader pulls from automatically; no text or audio product can be uploaded to DBL without an accompanying set of metadata, and archivists can add/edit it through GBC's web interface, or import it from an external XML file. Metadata includes things like completion percentage, translation history narrative, and promotional text for licensed partners.
  • Storage — text is stored as USX (the XML form of USFM), with metadata as a separate XML document, packaged as a text release bundle: a compressed zip file containing the text and metadata for a scripture translation project. The bundle also carries publication metadata, language, versification, and style references, and is the package that can actually be licensed out to partners.
  • Licensing — organizations contribute and maintain licensing documents that define the terms granted to publishers (Library Card Holders); these can be a locally-authored template or a reference to a third-party license like Creative Commons. Content can also be released for open access, meaning anyone can download it without a full per-recipient license agreement.

What Paratext work needs to get cataloged: Paratext, via the Paratext Registry, is the standard interface for uploading text content — configuration settings inside the Paratext project supply the metadata, and before upload Paratext validates that both text and metadata match DBL's required "text bundle" format. The Registry itself is where a project gets registered in the first place: it records the project name/short name, language, the managing organization and rights-holder, the visibility level (standard, confidential, or test/training), which books are being translated, and the users and their roles (administrators, translators, consultants, supporters). Newly registered projects go through an internal review period before that information becomes visible to other organizations. Practically: a project needs its GBC metadata record filled in (language, versification, book list, translation type/audience, etc.), correct Registry settings, and to pass Paratext's internal validation checks before the uploader will push it.

What PTXPrint work needs: PTXPrint isn't itself a DBL-uploading tool — it takes input either as Paratext USFM or as a DBL bundle to produce print-ready PDFs. So print/typeset output from PTXPrint isn't separately catalogued in DBL; DBL cataloging happens upstream (the USX text bundle), and PTXPrint just consumes that bundle to generate the publication layer.

Key reference links:

הארכיוןArchive

Proof of Moshiach in the Dead Sea Scrolls

Isaiah 53:11 Dead Sea Scrolls Isaiah Scroll - Proof of Moshiach's Resurrection (Techiyas HaMesim)

AFI Institute Diploma

Artists For Israel Institute Fellow diploma

A Fellow of Artists For Israel Institute and a Talmid Chochom of Yeshua HaMelech HaMoshiach — view full-size diploma (PDF)

Read Jude in Yiddish

Orthodox Yiddish Triglot Bible — Interlinear of Yiddish into Latin Script and English with the Orthodox Jewish Brit Chadasha

Begin reading Yehuda (Jude) in Yiddish — page 5019 of the Orthodox Yiddish Triglot Bible (PDF)

יָמָיו וּדְבָרָיו

Sha’ul had one Rebbe. So did Yehuda — and here, for these 187 pages, so do you.

afii.org