Linguistic Gap Analysis — Malachi (English → Arabic)

Scope and Method

This analysis examines the destination-language (Arabic) resources available for translating Malachi’s five curriculum doctrines, identifies where Arabic’s existing theological vocabulary is (a) genuinely absent, (b) crowded by a competing Islamic or folk-religious sense requiring explicit fencing, or (c) adequate but requiring disambiguating apparatus. It extends — and must remain consistent with — the baseline translation_memory.json/bible_term_registry.json conventions established for Romans, and it anchors every recommendation to the terms already registered in 08_core_glossary.md and the Malachi additions to bible_term_registry.json. No renderings are altered here; this document supplies the reasoning and risk-ranking behind those already-recorded choices and flags residual open questions for Phase 2.

Malachi’s translation profile differs from Romans in one important structural way: Romans’ highest risks cluster around soteriological abstractions (grace, justification, righteousness) contested by Islamic theology at the conceptual level. Malachi’s highest risks cluster around concrete covenant-life categories that Islamic law has independently codified in exacting technical detail — tithing (ushr), divorce (talaq), and messengership (risala/rasul) — so that the Arabic words are not merely theologically loaded, they are legally and liturgically defined in the dominant tradition, with specific procedural content that Malachi does not share and must not be read into.

---

1. Doctrine Vocabulary Matrix

Doctrine	Available Arabic Terms	Weaknesses of Available Terms	Recommended Strategy
God’s Unchanging Love for His People	أحببتكم (loved you); اختيار الله [BASELINE]; أنا الرب لا أتغيّر (I do not change); خاصتي/ملكي الخاص (segullah)	(1) محبة/أحببتكم risks being read through Qur’anic mahabbah (Q3:31), where Allah’s love is explicitly conditioned on obedience (“say: follow me, then Allah will love you”) — the reverse causal order from Malachi’s unconditioned, prior, elective love. (2) “لا أتغيّر” genuinely overlaps with the kalam doctrine of Allah’s immutable attributes (sifat), but that debate is abstract/metaphysical, while Malachi’s point is pastoral: God’s changelessness is the ground of mercy toward a sinning people, not primarily a philosophical claim.	Retain baseline اختيار الله for the electing-love doctrine; render أحببتكم plainly but pair with a mandatory teaching note establishing sequence — love precedes and is not contingent on obedience. Foreground the pastoral register of “لا أتغيّر” (covenant faithfulness) over the philosophical one; do not let the lesson drift into comparative kalam debate.
Corrupt Worship and a Broken Covenant	الكاهن (priest); الهيكل (temple); مائدة الرب (table); عيب/عاهة (blemish); اللعنة (curse); تعليم الحق (instruction of truth); الناموس [BASELINE]	(1) الكاهن carries a residual pre-Islamic/hadith-era association with pagan soothsaying (kahin), a condemned figure in Islamic tradition — readers may import negative connotations onto the OT priestly office. (2) الهيكل risks being read through the contemporary Haram al-Sharif/Temple Mount political dispute rather than the historical-theological referent. (3) تعليم الحق must be kept distinct from الناموس’s technical legal sense (2:8 vs. 2:6) or the two Hebrew senses of torah collapse into one.	Use الكاهن with a first-use clarifying note distinguishing the consecrated OT sacrificial office from the soothsayer association. Keep الهيكل strictly historical-theological with an explicit disclaimer against contemporary political reading (parallel to the baseline’s Israel caution). Document the dual torah usage (technical vs. general “sound teaching”) as a standing translation-consistency rule for Phase 2.
Faithfulness in Tithing and Marriage	العشور (tithe); التقدمة (terumah); سلب/اختلس (rob); الطلاق (divorce); غدر/خان (dealt treacherously); نسل من عند الله (godly offspring)	(1) العشور is the historical technical name for the Islamic ushr agricultural tax, a distinct fiqh category from zakat — readers may assume Malachi is teaching the Islamic tithe-tax system rather than a Mosaic covenant provision now relativized by NT giving principles. (2) الطلاق is not merely a loaded word but names a fully codified Islamic legal procedure (triple talaq, iddah, etc.) with no biblical equivalent structure — Malachi 2:16 is a moral condemnation of covenant-treachery, not a competing divorce statute. (3) The Hebrew behind “godly offspring” (2:15) is itself disputed among Hebraists; no Arabic rendering can resolve an unresolved Hebrew text.	العشور retained per glossary but MANDATORY explicit distinguishing note at every occurrence (OT Mosaic tithe ≠ ushr/zakat; relate to but do not equate with NT giving). الطلاق retained (no viable substitute exists) but framed exclusively as condemnation of covenant-breaking treachery, never as commentary on or critique of Islamic family law procedure — flag for mandatory theologian review at every occurrence, consistent with the Critical-tier escalation already recorded. Render “godly offspring” with a visible translator’s footnote naming the textual difficulty rather than presenting one gloss as settled.
The Coming Messenger and the Day of the Lord	الملاك/ملاكي (messenger); ملاك العهد (messenger of the covenant); الرب [BASELINE]; يوم الرب العظيم والمخوف (Day of the LORD); شمس البر (sun of righteousness); إيليا النبي (Elijah)	(1) الملاك is the standard Arabic word for a created angelic being; Malachi’s מַלְאָכִי is a human forerunner (fulfilled in John the Baptist), so the default reading actively misdirects the referent. (2) The alternative رسولي collides with الرسول, Muhammad’s own Qur’anic title — risking a false “seal of the messengers” comparison in the opposite direction. (3) يوم الرب has a fully developed, doctrinally incompatible Islamic parallel (Yawm al-Qiyamah/Yawm al-Din) with no assured individual outcome, unlike Malachi’s binary judgment/healing framework.	Retain الملاك/ملاكي per established Van Dyck OT tradition (changing it now would break OT-wide consistency), but attach a mandatory disambiguation note at every occurrence: (a) human forerunner, not a created angelic being; (b) no claim of prophetic finality parallel to khatam an-nabiyyin. Teach يوم الرب against, not alongside, the Yawm al-Qiyamah framework — assured, particular, personal outcome (healing for the God-fearing, judgment for the arrogant) vs. deeds-weighing uncertainty.
The Call to Repentance before the Great Day	ارجعوا إليّ فأرجع إليكم / التوبة (return); خائفو الرب (those who fear the LORD); سِفر التذكار (book of remembrance); عبادة الله عبث (vain to serve God); لعنة تامة/هلاك (cherem)	(1) التوبة (tawbah) as a stand-alone term risks importing the more transactional Islamic repentance pattern (sincere regret + cessation + resolve, restoring standing through the act itself) rather than Malachi’s God-initiated, relationally-reciprocal restoration (“return to me and I will return to you” — God’s returning is itself the promised gracious response, not an automatic mechanical consequence). (2) تقوى was rejected as the rendering for “fear of the LORD” (see below) precisely because it would pull this whole doctrine toward the same legal-piety category.	Prefer the fuller phrase ارجعوا إليّ فأرجع إليكم over the single word التوبة wherever space allows, precisely to keep God’s own prior initiative and gracious response visible in the wording itself, not merely explained in a footnote. Where التوبة must stand alone (space-constrained titles, headers), attach a footnote on first use per lesson.

