The practical answer
Set an approved translation or Keep original for each term, listing required variants as aliases. Preview matching with Replace terms only, then paste the complete draft and Check translation. The report measures coverage and occurrences; it does not establish sentence meaning or certify official names.
Agree on naming before expanding the glossary
Prepare the source, intended readers, a complete translation draft and evidence for approved product names. Without an official rendering, preserve the original or clearly identify an editorial choice. A preferred translation entered in a glossary does not become an official name. Confirm a small list before importing hundreds of terms.
Our original example uses a fictional product called Northstar. This project agrees on workspace for Arbeitsbereich and AI agent for KI Agent, while retaining Northstar. KI-Agent is an explicit hyphenated alias: this matcher does not automatically understand every grammatical form.
| Source | Target | Action | Alias |
|---|---|---|---|
| Northstar | Northstar | Keep original | None |
| Arbeitsbereich | workspace | Approved translation | None |
| KI Agent | AI agent | Approved translation | KI-Agent |
Use a short source that exposes missing terms
The source is: Northstar öffnet einen Arbeitsbereich. Ein KI-Agent nutzt den Arbeitsbereich. Keep the code `Arbeitsbereich` unchanged. Arbeitsbereich occurs twice in ordinary text and KI-Agent once. The occurrence inside backticks should remain unchanged. This diagnostic does not require an online translation request.
Open the terminology translation tool, add the three entries and set Northstar to Keep original. Leave Latin word boundaries and Preserve code and URLs enabled. Disable Original at first mention for an initial replacement-only comparison. Paste the source into the source field. If you later use Full translation for this sample, select German as the source and English as the target. These language selections do not change local glossary matching.
Original draft: locate the inconsistency before editing
Northstar opens a work area. An AI agent uses the workspace. Keep the code `Arbeitsbereich` unchanged.
Northstar opens a workspace. An AI agent uses the workspace. Keep the code `Arbeitsbereich` unchanged.
Choose the operation that matches the task
After replacement, check that both ordinary Arbeitsbereich occurrences changed and the backticked code stayed intact. Paste the first English draft above into the result field and run Check translation. The Arbeitsbereich row should show two source matches and one translation occurrence, requiring review.
DeepL’s XML documentation describes excluding tagged content from translation. This site’s online path protects specified content with markers. It does not use a glossary product to infer official naming. This article reports no paid-service trial or real-account translation benchmark.
Three different outputs
Replace terms only
Replaces matched glossary terms. Surrounding German stays German. Use it to inspect matching, not as a finished English translation.
Full translation
When configured and available, sends the source, glossary and context to this site’s service and DeepL. Configuration, quota and connectivity still affect the request.
Check an existing draft
Paste a complete draft to compare glossary coverage with the source. Glossary editing, replacement and this check run in your browser.
Matching counts do not establish correct placement
Covered means the output contains at least as many target occurrences as the source has matched terms. A draft can repeat workspace twice in its first sentence and still mistranslate the second. Shared target renderings, annotations and repeated text can also affect counts.
For each review item, locate the source and destination sentences. Look for omission, mixed names, explanatory words mistaken for a rendering, and translated brands that should stay unchanged. Continue with the numbers, negation and conditions review for complete meaning. Terminology consistency is one acceptance layer.
Human checks after coverage
- Every source occurrence has an appropriate destination position.
- Fixed wording fits grammar, number and domain usage.
- Brands, backticked code and URLs remain as intended.
- Numbers, negation, conditions, responsible parties and unresolved ambiguity are checked separately.
Keep the glossary with the deliverable and review report
Recheck after editing. Download the translation, review CSV and glossary JSON or CSV. Retain the source version, glossary version and open questions. The source and version locator workflow can help organize naming evidence.
Save glossary locally uses this browser’s storage and does not synchronize devices. Clearing browser data can remove it, so download a backup. Imports accept UTF-8 CSV, TSV or JSON. Separate aliases with | and resolve duplicate source terms or aliases first.
Current limits are 200 entries, three aliases per entry and 20,000 source characters. Split long documents at sensible paragraph boundaries while retaining one agreed glossary. Protection recognizes common code and URL forms; it does not guarantee preservation of every syntax or content type.
Common questions
Why does replacement still contain German?
Only matched glossary terms change. Other source text remains unchanged. For a complete translation, use the available online action or paste a finished draft for review.
Can I deliver when all rows say Covered?
Check every sentence first. Counts do not align sentences, judge meaning or certify names. Repetition and shared renderings can allow a flawed draft to satisfy the counts.
Why are plurals or abbreviations missed?
Matching uses explicit terms and aliases rather than automatic inflection. Add appropriate variants, then inspect word boundaries and case settings to avoid accidental replacements.
Further reading & sources
Put the guide into practice
Open the relevant tool, preview the result and check your exported file.
