Translation assistance
Every source of a translation, next to the string.
Translation memory, terminology, and machine translation from DeepL, Google Translate, or Azure Translator meet in Translation Hints, and validation checks each suggestion. The translator chooses; repeated work is done once.
- Sources
- Translation memory, terminology, machine translation, duplicates
- In one place
- Translation Hints, applied with Ctrl+1 to Ctrl+0
- MT providers
- DeepL, Google Translate, Microsoft Azure Translator
- Editions
- Memory and MT: Professional and higher. Terminology: Enterprise
On this page
Four sources, each with its own job.
Your account, your provider.
Professional and higher
Machine translation uses your own account with the provider. Text goes to a provider only when you use machine translation; projects stay local files.
DeepL
Localizer picks the free or paid DeepL endpoint from your key.
Google Translate
Connect with an API key (v2) or a service account (v3).
Microsoft Azure Translator
Connect with the key and region of your Translator resource.
Test each key in settings before you start. Keys are stored in Windows protected storage for each user, not in the project, so a project you send to a translator does not contain them. Availability depends on your provider account and language pairs.
Coming soon: AI translation and proofreading are planned for Enterprise.
What a tool translated is marked Auto.
Memory, terminology, machine translation, and Translate Duplicates give their translations the Auto status. The Needs Review filter finds them, for you or for a proofreader.
What translation assistance does and does not promise.
These capabilities accelerate translation work, but they do not replace human judgment or release verification.
What Lingobit helps with
- Suggestions from every source in Translation Hints
- Translation memory matches and TMX exchange
- One translation for repeated strings
- Terminology consistency and TBX import
- Machine translation with DeepL, Google Translate, or Azure Translator
- Validation of suggestions before they are used
What still needs human or project review
- Final translation quality
- Style and tone decisions
- Terminology approval
- Context-sensitive wording
- Machine translation review
- Provider credentials and third-party MT costs
- Final localization QA and application testing
Related capabilities
- Translation workflowTranslator Edition, translation tasks, proofreaders, XLIFF, and CSV.
- Visual localizationSee suggestions in the dialog or form before you accept them.
- Release workflowReuse translations across versions, scan changes, and automate repeatable steps.
- Localization QACheck placeholders and layout, run spellcheck, and catch issues before release.
- Compare editionsWhich translation assistance capabilities each Localizer edition includes.
Translate once. Reuse everywhere. Check every suggestion.
Translation memory, terminology, duplicates, and machine translation in one pane, with validation on every suggestion.