Enable field name translations to use "Custom translations" #19226
Replies: 2 comments 2 replies
-
Yes 100%. I actually thought this was already an open issue! |
Beta Was this translation helpful? Give feedback.
2 replies
-
This feature request was accepted. Implementation will be tracked here! #19228 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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:
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 could be automated.
We could imagine to auto-migrate all existing Field name translations, and use as the translation key the field key, and if there's already something with that key, add a simple increment (so field_1, field_2, etc.).
Unresolved Questions
No response
Beta Was this translation helpful? Give feedback.
All reactions