Log in

or use your email

Search the Library

Keyword search across Doctrine Analysis, Core Glossary, Comparative Theology, and Regional Analysis. Mention a language name for the best results — e.g. "remnant burmese" or "what glossary terms conflict for burmese."

Type at least 2 characters to search.

Work with us

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

Stay informed Get our weekly newsletter. Never sold or shared, unsubscribe anytime.

Let us serve you Church leaders and ministry networks seeking translated curriculum Join our team Volunteers interested in reviewing translations
Download Translation Skill

Linguistic Gap Analysis

Linguistic Gap Analysis

Persian’s translation gap has a distinctive shape: unlike Arabic, Persian has genuine native (pre-Islamic) vocabulary for several central terms, which is an asset, but its established Bible translation precedent is more recent and more actively contested (via the Hezare No controversy) than Arabic’s centuries-old tradition.

Terms with a genuine native-Persian option, unlike Arabic

  • God (خدا / Khoda): a native pre-Islamic word (from Middle Persian khwatay), unlike Arabic’s total dependence on الله. Used across Zoroastrian, Christian, and Muslim Persian traditions alike.
  • Lord (خداوند / Khodavand): similarly native, not a specific Quranic title the way Arabic’s الرب is — the collision here is about the underlying tawhid claim, not about borrowing a scripture’s own proper title.
  • Father (پدر / pedar) and prophet (پیامبر / payambar): native Persian constructions rather than Arabic loanwords, though the theological objections they raise (anthropomorphism, prophetic finality) are shared with Arabic regardless of the word’s origin.

Terms requiring a deliberate, actively-argued choice against existing precedent

  • Law (ناموس, not شریعت): existing Persian Bible translations have used شریعت for the Mosaic Law; this Language Package departs from that precedent, following Arabic’s namus strategy instead, because Iran’s status as a state actually governed by shari’a-based law makes the collision risk more acute in Persian than in most Arabic-speaking contexts.
  • Son of God (پسر خدا, not برگزیده خدا): the Hezare No translation’s softened alternative is a live, real, and recent example of exactly the wrong choice; this Language Package explicitly documents why it rejects that precedent.
  • Adoption (فرزندخواندگی, not سرپرستی): Iran’s own civil law avoids full adoption terminology for religious-legal reasons; this Language Package deliberately uses the fuller term rather than following the state’s own weaker legal category.

Gap-filling strategy

Where Persian has a native option unavailable to Arabic, this Language Package prefers it (Khoda over a transliterated Allah, Khodavand over a borrowed Rabb-equivalent). Where existing Persian Bible precedent is contested or, in the Hezare No case, actively rejected, this Language Package documents the specific reasoning for departing from or following that precedent rather than treating either choice as self-evident.

Library content is free and openly licensed under CC BY-NC-SA 4.0 — share and adapt it for non-commercial use, with attribution to tri-bible.ai.

Give feedback

How would you rate this page?

0 / 500 words