I’d like to preview a translated language file in SquareLine Studio.
This is useful to verify the string lengths and layouts are good.
Our current workaround is to manually test each function of the device, but it’s really time-consuming to fix the simplest layout errors, which are obvious as sono as the translated string is loaded.
Hi, Thanks for your feedback! Yes, this would indeed be an important feature, and we’re thinking about how to implement it.
One closely related note: it would be great if there were an option to build a fake language - for each phrase, take the longest string from each translation file. Of course each language would still needed tested separately(due to wrapping and line-breaks and such), but this would help us design UI layouts with enough space for most of the languages from the first pass.
LVGL added a new translation engine: Translation - LVGL 9.4 documentation
It’s seems easier to use fore then the YAML based version.
Mixed feelings here.
It’s nice having the translations in their own files, so it’s easier to send for translations and copy the updates back in.
But plenty of groups have their own translation processes, and this change will ease integrating into other workflows.
Yeah, YAML is really easy to script and convert to anything. Pure C, on the other hand, is more integrated and straightforward.
I only need to support English and German, and since I’m fluent in both, I can handle the translation myself. That’s why I value the simpler workflow of the new translation method.
Anyways, now we can decide. 