Linguistic Gap Analysis — Colossians (Turkish)

Continuing the prior baselines’ findings: Turkish handles Colossians’ cosmic and legal-financial metaphors with precision. This package identifies one genuine linguistic asset (senet) and confirms the sensitivity-application category already established for the tawhid confrontation and the household code.

Terms requiring careful qualification

• Firstborn of all creation (bütün yaratılışın ilk doğanı, πρωτότοκος πάσης κτίσεως): no vocabulary gap, but a sensitivity-application gap of the same category as Philippians 2:6 — the rank/supremacy sense must be made explicit against both a general “first created being” misreading and Islamic theology’s specific no-offspring doctrine.
• Fullness of deity, bodily (Tanrılığın bütün doluluğu bedensel olarak, πᾶν τὸ πλήρωμα τῆς θεότητος σωματικῶς): no vocabulary gap — Turkish states the incarnational claim precisely — but requires the same sensitivity-application discipline as the Christ Hymn.

Terms requiring sensitivity notes rather than compounding

• Household code (bağımlı olun, köleler/efendiler): fully inherited from the Ephesians package; no new gap, but the same sensitivity note applies without modification.

Terms with no gap at all — and one genuine asset

• Borç senedi (certificate of debt, τὸ καθ᾽ ἡμῶν χειρόγραφον, 2:14): a genuine linguistic asset — senet is a live, everyday Turkish legal-commercial term for a promissory note, giving this metaphor unusual concreteness, comparable to kapora’s role in the Ephesians package.
• Mesih her şeydir ve her şeydedir, meleklere tapınma: precise, well-established renderings requiring no gap-filling strategy.

Gap-filling strategy

Where Colossians presents a sensitivity-application risk (the Christ Hymn, the philosophy warning), 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.

Coverage confirmation

Covers linguistic-gap material relevant across chapters 1, 2, and 3; chapter 4 introduces no new gap beyond what is already addressed under the doctrine and sensitivity notes elsewhere in this package.