---

2. Missing Vocabulary vs. Crowded Semantic Neighborhoods

2.1 Genuinely Missing Vocabulary (no adequate existing Arabic Christian term; compound/coinage required)

Concept	Gap	Recommended Handling
”Messenger of the covenant” as implicit incarnation claim	No existing Arabic Bible tradition phrase captures the apposition-based Christological identification embedded in 3:1 as compactly as the Hebrew does.	Retain the compound ملاك العهد (already registered) but treat it as a taught construction, not a self-evident phrase: lesson material must walk through the apposition (“the Lord… and the messenger of the covenant”) explicitly, linking to baseline incarnation and deity_of_christ notes rather than assuming Arabic syntax alone will convey the identification.
Refining/purifying fire distinct from judgment fire	Arabic has no single lexical item distinguishing “purifying metallurgical fire” from “destructive judgment fire” the way the Hebrew’s two separate images (מְצָרֵף vs. כַּתַּנּוּר) do.	Maintain the registered pairing نار المُنقّي (3:2-3) vs. كالتنور (4:1) as two deliberately distinct compounds, and require every lesson to state the contrast explicitly rather than leaving readers to infer it from vocabulary alone — Arabic will not do this disambiguating work automatically the way it might in a language with two native fire-purpose words.
The Hebrew idiom behind “godly offspring” (2:15)	The underlying Hebrew (זֶרַע אֱלֹהִים / שְׁאָר) is contested even among Hebraists; no Arabic gloss can supply certainty the source text itself lacks.	Do not manufacture false certainty via a single polished Arabic rendering. Use נسل من عند الله / ذرية تقية with a visible footnote naming the interpretive difficulty — this is a case where translation transparency about ambiguity is itself the correct choice.
A distinct term for “instruction of truth” (2:6, broad sound-teaching sense) vs. “the Law” (2:8, technical Mosaic-corpus sense)	Both senses trace to the same Hebrew root תּוֹרָה, but Arabic’s two chosen renderings (تعليم الحق vs. الناموس) must now do double duty distinguishing a distinction the English text itself preserves only by context.	Document as a standing Phase 2 rule: תּוֹרָה renders as تعليم الحق only in the “sound doctrine/faithful instruction” sense (2:6) and as الناموس only in the technical legal-corpus sense (2:8; 4:4) — never interchange, and flag any future occurrence where the sense is ambiguous for theologian review.

