Linguistic Gap Analysis

German rarely lacks a word for a Romans concept — its native compounding ability (Menschwerdung, Kindschaft, Gnadengaben, zugerechnete Gerechtigkeit) in fact gives it unusually precise, non-borrowed vocabulary for several concepts other languages in this batch must render with a Latinate loanword or a compound phrase. The real gaps in German are sensitivity and register gaps, not vocabulary gaps.

Terms requiring careful qualification

• Salvation (Rettung / Erlösung / Heil): three overlapping words exist, and the most doctrinally precise, “Heil,” carries Nazi-era contamination risk. This is a genuine three-way translation decision with no clean single answer, requiring case-by-case reviewer judgment rather than one blanket rule.
• Imputed righteousness (zugerechnete Gerechtigkeit): must be explicitly distinguished from “verdiente Gerechtigkeit” (earned righteousness, rejected), since the compound alone does not automatically block a merit-based misreading without the doctrinal note attached.
• Calling (Berufung): collides with both the everyday career-calling sense and the unrelated legal-appeal sense (Berufung einlegen), a homonym problem requiring context rather than compounding to resolve.

Terms requiring sensitivity notes rather than compounding

• Gentiles/Heiden: the term itself is linguistically adequate and traditional, but pairing it with “Juden” requires an explicit historical-sensitivity note given Germany’s specific 20th-century history, a genuinely different kind of “gap” than a missing word — a gap in how safely the existing word can be used without further framing.

Terms with no gap at all

• Incarnation, adoption, spiritual gifts: German’s native compounds (Menschwerdung, Kindschaft, Gnadengaben) give precise, doctrinally apt renderings with minimal ambiguity, among the strongest linguistic assets in this Language Package compared to the other five languages in this batch.

Gap-filling strategy

Where German has multiple candidate words (as with salvation), this Language Package documents the trade-off explicitly in translation_memory.json rather than picking one word and hiding the reasoning, so translators and reviewers can make an informed, context-sensitive choice each time.