1
Language-Fallback on custom translations
Source: directus/directus#24944 · opened by @Dominic-Marcelino
Describe the Improvement
When a custom translation is missing for the current language the key is displayed. This could be optimized in two ways:
1. Fallback to same base-language (e.g if we're on en-US but only have a translation vor en-GB this would be better then nothing)
2. Fallback to projects default language
3. As a last alternative use the translation-key
When a custom translation is missing for the current language the key is displayed. This could be optimized in two ways:
1. Fallback to same base-language (e.g if we're on en-US but only have a translation vor en-GB this would be better then nothing)
2. Fallback to projects default language
3. As a last alternative use the translation-key
No pledges yet. Be the first to back this.
Comments
Similar requests
Enable field name translations to use "Custom translations"
1 vote · 0 comments
Bundle custom i18n translations with extensions
21 votes · 0 comments
Best Practices for Handling Translations in a Multilingual Website
3 votes · 0 comments
Revisions don't work together with translations
6 votes · 0 comments
Reusable Field Templates for Consistent and Efficient Schema Design
6 votes · 0 comments
No comments yet.