A close language, not a new source draft

Related language Bible translation — keep the knowledge base in Adapt It.

Related language Bible translation adapts a finished translation into a close language, instead of drafting every verse from Greek or Hebrew. Adapt It does that on the desktop with a knowledge base of word and phrase adaptations. Aquilla does not run Adapt It, and Living Memory is not that knowledge base.

The direct answer

It is translation between languages that already share a lot of words and grammar, starting from a finished text rather than from the Hebrew or Greek alone. Adapt It is the open-source editor for that job. FLExTrans is SIL’s rule-based path from FieldWorks data. Aquilla does not do either one. Export USFM and keep the adaptation in the tool that stores it.

People searching for related language Bible translation usually already have a translation in a language their translators understand. The question is whether the next language can reuse those decisions, word by word and phrase by phrase, without pretending the languages are the same.

Adapt It’s own description is a knowledge base of previously entered adaptations, inserted into the target as the translator works, with USFM in and USFM out. Its administrator help describes exchanging those files with Paratext or Bibledit. SIL’s software catalog lists Adapt It for adaptation, and lists Scripture Forge separately for AI-enabled related-language adaptation suggestions. This page does not repeat their menus.

What the search is actually choosing

Searchers want a knowledge base, transfer rules, or adaptation suggestions from a related language. Aquilla covers an authorized draft and an export. It does not cover the adaptation.

JobAquillaTypical result for this search
Adapt a finished translation into a closely related languageNo — Aquilla does not run an adaptation editor.Yes — Adapt It is built for translation between related languages
A knowledge base that inserts earlier word and phrase adaptationsNo — Living Memory is not Adapt It’s knowledge base.Yes — Adapt It stores adaptations the translator has entered
Rule-based transfer from FieldWorks lexical dataNo — Aquilla does not read a FieldWorks lexicon or apply transfer rules.Yes — SIL describes FLExTrans this way, including a language cluster
AI suggestions that adapt from a related language into ParatextNo — Aquilla does not sync with Paratext.SIL’s catalog lists Scripture Forge for related-language adaptation suggestions
A desktop install that exchanges USFM with Paratext or BibleditNo — no desktop installer, and no automatic exchange.Yes — Adapt It is a desktop program and its administrator help describes that exchange
A person authorizes a draft in the browser, then exports USFM or USXYes — the workspace, Living Memory, and export.The adaptation itself stays in Adapt It or FLExTrans

Common questions

What is related language Bible translation?

It is adapting a finished translation into a language that is close to it, instead of drafting every sentence from Greek or Hebrew. Adapt It is the desktop editor built for that. It stores word and phrase adaptations in a knowledge base and can insert them as the translator works. Aquilla does not run that editor.

Does Aquilla replace Adapt It?

No. Adapt It is a free, open-source desktop program for Windows, macOS, and Linux. It expects USFM, keeps a knowledge base of adaptations the translator has entered, and its administrator help describes exchanging Scripture files with Paratext or Bibledit. Aquilla does not store that knowledge base, does not install on the desktop, and does not sync a project into Paratext. Export USFM or USX when the adaptation still belongs in Adapt It.

Is a knowledge base the same as translation memory?

No. Translation memory for Bible translation, on its own page, is consistency of renderings the team has already authorized inside one Scripture project. Adapt It’s knowledge base is earlier word and phrase adaptations from a source language into a related target. Living Memory is the first job. It is not Adapt It’s knowledge base, and it is not a TMX file.

What about FLExTrans or Scripture Forge?

SIL describes FLExTrans as rule-based translation between related languages, using FieldWorks lexical data and Apertium transfer rules, including a language cluster. SIL’s software catalog also lists Scripture Forge for AI-enabled related-language adaptation suggestions. Aquilla does not run transfer rules, does not read a FieldWorks lexicon, and does not make those suggestions. How a model is prompted or fine-tuned is the low-resource page, not this one.

Can a prompted draft adapt a related language?

A prompted draft is not an adaptation engine. Aquilla drafts in the browser from project context and keeps decisions you authorize in Living Memory. It does not insert Adapt It’s previous word adaptations, and it does not apply FLExTrans rules. If the team’s method is adaptation between related languages, keep Adapt It or FLExTrans.

How much does this cost in Aquilla?

Anyone can start on the Free plan with a weekly allowance of AI assistance. Bible-translation teams and ETEN affiliates get team-plan access at no cost — contact us to activate your organization’s workspace.

Related topics

Draft in the browser. Adapt related languages in Adapt It.

Start on the Free plan. Bible-translation teams and ETEN affiliates can contact us to activate team-plan access. Keep Adapt It when the job is a knowledge base of adaptations.