Linguistic Gap Analysis

Pashto’s translation gap is the largest in this batch: unlike Arabic, Hebrew, or Persian, it lacks both a deep native Christian theological tradition and a large, mature body of doctrinal-instruction vocabulary to draw on, requiring more deliberate construction than any other Language Package here.

Terms requiring careful, actively-argued construction

• Incarnation (تجسد): a loanword shared with Arabic and Persian but with the least settled local precedent of any language in this pipeline; periphrastic explanation (“God became a man”) should accompany the technical term rather than standing alone.
• Righteousness/justification (صداقت، صادق ګڼل کیدل): not a missing word so much as a missing cultural frame - honor-shame ethics do not supply an intuitive equivalent for forensic guilt-innocence categories, so this Language Package deliberately bridges through honor-restoration language rather than relying on a direct translation to carry the full doctrinal weight.
• Son of God (د خدای زوی): correct and necessary, but with no local Muslim-Idiom-Translation controversy of its own to draw lessons from; this Language Package applies Arabic’s and Persian’s documented experience proactively.

Terms with a genuine native-Pashto asset

• God (خدای) and Lord (خداوند): native pre-Islamic Iranian-language vocabulary (Pashto being an Eastern Iranian language related to but distinct from Persian), not exclusively Arabic/Quranic terms.
• Fellowship (ملګرتیا): a native word avoiding the shirk-root resonance that Arabic’s الشركة and Persian’s مشارکت both carry.
• Covenant (تړون) and intercession (منځګړیتوب): native Pashto words resonant with Pashtunwali’s own customary treaty-making and mediation institutions - real cultural assets, though each requires a caveat (see Comparative Theology) since the customary institutions are not exact equivalents of the biblical doctrines.

Gap-filling strategy

Where Pashto has a native-language option, this Language Package prefers it, both for linguistic authenticity and to avoid loanword-specific risks (like the shirk-root collision) inherited from Arabic. Where no settled precedent exists at all, this Language Package prefers transparent, semantically-motivated compounds paired with periphrastic explanation over an opaque technical coinage.