Read also
If you have already read our articles about fallback languages and how to manage them, let's overview the use cases and advise on how to use them better.
Fallback languages can boost your translation efforts. You should use fallback languages when:
localizing to pluricentric languages (e.g., British, American, Australian English or Austrian, Swiss, and standard German.)
you are working with brand-related data with similar text segments but different brand names.
Caution for uploads
For uploads, use the fallback language text segments with caution.
We advise you to refrain from uploading exported text segments again after using the fallback language feature. After uploading, your empty text segments will be overwritten. There is no setting to change this behavior.
The example below illustrates what would happen when you upload your target languages back to Lingohub.
Data before export
Text segment | Language | Fallback language |
- | de-AT | de-DE |
Apfel | de-DE | en-GB |
Apple | en-GB | - |
2. Export data/import data
Text segment | Language |
Apfel | de-AT |
Apfel | de-DE |
Apple | en-GB |
3. Data after import
Text segment | Language | Fallback language |
Apfel | de-AT | de-DE |
Apfel | de-DE | en-GB |
Apple | en-GB | - |
As you can see, Lingohub will automatically overwrite your previously empty text segment in the de-AT language. The fallback language workflow will not work anymore for the de-AT variant as it has been filled with content.
We, therefore, advise you to only export data when using fallback languages unless you are sure you want to overwrite previously empty text segments with fallback language translations.
Congratulations! You finished the article about fallback languages use cases. In case you have any questions - contact us.