AI translation and glossary

ReRune integrates with DeepL and OpenRouter. Configure the integration with the provider credentials required by your account. Where project AI settings are available, choose the provider and model you want the project to use.

The integration uses the connected provider account. Provider availability, supported languages, model behavior, and provider charges depend on that service and configuration. Check the provider response if a translation request fails.

• DeepL setup in the dashboard
• OpenRouter setup in the dashboard

• AI translation management overview

Use the Glossary for terms that need the same treatment across messages. Add each term with its approved translation per language. Mark brand names and other words that must stay as written as Do not translate, and words you never want in a translation as Forbidden. For a single language, list the wordings to avoid next to its translation.

When you translate a key, ReRune looks for Glossary terms in the source text, including common inflected forms. AI translation receives only the terms it finds, as instructions. DeepL receives only those terms too, as a hint it may not follow. In languages written without spaces, a term may also match inside a longer word.

ReRune saves nothing in DeepL. Matching terms travel with each request as a hint, in every DeepL language, and DeepL doesn't bill for it. When es-MX and es-AR have different terms, ReRune sends a request for each, and DeepL bills both. A regional language DeepL doesn't receive, such as de-AT when the project has de, gets its terms through AI translation only.

To change a term itself, use Rename. ReRune first lists the keys and languages it would change, and what it leaves alone. It changes drafts only; published text stays as it is until you publish.

You can export the Glossary as a CSV file and import one. An import first lists the terms it would add or update, before anything is saved. It adds terms and overwrites the cells you filled in: description, flags and approved translations. Banned wordings are only added. It never deletes a term, changes a term itself or touches drafts, and a blank cell keeps what is stored.

AI translation also receives Project Context and Translation Style from AI Settings. DeepL does not. The project's Description and Guidelines are notes for your team: ReRune does not send them to AI or DeepL. Review all of these when your product language changes.

1. Start with accurate main-language text and enough context to resolve ambiguity.
2. Select the messages and target languages and run the available translation action.
3. Check the result for meaning, terminology, placeholders, plural forms, and space constraints.
4. Save the reviewed text and publish through your normal delivery workflow.

Treat generated output as a draft. A fluent sentence can still use the wrong domain term or change the meaning of a short action label.