Translation Landscape

Existing Urdu Bible translations

The Urdu Bible Society (and predecessor 19th and 20th century mission translation efforts) established a continuous Urdu Christian Bible tradition still in active use across Pakistan and North Indian Urdu-speaking churches. This Language Package follows that tradition’s precedent for its highest-risk proper names and core terms (خدا, یسوع, خداوند, مسیح, روح القدس) rather than introducing new renderings.

Where existing translations fall short for this curriculum

• Doctrinal precision vs. readability trade-offs: the Urdu Bible Society text is a translation of Scripture itself, optimized for continuous devotional reading. A Bible study curriculum needs to be more explicit — for example, explaining why Son of God language does not mean physical begetting, rather than simply using the correct term and trusting context to prevent a shirk-reading.
• No systematic doctrine-level risk framework for Islamic-theology-specific collisions: existing Urdu Bible translation work renders Scripture faithfully but does not, as a translation project, systematically flag which doctrines require explicit contrastive teaching against Qur’anic denial versus which are safely shared vocabulary. This Language Package’s doctrine_risk_registry.json fills that gap for this curriculum specifically.
• The Khuda/Allah choice requires active, documented defense, not passive inheritance: usage varies across the wider Urdu-speaking Christian world, with some editions using Allah (correctly noting that Arabic-speaking Christians have always used the word without contradiction) and others, including this Language Package, preferring Khuda specifically to avoid this curriculum’s Trinitarian and Christological claims being heard as claims about the Qur’anic Allah under a different label. Existing translations do not uniformly resolve this, so this Language Package states and defends its own choice explicitly (see the god entry in translation_memory.json).

Readiness assessment

Urdu is comparatively well-positioned in translation-tradition terms (unlike Maithili): a real, continuously used Christian Bible translation tradition already supplies settled proper names and core terms. The translation task here is not tradition-building but disciplined, explicit doctrinal contrast-teaching layered onto an already-adequate vocabulary base — the vocabulary mostly exists; the systematic risk-flagging and pastoral framing around specific Qur’anic negations is what this Language Package adds.