Linguistic Gap Analysis
Linguistic Gap Analysis: James 1–5 (English → Pashto)
Purpose
This document executes Phase 1 Step 8. It does not re-derive the glossary (Step 1, already delivered in 08_core_glossary.md); it analyzes the linguistic terrain the glossary sits on: where Pashto has no ready vocabulary at all (missing vocabulary), where it has too much overlapping vocabulary competing for the same space (crowded semantic neighborhoods requiring fencing), where a source term should be transliterated versus paraphrased, and which ambiguities carry the greatest doctrinal danger if mishandled in Phase 2. All findings extend, and must not contradict, the baseline Romans Language Package and the James-specific bible_term_registry.json entries already established.
Coverage spans the full letter, James 1–5, with James 2:14–26 (Faith and Works) treated as the theological anchor rather than the analytic boundary.
1. Doctrine Vocabulary Matrix
For each of the nine assigned doctrines: the Pashto vocabulary currently available, its structural weaknesses, and the recommended handling strategy for Phase 2.
1.1 Faith and Works (James 2:14–26, core passage)
| Available Pashto terms | Weakness | Recommended strategy |
|---|---|---|
| ایمان (iman) for faith; کارونه (karona) for works; مړه (mara) for dead(faith) | Pashto’s everyday register for “faith” (iman) is saturated with the six-pillars creedal-assent sense; “works” has an available high-register competitor (اعمال, deeds) that is doctrinally loaded with the Qur’anic mizan (deeds-weighing, 101:6-9) framework | Retain ایمان (baseline-established) but pair every 2:14-26 occurrence with narrative framing (Abraham’s act of offering Isaac, Rahab’s act of hiding the spies) so “faith” is shown, not merely asserted, to be inseparable from its fruit — this does the doctrinal work the lexicon alone cannot. Never substitute اعمال for کارونه under any register pressure, including more “elevated” or literary drafts. |
| صادق ګڼل کیدل (justification, reused from baseline) | Same phrase must carry two different technical senses across two different biblical books (Paul’s forensic declaration in Romans; James’s evidentiary vindication in 2:21,24,25) with no separate Pashto lexeme available to mark the difference | Mandatory harmonizing translator note at every James 2:14-26 occurrence (already flagged Critical in bible_term_registry.json). This is a structural gap in the language, not a translation error — Pashto (like most target languages) has no native mechanism to disambiguate lexically, so disambiguation must happen at the paratextual/explanatory level, never by inventing a second rendering. |
| د خدای ملګری (friend of God) | Strong pre-existing bridge (Khalil Allah) risks importing the Islamic khalil tradition’s own merit-based reading of why Abraham earned that title | Anchor explicitly to Genesis 15:6 / James 2:23’s causal chain: faith credited as righteousness → friendship follows. The gap here is not vocabulary but doctrinal sequencing; the strategy is explanatory anchoring, not lexical substitution. |
1.2 Trials and the Testing of Faith (James 1:2–4, 12–15)
| Available Pashto terms | Weakness | Recommended strategy |
|---|---|---|
| ازموینه (trial/testing), وسوسه (temptation) | Greek uses one word-family (πειρασμός/πειράζω) for both senses; Pashto’s two available terms are not natural synonyms so the reader may miss that James is doing deliberate wordplay across 1:2 and 1:13-14 | Retain the two-term split already fixed in the registry (ازموینه for positive external testing, وسوسه for internal enticement) but add a single explanatory footnote at 1:13 noting the wordplay so the “God does not tempt” argument is not read as a non-sequitur disconnected from v.2’s “trials.” |
| زغم (steadfastness/endurance) vs. صبر (patience-in-waiting) | Both would gloss as “patience” in English-derived study aids, risking translators or reviewers treating them as interchangeable and collapsing James’s two distinct pastoral movements (present endurance under trial, ch.1; future-oriented waiting for the Parousia, ch.5) | Enforce strict lexical separation per registry; add a cross-reference note at 5:7 pointing back to 1:3-4 so the relationship between the two (endurance produces the character that sustains patient waiting) is visible, not just the vocabulary distinction. |
| دوه‑زړی (double-minded) | No structural weakness — genuine positive bridge to Pashtunwali’s undivided-loyalty (nang) expectation | Use as a positive cultural asset; connect 1:8 forward to 4:8’s “purify your hearts” so double-mindedness is shown resolved, not just diagnosed. |
1.3 Wisdom from Above (James 1:5; 3:13–18)
| Available Pashto terms | Weakness | Recommended strategy |
|---|---|---|
| حکمت (wisdom), له پاسه حکمت (wisdom from above), ځمکنی/نفسي/شیطاني (حکمت) (earthly/soulish/demonic wisdom) | حکمت’s dominant cultural association is the Islamic hikmah philosophical-wisdom-literature tradition (proverbs, aphorisms, practical shrewdness); James’s “wisdom” is specifically relational/moral fruit (peaceable, gentle, full of mercy), not intellectual acuity or clever speech | Always pair حکمت with its concrete fruit-list (3:17) at first occurrence per lesson; never let the term stand alone as an abstract virtue. This is a crowded-neighborhood risk (see §2 below), not a missing-vocabulary gap. |
| شیطاني (demonic) | No weakness of substance — genuine shared devil-figure bridge | Use confidently; anchor to visible fruit (jealousy, disorder) named in 3:16, not occult/folk-magic associations. |
1.4 Favoritism and the Poor (James 1:9–11; 2:1–13; 5:1–6)
| Available Pashto terms | Weakness | Recommended strategy |
|---|---|---|
| جانبداري (favoritism), غریب (poor), شتمن (rich) | جانبداري as a named vice directly opposes Pashtunwali’s own status-deference etiquette (melmastia hospitality customs privilege honored/wealthy guests); there is no existing Pashto religious-register vocabulary that frames such deference itself as sin | This is a genuine missing-vocabulary gap at the conceptual level, not the lexical level — the word جانبداري exists and is adequate, but the underlying value judgment (deference-to-wealth-as-sin) has no cultural precedent to draw on. Strategy: explicit teaching that names the cultural default before correcting it (“in our culture X is customary; James 2:1 calls this exact behavior sin when it demeans the poor before God”), rather than assuming the term alone communicates the reversal. |
| بلل شوی (called), د خدای پاچاهي (kingdom of God) | No independent weakness; reused baseline terms functioning as designed | Standard baseline enforcement; connect 2:5’s “chosen the poor” explicitly against tribal-lineage/honor-based chosenness per baseline called/election notes. |
1.5 Taming the Tongue (James 3:1–12)
| Available Pashto terms | Weakness | Recommended strategy |
|---|---|---|
| ژبه (tongue), جهنم (Gehenna/hell), د خدای مثال/شان (likeness of God) | ژبه itself is linguistically Low risk, but the doctrine is High risk because speech (gossip, public insult, accusation) is a live trigger for honor-based retaliation and blood feud (badal) in the target culture — the danger is sociological, not lexical | No vocabulary gap to fill; strategy is contextual framing: teach 3:1-12 with explicit acknowledgment of real-world escalation risk, so the passage functions as practical safety wisdom, not only rhetorical metaphor. |
| د خدای مثال/شان (likeness of God) | Tawhid theology structurally resists any human-divine resemblance language; Pashto has no established devotional vocabulary for imago Dei since the mainstream regional theological tradition never needed one | Genuine missing-vocabulary gap. Strategy: periphrastic explanation (“made to reflect God’s moral character,” not “made in God’s physical form”) rather than seeking a single-word equivalent that does not exist in the tradition. |
1.6 Worldliness versus Friendship with God (James 1:27; 4:1–10)
| Available Pashto terms | Weakness | Recommended strategy |
|---|---|---|
| دین (religion), هوس (desires/passions), (روحاني) زنا کوونکې (spiritual adultery), د نړۍ سره ملګرتیا (friendship with the world), خدای ته تابع شئ (submit to God) | Two distinct crowded-neighborhood problems converge here: (a) دین is Islam’s own totalizing self-designation; (b) ملګرتیا root is stretched to carry both a strongly positive sense (2:23) and a strongly negative sense (4:4) within the same letter; (c) تابع/تسلیم structurally overlaps with the root meaning of “Islam” itself | See §2 (fencing) below for detailed disambiguation strategy for each. No missing vocabulary here — the risk is entirely overcrowding, not absence. |
| زنا کوونکې (adulteresses, metaphor) | Acute missing-safe-vocabulary gap: Pashto has no devotional-register metaphorical-idiom equivalent for OT covenant-unfaithfulness-as-adultery that does not also trigger the literal, socially lethal honor-code meaning of زنا | Mandatory explanatory framing at every occurrence (already Critical in registry); this is the single highest real-world-danger gap in the entire letter (see §4, rank 1). |
1.7 Prayer and Healing (James 5:13–18)
| Available Pashto terms | Weakness | Recommended strategy |
|---|---|---|
| د ایمان دعا (prayer of faith), په غوړ سره تیلي کول (anoint with oil), مشران (elders) | Oil-anointing risks conflation with folk-Islamic amulet (taweez) and ruqya exorcism practice, which is widespread in regional folk religion and shares surface features (physical object + prayer + healing intent) | No lexical gap; strategy is explicit negative contrast — teach what this practice is not (not a protective charm, not exorcism) alongside what it is (simple faith-expressing pastoral act), since silence on the distinction invites syncretistic reading. |
| مشران (elders) | Crowded neighborhood: same word denotes tribal/village jirga elders with customary legal-adjudication authority | See §2 below. |
1.8 Patience and the Lord’s Return (James 1:2–4, 12; 5:7–11)
| Available Pashto terms | Weakness | Recommended strategy |
|---|---|---|
| صبر (patience-in-waiting), د خداوند راتلل (coming of the Lord), د ایوب زغم (Job’s endurance), که خداوند وغواړي (if the Lord wills) | صبر and که خداوند وغواړي are both extremely strong positive bridges but also extremely close in surface form to Islamic devotional vocabulary (sabr as a named virtue; “In sha’Allah” formula), risking the doctrine being absorbed into generic Islamic piety rather than read as distinctively grounded in Christ’s specific, promised return | No missing vocabulary; strategy is anchoring every occurrence explicitly to the specific object of hope — Christ’s return as Judge/Bridegroom (5:7-8) — never left as generic patient submission to divine decree. |
| د خداوند راتلل (Parousia) | Acute missing-vocabulary gap: no existing Pashto Christian-register term for the technical NT concept of a singular, sovereign, self-initiated return of a divine Judge, since regional eschatology (Isa’s return subordinate to the Mahdi, opposing the Dajjal) has no structural equivalent to this claim | Periphrasis only (“د خداوند راتلل,” the Lord’s coming/arrival) plus mandatory contrastive teaching against the Mahdi-subordinate framing; this is Critical and ranks highly in §4. |
1.9 Confession and Restoration (James 5:16, 19–20)
| Available Pashto terms | Weakness | Recommended strategy |
|---|---|---|
| یو تر بل ګناهونه بیانول (confess sins to one another), ډیری ګناهونه پوښي (cover a multitude of sins) | اقرار (the natural high-register word for “confession”) carries formal/judicial-admission connotations under Islamic jurisprudence categories; پوښل (“cover”) risks the honor-shame “cover-up-to-preserve-honor” script rather than gracious forgiveness | No true missing-vocabulary gap; the risk is a false-friend collision (see §2). Strategy: periphrastic descriptive phrase already adopted (یو تر بل … بیانول, “relate/tell to one another”) rather than the loaded اقرار noun, plus mandatory framing of “covering” as forgiveness-after-repentance, never concealment. Safety framing is paramount given persecution context — this is ranked among the highest-risk items in §4. |
2. Crowded Semantic Neighborhoods Requiring Fencing
Unlike the baseline Romans package (which mostly documented false-friend collisions with a single dominant religious tradition), James repeatedly reuses the same Pashto root for two or more distinct in-letter senses. This is a different and additional class of risk: internal crowding, not just external collision. Each needs an explicit “fence” — a rule for how the term must be marked, glossed, or contrastively taught at each occurrence so one sense does not bleed into the other.
| Root | Senses in James | Fence required |
|---|---|---|
| ملګرتیا (fellowship/friendship root) | (1) baseline Christian fellowship (Romans, Low risk); (2) “friend of God” (2:23, High, positive); (3) “friendship with the world” (4:4, High, negative/condemned) | Every occurrence in James must carry an explicit qualifier — “د خدای ملګری” never appears bare as “ملګری,” and “د نړۍ سره ملګرتیا” must always retain “د نړۍ سره” (with the world) so readers cannot misread it as commendation of ordinary sociability or confuse it with church fellowship. |
| ناموس (law root) | (1) Romans’ Mosaic Law argument (Critical, baseline); (2) “law of liberty” (1:25, Critical, distinct referent — Christ’s ethic); (3) “royal law” (2:8, same referent as #2); (4) God as “lawgiver” (4:12) | Fence: James’s ناموس occurrences must NEVER be taught as a continuation of the Romans Mosaic-Law discussion. A standing rule for Phase 2: any segment using ناموس in James must include a one-line disambiguating gloss identifying which of the two distinct doctrinal referents (Mosaic Law vs. Christ’s liberating ethic of love) is active, since the same Pashto word cannot self-disambiguate. |
| صادق ګڼل کیدل (justification) | (1) Paul’s forensic declaration (Romans, initial); (2) James’s evidentiary vindication (2:21,24,25, subsequent/demonstrative) | Fence: mandatory harmonizing note at every James 2:14-26 occurrence (already specified in the registry) explaining these are sequential moments of one reality (declared righteous by faith, then shown righteous by works), not competing definitions. |
| دین (religion) | Only one sense in James (1:27) but sits inside Islam’s own crowded self-designation space in the wider culture | Fence: 1:27’s redefinition (“pure and undefiled دین… is this: to visit orphans and widows…”) must always be presented as a redefinition of an existing term the reader already holds strong assumptions about, with explicit contrast to ritual-observance notions of din, and an explicit caution that this redefinition is not itself a route to salvation by good works (connecting to the Faith-and-Works fence above). |
| تابع/تسلیم-family (submit) | Only one sense in James (4:7) but shares root meaning with “Islam” (submission) itself and with Pashtunwali’s competing loyalty codes (nang, tribal-elder authority) | Fence: “خدای ته تابع شئ” must always appear paired with “خدای ته نږدې شئ” (draw near to God, 4:8) in the same teaching unit so submission is never taught in isolation from relational nearness — preventing a reading of submission as mere hierarchical distance or performative Islamic-style submission. |
| مشران (elders) | Church elders (5:14) vs. tribal/village jirga elders (everyday usage) | Fence: always qualify as “مشران (کلیسا)” or an equivalent descriptive clause (“د کلیسا مشران,” the church’s elders) at first occurrence per lesson; never leave bare مشران in a healing/prayer context, since the everyday sense carries customary-legal adjudication authority Christ’s model does not intend. |
| زغم / صبر (endurance vs. patience) | Distinct Greek roots (ὑπομονή vs. μακροθυμία) mapped to two Pashto near-synonyms | Fence: treat as strictly non-interchangeable in all Phase 2 output; a QA rule should flag any segment where the two are swapped relative to their assigned Greek source term. |
| حکمت (wisdom) | James’s concrete, fruit-defined wisdom (3:17) vs. general regional hikmah-tradition wisdom (proverbial cleverness, philosophical insight) | Fence: never let حکمت stand as a bare abstract noun in James; always require the accompanying fruit-list or an equivalent descriptive clause at first occurrence per lesson. |
General fencing rule for Phase 2: wherever a single Pashto root is required by the glossary to carry more than one distinct sense within James itself (not just versus the baseline), the segment-level translator note must name which sense is active, not merely which term is used. This is a stricter requirement than the baseline’s single-collision-per-term model, because James’s letter compresses far more semantic range into fewer, more everyday words than Romans’ more technical argumentation.
3. Transliteration vs. Paraphrase Decisions
James contains fewer brand-new theological technical terms than Romans (most of its vocabulary is drawn from everyday moral-exhortation registers), so the transliteration-vs-paraphrase question is less about proper nouns and more about whether a compact Greek theological compound should get a single Pashto loanword, a native compound, or a fuller descriptive phrase.
| Term | Decision | Rationale |
|---|---|---|
| παρουσία (coming of the Lord) | Paraphrase, not transliteration | No transliterated form (“پروسیا”) exists in any Pashto Bible tradition; a loanword would be theologically opaque to a low-literacy oral-culture audience. د خداوند راتلل (“the Lord’s coming/arrival”) using ordinary vocabulary, reinforced by explicit teaching, is far more accessible and still fully retains the technical weight through context, not through a special loanword. |
| θρησκεία (religion) | Native-vocabulary rendering (دین), not a coined neologism | A coined term would forfeit the entire rhetorical strategy of James 1:27, which depends on redefining a word the reader already owns. Paraphrase-with-redefinition, not transliteration, is the correct move. |
| γέεννα (Gehenna) | Transliteration/loanword (جهنم), following the Islamic-Arabic cognate, not a periphrastic “place of fire” | جهنم is already the settled term across the region’s Islamicate religious vocabulary and requires no introduction; periphrasis here would sound evasive or unfamiliar. Risk is managed by scope-limiting explanatory notes (do not import the full tiered-punishment doctrine), not by avoiding the loanword. |
| δίψυχος (double-minded) | Native compound (دوه‑زړی), not a loanword | No existing loanword tradition for this concept; a transparent native compound (“two-hearted”) is immediately intelligible and carries a positive cultural resonance (undivided loyalty/nang) that a borrowed term would not. |
| ἔμφυτος λόγος (implanted word) | Partial paraphrase with retained کلام, flagged, not full paraphrase-only | کلام is retained because “word of God/gospel message” needs a noun with sufficient theological weight, but it must always appear inside the fuller phrase (د حقیقت کلام, ریښه شوی کلام) rather than standing alone, precisely because bare کلام risks activating the ilm al-kalam / Kalam Allah (Qur’an) association. This is a hybrid decision: transliteration-adjacent noun choice, paraphrase-level framing. |
| μοιχαλίδες (spiritual adultery) | Paraphrase with explicit metaphor marker, never a bare loan or direct literal noun alone | (روحاني) زنا کوونکې retains the root but the mandatory bracketed “(روحاني)” qualifier functions as an obligatory paraphrase-level safety fence, not an optional stylistic choice — this is the letter’s single most safety-critical rendering decision (see §4). |
| Ἀββά / other proper names (Job/Ayub, Elijah/Ilyas if referenced) | Established transliteration per existing Pashto Bible tradition, consistent with baseline proper-name conventions (Dawud, Musa, Esha’ya) | No new decision needed; follow settled forms. Note: James 5:11’s “Job” = ایوب (Ayub), already a positively-loaded shared figure; James 5:17’s “Elijah” (if included in lesson content) = الیاس (Ilyas) per standard convention, not previously logged in the baseline and should be added to translation memory as a new Low-risk proper name if used. |
General principle for Phase 2: transliterate only where (a) an established loanword already carries the needed content with acceptable risk (جهنم), or (b) the target audience’s oral/low-literacy profile makes an unfamiliar coined term counterproductive. Paraphrase wherever the technical content has no existing settled Pashto Christian equivalent (παρουσία) or where the rhetorical strategy of the passage itself depends on redefining ordinary vocabulary (θρησκεία).
4. Ranked List of Highest-Risk Ambiguities in James
Ranked by combined severity of (a) doctrinal distortion potential and (b) real-world safety/social consequence for the persecuted, honor-shame-embedded readership.
-
“Spiritual adultery” (4:4, μοιχαλίδες) — Highest rank. Decontextualized quotation of زنا-rooted vocabulary carries literal, sometimes lethal, honor-code danger (honor-killing risk) in addition to doctrinal risk. Every single occurrence, in every lesson artifact, must carry the mandatory “(روحاني)” metaphor marker and explanatory OT-covenant-idiom framing; this is the one ambiguity in the letter where a translation error is not merely theologically wrong but potentially physically dangerous to real people.
-
“Justified by works” vs. Romans’ “justified by faith” (2:14-26, δικαιόω) — The passage most likely to be lifted out of context (by both a skeptical Muslim interlocutor and a well-meaning but confused new believer) as proof James contradicts Paul, reinforcing exactly the deeds-weighing (mizan) soteriology the whole Language Package exists to correct. Requires the mandatory harmonizing note at every occurrence, with zero exceptions, and should be flagged for theologian review even in seemingly low-stakes derivative content (quizzes, summaries).
-
“Coming of the Lord” / Parousia (5:7-8) vs. Islamic Isa-returns-subordinate-to-Mahdi eschatology — A shared vocabulary/different content collision at the same severity tier as the baseline’s Critical
messiahandresurrection_of_christentries; every occurrence needs explicit contrastive teaching, not just consistent vocabulary, or readers will silently map James’s picture onto the familiar regional end-times scheme. -
“Confess your sins to one another” (5:16) — safety framing — Not primarily a doctrinal-content risk but an operational-safety risk: any rendering or teaching implying formal, public, or judicially-recorded confession could expose readers to real danger if intercepted or misunderstood by hostile outsiders. Must always be taught as small, voluntary, trusted-circle disclosure.
-
“Law of liberty” / “royal law” (1:25; 2:8) vs. Romans’ Mosaic-Law ναμος argument — High risk of flattening two distinct referents of the same Pashto word (ناموس) into one, especially for readers or even secondary translators who encountered Romans first in this same Language Package and default to the earlier learned sense.
-
“Wisdom” (1:5; 3:13-17) left unanchored from its named fruit — Risk is subtler than the above (Medium in the registry) but pervasive: حکمت’s strong positive cultural resonance with the hikmah tradition makes it easy to teach as generalized shrewd or proverbial wisdom rather than James’s specific, morally-defined, peaceable fruit — diluting rather than distorting doctrine, but diluting consistently across every occurrence if unaddressed.
-
“Religion” (1:27) redefinition — Risk of the redefinition being heard as “good deeds constitute true religion,” reinforcing a syncretistic deeds-based framework rather than James’s intended point that genuine faith inevitably produces such deeds; must always be taught in the same breath as the Faith-and-Works doctrine, never as a stand-alone ethical maxim.
-
“Submit to God” (4:7) read as generic Islamic submission or competing Pashtunwali loyalty — Risk of the term being absorbed into either of two existing, well-formed loyalty frameworks (Islamic submission; Pashtunwali nang/tribal-elder loyalty) rather than being heard as a call to a specific relationship with the God of the gospel; mitigated by the mandatory pairing with “draw near to God” (§2 fence).
-
“Anoint with oil” (5:14) conflated with folk-Islamic ruqya/taweez practice — Real syncretism risk given surface similarity (physical object + prayer + healing intent) to widespread regional folk-religious healing practice; requires explicit negative contrast, not just positive description.
-
“Elders” (5:14) conflated with tribal jirga authority — Lower doctrinal severity than the above but a persistent low-grade risk across every occurrence in ch. 5; mitigated by consistent qualification per the fencing rule in §2.
5. Summary and Handoff
- Missing vocabulary (no adequate existing Pashto term at all) is concentrated in technical NT-specific concepts with no regional theological precedent: Parousia/coming of the Lord, imago Dei/likeness of God, and the James-specific evidentiary sense of justification. All three require periphrasis plus mandatory contrastive teaching, never a coined single-word solution.
- Crowded semantic neighborhoods (too much existing vocabulary competing for the same space) dominate this letter more than missing vocabulary does, reflecting James’s everyday moral-exhortation register: ملګرتیا, ناموس, صادق ګڼل کیدل, دین, تابع/تسلیم, مشران, and زغم/صبر all require explicit fencing rules per §2, to be encoded as segment-level QA checks in Phase 2.
- Transliteration decisions favor established loanwords only where already settled in regional Islamicate vocabulary with manageable scope risk (جهنم); paraphrase is preferred everywhere the technical content has no settled Pashto Christian precedent.
- Highest-risk ambiguities combine doctrinal distortion risk with, in several cases (spiritual adultery, confession of sins), acute real-world physical/social safety risk for this persecuted readership — a dimension of severity that must weight the review-routing decisions in Phase 1 Step 2 (Doctrine Analysis) at least as heavily as pure theological-content risk.
This analysis is the required input to Phase 1 Step 2 (11_doctrine_analysis.md) risk-tier confirmation and to the James-specific extension of translation_memory.json in Phase 1 Step 3. No baseline Romans entries are altered; all findings here extend the baseline’s existing collision-documentation model to the additional internal-crowding risk class specific to James’s register.