Manage languages
This guide applies to the branch selected in Current branch. Keys, values, languages, tags and file mappings are independent between branches. See branch navigation and branch permissions.
Use Languages to inspect the source, targets and their active state. All workspace members can read the configuration. Owner/Admin can change it while the workspace, project and selected branch are active.
Add a target language
Section titled “Add a target language”- Open the project’s Languages page.
- Under Add target language, open Target language.
- Search by English name or enter a standard code. Use Use entered code to validate a code entered manually.
- Select Add language.
The target is added as active and falls back to the source by default. Select its row to inspect the chain or change its fallback.
Understand the states
Section titled “Understand the states”| State | Behavior |
|---|---|
| Source | Always active, has no fallback, cannot be replaced or deactivated. |
| Active | A target that can be selected as another language’s fallback. |
| Inactive | Keeps its saved fallback and can be reactivated. Cannot be chosen as a fallback target. |
An inactive language already exists in this branch. Reactivate its row rather than trying to add it again.
Deactivate a target
Section titled “Deactivate a target”Select the target row, choose Deactivate language, read the effect and confirm.
A language used as fallback by any active or inactive language cannot be deactivated. The error lists dependent language codes. Change each dependent language’s fallback first, then retry.
Deactivation preserves the target’s own fallback. You can edit that fallback while the target is inactive, provided the branch, project and workspace are active.
Reactivate a target
Section titled “Reactivate a target”Select the inactive target, choose Reactivate language and confirm. The saved fallback is validated and retained. Reactivation does not create a duplicate language.
Handle a conflicting change
Section titled “Handle a conflicting change”Language changes advance the branch’s configuration version. Project settings keep a separate version. If someone changed the branch configuration after your screen loaded, refresh and review the latest configuration before submitting again. Do not assume your old selection still has the same effect.
See Fallback chains for valid links and Project settings for archive restrictions.
Choose whether we remember appearance preferences and use Google Analytics on Localisync and its documentation. Optional storage stays off until you accept.
Read our cookie policy