Imagine a brand carrying an old line into a new product film: “Suitable for every model in this range.” The translation tool finds identical source wording and returns last year's approved translation. The words match—but nobody has yet confirmed what “this range” means for the new release. This is a hypothetical example, not an ONCE client case.
Reuse is valuable. Treating a match score as approval for today's product is not. Overseas teams working with Chinese manufacturers need the conditions behind approved language, not just a collection of familiar sentences.
Text matching does not validate product scope
DeepL's About translation memories describes storing and reusing previous translations through TMX uploads. A 100% match means the current source matches the stored source segment; an in-context exact match also matches the preceding and following segments. The undated page was reviewed October 27, 2026.
“Context” here has a specific textual definition. It does not establish that the product, accessory, market or instruction version remains unchanged. Even identical surrounding sentences cannot approve a new product claim. That is ONCE's procurement inference from the definition, not an allegation that DeepL promises product approval.
The usage guide says glossary entries take priority over memory, describes matching thresholds and provides TMX download by appropriate administrators. Reviewed October 27, 2026; no publication date established. These are application and access conditions—not a guarantee that a glossary repairs every old sentence or that every account can export.
Separate approved terminology, reusable phrasing and permission to make a current statement. The first two support the third; they do not replace it.
ONCE's reuse eligibility card
This is a proposed working method, not a software standard or a tested system. Add four groups of information to language worth reusing: origin, conditions, changes and approvers.
Origin links the source and translation to a script or video segment, language and locale, and approved revision. Do not label machine drafts, unreviewed subtitles and approved voice scripts alike. Retain any project-specific reuse restriction.
Conditions identify the product or model scope and necessary assumptions. Prioritize phrases such as “every model,” “no additional accessory” and “ready to use.” Ask the product owner what conditions are implicit. A linguist can assess the wording without being able to verify engineering compatibility or authorize broader claims.
Changes describe what differs from the source project. If a condition has changed, suspend the affected segment for the new release, preserve the earlier project's history and revise the current wording. You need not discard the whole memory, but you should not erase what the old project actually published.
Approvers identify who confirmed the product facts and who approved the target-language expression for the release. These are distinct responsibilities. A native-language reviewer should not have to certify a product scope they cannot verify.
In the fictional example, if the new range has different compatibility, fix the source meaning first. Then decide whether to retain, adapt or remove the line. Changing one translated word is insufficient if the narration or demonstration still implies the broader promise.
A memory file is not a finished localized film
GoLocalise's localization glossary describes audiovisual translation as adaptation within timing and picture constraints, and terminology management as agreeing key terms and approved translations. Relevant entries reviewed October 27, 2026; no publication date established. This is that provider's professional explanation, not a requirement to use one particular tool.
A reusable sentence still needs a presentation check. Can viewers read the subtitle? Does the on-screen text agree? Does the voice refer to the object being demonstrated? Has removing an earlier sentence removed a necessary limitation? Approved manual wording may need adaptation for a fast voiceover or mobile subtitle.
Language handover and editing-project handover are also separate. A translation memory does not automatically include a timeline, voice recordings, fonts or graphic layout. If a new supplier needs to continue the work, define the authorized language assets, approval records and production files, then verify the agreed use. Technical exportability does not establish unrestricted redistribution rights. Keep client material separated and respect confidentiality.
Accumulate decisions, not just old text
Start with approved segments that genuinely merit reuse, not every informal or temporary version. On the next batch, review changes, reuse what still applies and separately translate, review and adapt new material. A software subscription cannot replace an accountable maintenance owner.
Price initial preparation, source-condition confirmation, target-language review, video adaptation and bounded maintenance separately. Reuse may reduce repeated drafting; no fixed saving follows from a match score, and a match should not automatically mean no review. The work depends on source quality, changes and the requested delivery.
For ONCE, a durable language asset is authorized content with stated conditions and traceable approval—not the largest possible database. When the next 100% match appears, ask what has been matched and whether its intended use has been confirmed for this release.
Sources reviewed October 27, 2026. No DeepL account, TMX transfer or client language database was tested. The original cover is conceptual, not customer data.
