Skip to main content

Choosing source language and target language(s)

Learn how to select the right source and target languages for translations in Elovate, including DeepL and GPT language support.

Updated this week

When setting up a translation job in Elovate, selecting the source and target languages is essential.

This determines the language your content will be translated from and into.


1. Source language

The source language is the language in which your original content is currently written.

Example: If your Magento store’s default content is in Dutch, your source language should be Dutch.

This must match the actual store view or entity data in Magento to ensure accurate translations.


2. Target language(s)

The target languages are the languages you want your content to be translated into.

Example: If you want to expand into the German market, set your target language to German (DE).

  • You can select multiple target languages in one job.

  • Example: Translate from Dutch → English (UK), French (FR), and German (DE) in a single job.


3. Supported languages

Elovate supports all languages provided by its integrated providers:

  • DeepL – High-quality neural translations, but limited coverage (e.g., no Croatian).

  • GPT – Covers virtually all languages and dialects, including those not supported by DeepL (e.g., Croatian).

You can mix providers across different jobs — e.g., use DeepL for supported EU languages, and GPT for languages not covered by DeepL.


4. How to set source & target in a job

  1. Go to Apps → Translations → Jobs.

  2. Click Add new translation job.

  3. Under Select a translation, choose a predefined translation setting or create a new one.

  4. In the translation settings:

    • Translate from – Select your source language.

    • Translate to – Select one or more target languages.

  5. Save your settings and continue configuring your job.


5. Best practices

  • Always verify your store view language matches your chosen source language to avoid mistranslations.

  • If your content contains specialized terminology, link a glossary to ensure consistent translations.

  • For bulk multi-language expansion, consider running separate jobs per target language for better control and QA.

Did this answer your question?