Would be amazing to be able to create string type tokens for localized content. One of the friction points of translating the design to the real thing is taking care of translations.
With string type tokens, we could define key names, such as homepageWelcome and have all the translations tokenized. Thanks to that, designers would be easily able to see how the UI behaves and renders in different languages.
WDYT?
I agree. Key-based translation is the common way in the FOSS world to translate UI strings. There are already some translation systems existing, which could be connected on the back-end.
I think it’s a great idea, though I’m not sure design tokens are the right location as they concern style rather than content. Though I appreciate a similar interface would work well. This would be a really cool plugin, it reminds me a little of the ContentMock plugin.
I understand and this could indeed be very handy to be able to switch from one language to another in one click, however I’m not sure this should be natively supported in a design tool like Penpot.
Translation usually occurs after the design’s completed (for the main language). So a workaround could be -to be able to present mockups in various languages- to duplicate a file once the design’s been validated, and then translate the strings inside in another language.
