Linguistic Gap Analysis
Linguistic Gap Analysis — Philippians (Turkish)
Continuing the Romans, Galatians, and Ephesians baselines’ findings: Turkish’s agglutinative morphology again serves this curriculum well. Philippians introduces one genuine sensitivity-gap pair (kul/köle) already partially addressed in Galatians, and confirms the associative-overload category for a new term (vatandaşlık).
Terms requiring careful qualification
- Form of God / equality with God (Tanrı özünde var olan / Tanrı’yla eşitliği, μορφῇ θεοῦ / ἴσα θεῷ): no vocabulary gap — Turkish states the claim precisely — but the sharpest sensitivity-application gap in this Language Package, given the direct tawhid confrontation. Requires explicit comparative-theology framing, not a rendering adjustment.
- Contentment (Beni güçlendirenin aracılığıyla her şeye gücüm yeter, 4:13): no vocabulary gap, but a structural/contextual-anchoring gap — the verse must be kept tethered to 4:11-12 in every teaching use, a discipline gap rather than a translation gap.
Terms requiring sensitivity notes rather than compounding
- Form of a servant (köle biçimini alarak, μορφὴ δούλου): linguistically adequate via köle, but requires the explicit kul/köle distinction note established in the Galatians package — a sensitivity gap of the same category as Galatians’ circumcision note, now recurring in a Christological (rather than ethical-exhortation) context for the first time.
Terms with no gap at all — and one genuine asset
- Vatandaşlığımız göklerdedir (citizenship in heaven, πολίτευμα, 3:20): a genuine linguistic and cultural asset — vatandaşlık’s strong legal/civic resonance in Turkish gives this metaphor unusual clarity, arguably more concrete than in languages where “citizenship” carries less everyday civic weight.
- En yüce yere çıkardı, İsa Mesih Rab’dir: precise, well-established renderings requiring no gap-filling strategy.
Gap-filling strategy
Where Philippians presents a sensitivity-application risk (the Christ Hymn’s tawhid confrontation,
the kul/köle distinction) or a contextual-anchoring risk (4:13), this Language Package documents
the framing requirement explicitly in translation_memory.json and 02_cultural_context.md,
following the same contextual-containment strategy established in prior packages, rather than
softening the underlying claim.
Coverage confirmation
Covers linguistic-gap material relevant across chapters 2, 3, and 4; chapter 1 introduces no new gap beyond what is already addressed under the doctrine and sensitivity notes elsewhere in this package.