Add a target language
Add a language to translate into, and have the project's existing strings translated into it.
Adding a target language needs the Developer role or above. Translators and Reviewers can work in a language but cannot add one.
Add the language
Find the add row
Open the project. The last row of the Locales table on the overview is Add a language. The same control is on Settings, then Languages.
Pick the language
Type into Search languages to search by English name, native name or tag (for example "German", "Deutsch" or de), and pick it from the list. The source language and the languages already in the project are not offered.
Add it
Select Add.
Confirm the translation
If the project has strings to translate into the new language and Auto-translate is on, the console asks first: Add language and translate into it? "Everything already in this project is translated into language as soon as it is added." The dialog shows how many words that is. Confirm to add the language and start the translation.
If you pick a regional form of a language the project already has, for example pt-PT when it has pt-BR, a warning says so before you add it. Both are allowed, but each is translated separately: no strings carry over between them.
What happens next
The language joins the Locales table, and a message says what happened to the project's existing strings:
| Message | Meaning |
|---|---|
| "Language added. GLOSSA is translating 240 strings into it. Reload the page to see its progress." | A translation run has started. |
| "Language added. 12 strings came straight from translation memory, so they are in the language already." | Every string was reused from earlier translations, at no cost. |
| "Language added. Nothing in the project was waiting to be translated into it." | There was nothing to translate. |
| "Language added. Auto-translate is off for this project, so nothing has been translated into it yet." | Translate it from the editor with Translate missing when you are ready. |
| "Language added. There are no source strings in the project yet, so nothing is being translated into this language." | Import your strings first. |
| "Language added. There was not enough word quota left this cycle to translate the existing strings into this language." | The language was added, untranslated. |
| "Language added. AI translation is paused for this project, so the existing strings were not translated into this language." | The language was added, untranslated. |
| "Language added. Your access does not cover this locale, so the strings already in the project were left untranslated." | You can manage languages but are not scoped to this one. |
Whatever you type or pick is stored as a standard BCP-47 tag, so pt-br and pt-BR are the same language. See Languages and locales.
Language limits
On the Free plan, an account can use a limited number of languages across all its projects, counting source languages; a language already used by another project in the account does not count again. Paid plans have no language limit. See pricing.
If it doesn't work
- "That language is already in this project.": the language, or the same language under another spelling, is already a target or the source.
- "Unknown locale: use a BCP-47 tag like de, pt-BR, or zh-Hans.": the tag is not a language transglot recognises.
- "The account this workspace belongs to has no room for another language on its plan.": the account has reached its plan's language limit. Upgrade, or pick a language the account already uses. See Change your plan.
- Add a language is not shown: you need the Developer role or above.