2.2 Crowded Semantic Neighborhoods Requiring Explicit Fencing

These are cases where Arabic vocabulary is not missing but is already densely occupied by a well-defined competing sense from Islamic theology, fiqh, or pre-Islamic folk religion — the opposite problem from §2.1, and in Malachi’s case the larger risk category.

Arabic Term	Competing Occupant of the Semantic Space	Fencing Required
الملاك (messenger, 3:1)	Standard word for a created angelic being (Jibril, Mika’il, etc.)	Mandatory note at every occurrence: human forerunner, not an angel; distinguish from the priestly “messenger” sense (2:7) and from the prophet’s own name (ملاخي).
العشور (tithe)	Historic technical term for Islamic ushr land/agricultural tax, distinct in mechanism and rate from zakat	Mandatory note distinguishing the Mosaic covenant tithe (supporting the Levitical priesthood/temple) from the codified Islamic tax category, plus a bridge to NT giving principles so the doctrine does not stop at “the OT tithe rate.”
الطلاق (divorce)	Fully codified Islamic legal procedure (fiqh categories: talaq raj’i, talaq ba’in, iddah, khul’)	Frame exclusively as condemnation of covenant-treachery in a specific historical dispute (2:14-16), never as commentary on, or implicit critique of, the Islamic legal procedure by the same name. Mandatory theologian review, every occurrence.
الكاهن (priest)	Pre-Islamic/hadith-era kahin — a pagan soothsayer/diviner, an explicitly condemned figure in Islamic tradition	First-use clarifying note: the OT كاهن is a consecrated sacrificial mediator under divine appointment, not a diviner; typologically fulfilled in Christ’s priesthood.
مخافة/خشية الرب (fear of the LORD)	تقوى (taqwa), the load-bearing Qur’anic virtue-category — God-consciousness within a legal-piety framework, functioning almost as a summary term for the whole religious life of a Muslim	تقوى explicitly rejected as primary rendering throughout (already recorded at 1:6 and 3:16); consistent use of the خشية/مخافة root reinforces a relational, filial reverence rather than importing the taqwa devotional architecture wholesale.
التوبة (repent/return)	Islamic tawbah — sincere regret, cessation of the sin, resolve not to repeat, understood as the human act that (by God’s mercy) restores standing	Prefer the fuller phrase ارجعوا إليّ فأرجع إليكم to keep God’s own initiating and answering action visible in the sentence itself; treat التوبة alone as a shorthand requiring the fuller phrase nearby.
اللعنة / لعنة تامة (curse / cherem)	لعنة carries everyday folk-religious usage (evil eye, sorcery curses) in colloquial registers	Keep register formal/fusha throughout to avoid folk-magic association; the escalation from general اللعنة (1:14; 2:2; 3:9) to the stronger cherem term at 4:6 should be flagged in teaching notes as intensification, not treated as interchangeable synonyms.
الوحي (massa/oracle, 1:1)	The Qur’an’s own defining category of revelation — verbatim divine dictation to a single final prophet	Mandatory disambiguating note at the book’s very first verse: prophetic inspiration here works through the human author’s own voice/idiom over time, not one-time verbatim angelic dictation; sets the interpretive frame for the entire book before any other term is encountered.
إله العدل / إله القضاء (God of justice)	Bridges positively with al-‘Adl (Divine Justice, one of Allah’s 99 names) but that tradition grounds justice’s vindication in a future deeds-weighing (mizan)	Note the shared vocabulary as a genuine bridge point, but ground Malachi’s answer to the theodicy complaint (3:13-18) in the coming Messenger’s redemptive work, not merely in an eventual impartial audit.
ملك عظيم (great King)	Bridges with Al-Malik (The Sovereign), one of Allah’s names	Low risk but distinguish explicitly from [BASELINE] ملكوت الله (kingdom, a reign/domain) — great King (1:14) names God’s person and title, not the kingdom concept; do not conflate the two entries in teaching material.

---

3. Transliteration vs. Paraphrase Decisions

