1
Enable field name translations to use "Custom translations"
Source: directus/directus#24904 · opened by @rijkvanzanten
Discussed in <div type='discussions-op-text'> <sup>Originally posted by ruihildt July 24, 2023</sup> Summary Custom translations are useful because you can centralize all translations in the same place. Basic Example _No response_ Motivation Unfortunately, field name translations can't use the Custom translations. So sometimes you will have to duplicate translations, and not every translations will be centralized in the same place. Detailed Design Next to the "Create new" button (or instead), add the translation icon to make it possible to select an existing custom translation Requirements List Must Have: • easy pick from the Custom translations Drawbacks No drawbacks. :) Alternatives Don't do anything and keep the issue unsolved. Adoption Strategy If you already have translation, I guess it would be nice to offer to add them to the Custom translations. Ideally this coul…
No pledges yet. Be the first to back this.
Comments
Similar requests
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
Include Translated fields in quicksearch
4 votes · 0 comments
No comments yet.