Exact-match reuse
Translation memory helps when the same source string appears again. LangKit keeps project-specific source-and-target pairs so a later identical source can be reused. Exact matches avoid a new provider call.
Memory is not a glossary
Translation memory stores complete source-target pairs. A glossary holds preferred terminology such as account, subscription or checkout. The two solve different consistency problems and should be maintained separately.
Human review still matters
An exact match does not guarantee the right choice in every context. Review potentially ambiguous interface text, particularly when a short source label can have multiple meanings.
Common questions
Does reuse spend standard translation credits?
Exact translation-memory reuse in the existing engine is free.
Can community proposals change the memory?
Unreviewed community submissions are not added as authoritative translation memory.
Before relying on this in production
Confirm support for your resource syntax and test exported translations in your application. Documentation describes supported workflows, not a guarantee of lossless conversion for every specialized format.