Localizing Email Templates
One template can carry a version per language. The template itself holds the source subject and body; every other language is a translation of it, so a wording change has a single place to be made. Recipients receive the version matching their own language whenever one exists.
The language row and the Languages list column appear only when the portal has more than one active language. Activate the languages you need first - see Configuring Language Settings.
Requires Edit permission to add or save a translation, and Delete permission to remove one.
Adding Languages
- Author the subject and body in the source language first. Every translation is based on it.
- Click Add language.
- Select one or more languages, then choose the Starting content mode.
- Click the confirm button - Translate N languages or Add N languages. The editor switches to the first language added.
| Starting content | What you get | Best when |
|---|
| Translate from source with AI | A generated first draft for every selected language. | You want a usable starting point immediately. Requires the AI Assistant license (see below). |
| Copy from source | The source content duplicated, for you to localize by hand. | Faster than blank - you edit each version down. |
| Start blank | An empty version. | The localization differs significantly from the source. |
Languages already on the template appear pre-ticked and disabled, marked Added. When every available language is already present, the drawer reports No more languages to add.
Editing Each Language
Use the language selector to move between versions and edit each one's subject and body independently. The source version is marked Source.
Keeping Translations Current
There is no staleness tracking. A translation is used whenever it exists, even if the source has changed since. Two mechanisms help you keep them aligned:
- At save time. When you save a source change while translations exist, Apply changes to translations? appears. Choose the languages to update and click Apply to selected, or click Skip translations to leave them as they are.
- On demand. Use Regenerate translation on a single language, or Manage > Regenerate all translations for every language at once.
- Regenerating overwrites. Both routes replace that language's subject and body and confirm before running. On failure the existing content is left untouched.
- Applying to translations runs one language at a time, with progress shown. A large template with many languages takes noticeably longer than a plain save.
- Bulk regeneration is resilient. It continues even if an individual language fails, then reports which languages failed and why.
- AI translation requires the AI Assistant license. It is part of your Magentrix subscription, not a setting an administrator can switch on. Without it, Translate from source with AI, Regenerate translation and Regenerate all translations are not shown at all - only Copy from source and Start blank are available, and translations are maintained by hand. If your plan does not include it, contact your Magentrix representative.
How AI Translation Protects the Email
AI translation rewrites only human-readable text. Merge tokens, links, images and structure are preserved exactly. If a translation would modify, remove or reorder a merge token, or alter a link, image or structural element, the result is rejected and the previous content is kept rather than saved.
Size limit. AI translation sends the body plus its translation instructions to the AI service, and the whole request is capped at roughly 10,000 characters. Because the instructions count toward that cap, the usable body budget is somewhat under 10,000. Templates that exceed it cannot be AI-translated - use Copy from source or Start blank and translate by hand, or split the email.
Removing a Translation
Use Delete this translation on that language, or Manage > Delete all translations. Both confirm first and cannot be undone.
The source language always remains. It is never offered as a delete target. Deleting the language you are currently editing returns you to the source.
What Else Gets Localized
Choosing the right-language subject and body is only half of it. When the email is sent, custom labels, picklist values and date and number formatting inside the body also render in the recipient's language. See Email Template Localization at Send Time in the Developer Guide for the exact behavior.
Messages You May See
| Message | Cause |
|---|
| Unsupported language code. | A translation was requested for a language that is not active on the portal. |
| A localized version already exists for this language. | That language is already on the template. |
| AI translation service is temporarily unavailable — please try again shortly | The AI service returned nothing. This is also what an unlicensed organization sees if an AI action is reached. |
| translation didn’t preserve all merge fields or links | The translation altered merge tokens, links or structure and was rejected. The existing content is kept. |
| this template is too long for AI translation… | The request exceeded the AI service's 10,000-character limit. |
| an unexpected error occurred — check the event log | An unclassified failure during translation. |
| Regeneration failed. Existing translation was kept. | A single-language regeneration failed; nothing was overwritten. |
| Re-generation failed. Existing translations were kept. | A bulk regeneration failed; nothing was overwritten. |
| Couldn’t add the language. Please try again… | The add-language request itself failed, as opposed to a per-language translation failure. |
<< Editing Email Templates | Previewing and Testing >>