Term	Decision	Rationale
מַלְאָכִי / מַלְאַךְ (messenger)	Established-word retention (الملاك/ملاكي), not transliteration, not paraphrase	A transliteration (malʾakhī) would be unrecognizable to Arabic readers and orphan the term from the whole Van Dyck OT tradition; a paraphrase (e.g., “the sent one,” المُرسَل) would sacrifice continuity with the prophet’s own name (ملاخي) and the wordplay the book depends on. Retention + mandatory disambiguation note is the only strategy preserving both continuity and doctrinal accuracy.
מַשָּׂא (massa, burden/oracle)	Paraphrase/compound (الوحي / قول الرب), not transliteration	A transliteration would be meaningless to readers; الوحي alone risks the wahy collision, so the compound قول الرب is offered as an alternative less-loaded phrasing to be weighed case-by-case in Phase 2, with the disambiguating note doing the heavier doctrinal work regardless of which is chosen.
אֵלִיָּה (Elijah)	Christian-tradition transliteration retained (إيليا), Qur’anic form rejected as primary	إلياس (Ilyas) is the Qur’anic transliteration tradition and would create false confidence of a shared, fully overlapping account; إيليا (Van Dyck) is correct continuity with the Arabic Christian Bible tradition but requires a bridging note since Muslim-background readers may not recognize it as the same figure without help, and the Ilyas Qur’anic account lacks the John-the-Baptist forerunner typology entirely.
מְצָרֵף / מְטַהֵר (refine/purify)	Paraphrase (يُنقّي ويُطهّر), not a single transliterated technical term	No single Arabic word captures the metallurgical refining process; a two-verb paraphrase preserves both senses (removing impurity + making pure) without importing [BASELINE] التقديس’s different theological register (ongoing Spirit-sanctification vs. one-time priestly refining).
סְגֻלָּה (segullah, treasured possession)	Paraphrase (خاصتي / ملكي الخاص), not transliteration	No established transliterated loanword exists in Arabic Bible tradition for this term (unlike, e.g., “Amen” or “Hallelujah,” which are established transliterations); a relational-possessive paraphrase captures the sense while bridging to [BASELINE] اختيار الله.
חֵרֶם (cherem)	Paraphrase, not transliteration, and not treated as synonymous with the book’s general curse term	An Arabic transliteration (ḥirām/ḥerem) would be unintelligible and could be confused with the unrelated Islamic term حرم/إحرام (sacred/forbidden precinct, pilgrimage state) — a serious false-cognate risk. لعنة تامة / هلاك paraphrases the total-destruction sense without this collision, while flagging the escalation from the book’s general اللعنة vocabulary.
אָדוֹן (adon) — dual rendering	Context-split, not a single fixed transliteration or paraphrase	The same Hebrew root receives two different Arabic renderings by design: السيد (1:6, generic master-metaphor) vs. الرב (3:1, full Christological weight). This is a deliberate fencing strategy, not inconsistency — flagged explicitly to prevent a well-meaning Phase 2 “consistency” correction from erroneously unifying the two.
אבא/אב (Father, 1:6)	Baseline term retained (الآب), used in its lower-intensity covenantal-corporate sense	No paraphrase or transliteration alternative is needed; the same word as the baseline’s fully Trinitarian Father is retained deliberately, with a teaching distinction (this occurrence is God’s fatherhood over Israel corporately, not yet the fully Trinitarian hypostatic sense) rather than a different word, preserving forward continuity toward the NT sense.

---

4. Ranked List of This Letter’s Highest-Risk Ambiguities

Ranked by combined severity (doctrinal distortion potential) and likelihood (how easily a reader or even a careful translator could default to the wrong sense without active intervention):

