- Issue created by @Anybody
- 🇩🇪Germany Anybody Porta Westfalica
Most of the other types beside "Token" don't seem to be that important to be translatable, but it also wouldn't do any harm, I think.
- 🇩🇪Germany Anybody Porta Westfalica
Maybe using translatable schema types is a good first step to give it a try. Additionaly we'll then have to add the *.config_translation.yml for the UI?
https://github.com/erpushpinderrana/config_translations_example/blob/mai...@Grevil could you give it a try? I'll show you an example where it affects us.
- First commit to issue fork.
- 🇩🇪Germany lrwebks Porta Westfalica
@anybody, I think that I might be misunderstanding what you want from this issue. Do you want the extra fields to be translatable within their config (on the “Manage extra fields”) page, or within a content entity form (when editing a content entity with extra fields)? As far as the second one goes, I don't think that there is a universal option for doing this with every entity, because this requires the entity to be translatable as well. Also, I'm a bit confused since you appear to want the second solution, but your talk about a
config_translation.ymlseems to lean toward the first solution.TL;DR: Could you clarify what you want to be translatable specifically?