1. מַלְאָכִי / מַלְאַךְ rendered الملاك (messenger, 3:1) — Highest risk in the book. The default Arabic reading is “angel,” a created being, which not only obscures the human-forerunner referent but weakens the Christological structure of 3:1 (a human forerunner distinct from the divine Lord who follows him). Compounded by the wordplay with the prophet’s own name. Mandatory theologian review, every occurrence.
2. הָאָדוֹן / הָרַב rendered الرب vs. السיד (3:1 vs. 1:6) — A single Hebrew root deliberately split into two Arabic words carrying opposite doctrinal weight. Any Phase 2 “normalize for consistency” impulse would silently destroy either the generic-metaphor register of 1:6 or the full deity-claim register of 3:1. Mandatory theologian review at 3:1; flag any deviation at 1:6.
3. מַעֲשֵׂר rendered العشور (tithe) — Near-certain default association with the codified Islamic ushr tax category for any reader with basic fiqh literacy (the majority of the intended Muslim-background audience). Risk is not mistranslation but silent doctrinal substitution — readers may assume Malachi teaches a comparable religious-tax obligation rather than a Mosaic covenant provision relativized by the New Testament. Mandatory theologian review, every occurrence.
4. שִׁלַּח rendered الطلاق (divorce, 2:16) — Unavoidable direct collision with a fully proceduralized Islamic legal category; the single highest pastoral-sensitivity item in the book given real marital, legal, and social stakes for readers. Mandatory theologian review, every occurrence; coordinate with pastoral/legal sensitivity guidance beyond the translation task itself.
5. מַשָּׂא rendered الوحي (oracle, 1:1) — Occurs in the book’s very first verse, meaning the collision with Qur’anic wahy sets the interpretive frame for everything that follows before any corrective teaching can occur. Mandatory disambiguation note required at first occurrence without exception.
6. אֶת־עֵשָׂו שָׂנֵאתִי rendered أبغضت/كرهت (Esau I hated, 1:3) — Risk of readers hearing raw emotional animus rather than the Hebrew idiom of relative covenant preference, especially given Romans 9:13’s direct quotation — any wording drift between the Malachi and Romans curricula on this exact clause would create a visible, citable inconsistency. Requires cross-curriculum wording verification against the Romans Language Package before Phase 2 release.
7. אֲנִי יְהוָה לֹא שָׁנִיתִי rendered أنا الرب لا أتغيّر (I do not change, 3:6) — Genuine bridge with Islamic divine-immutability doctrine risks pulling the lesson into abstract kalam debate at the expense of the verse’s actual pastoral function (grounding assurance of ongoing mercy toward a sinning people). Risk is one of emphasis distortion rather than mistranslation.
8. הֵיכָלוֹ rendered الهيكل (temple, 3:1) — Contemporary Temple Mount political sensitivity risks anachronistic contamination of a historical-theological reference, paralleling the baseline’s documented caution on “Israel.”
9. זֶרַע אֱלֹהִים / שְׁאָר rendered نسل من عند الله (godly offspring, 2:15) — Risk here is presenting false interpretive certainty on a genuinely disputed Hebrew phrase; the ambiguity is in the source text, not introduced by Arabic, but must be flagged rather than silently resolved.
10. יוֹם יְהוָה הַגָּדוֹל וְהַנּוֹרָא rendered يوم الرب العظيم والمخوف (Day of the LORD) — Safe shared vocabulary at the word level, but Islamic eschatology’s fully developed, competing Yawm al-Qiyamah framework (deeds-weighing, no assured individual outcome) means every occurrence requires active doctrinal correction, not passive translation — parallel in structure to the baseline’s resurrection risk pattern.
11. כֹּהֵן rendered الكاهن (priest) — Pre-Islamic soothsayer association is a lower-frequency but real risk of negative-connotation transfer at first encounter, mitigated by a single clarifying note.
12. בָּגַד rendered غدر/خان (dealt treacherously) — Not a collision risk but a consistency risk: the doctrinal force of this passage depends on the same Arabic root recurring at every one of its six occurrences (2:10, 11, 14, 15×2, 16) to bind worship-unfaithfulness to marital-unfaithfulness; any Phase 2 stylistic variation would sever this deliberate literary link.

---

5. Follow-On Actions for Phase 2

1. Treat items #1–#5 above (messenger, adon-split, tithe, divorce, massa/wahy) as mandatory theologian-review gates — no segment containing these terms may be marked approved without human sign-off, per the baseline’s Critical-tier escalation rules.
2. Verify wording of item #6 (Esau I hated) against the Romans curriculum’s existing rendering of Romans 9:13 before finalizing Malachi 1:3, to guarantee cross-curriculum citation consistency.
3. Confirm the torah dual-rendering rule (תּוֹרָה = تعليم الحق in 2:6 vs. الناموس in 2:8/4:4) is written into the Phase 2 segment-cache instructions explicitly, since this distinction is invisible without documentation.
4. Confirm the two-fires rule (نار المُنقّي vs. كالتنور) and the adon-split rule (الرب vs. السيد) are both encoded as explicit non-normalization exceptions in any automated consistency-checking tooling used in Phase 2, so that well-intentioned uniformity passes do not erase deliberate doctrinal distinctions.
5. All findings above should be reflected in the forthcoming Malachi-specific additions to translation_memory.json, bible_term_registry.json, and doctrine_risk_registry.json, consistent with 08_core_glossary.md Section D.