We are building mobile apps that need to be used in multiple languages. We use the proposed way of work for mobile and reactive.
However several widgets in OutSystems UI have text that we can not easily change the language of, like for example the Action Sheet Cancel button that is automatically added as last button in the sheet.
It would be nice if we could easily handle translations for these types of text, and avoid us from cloning widgets.
Hi @Jakub Lubowicki,
The reason why this is not possible is that the product doesn't have a way to translate text elements from a producer module and, being OutSystems UI is a supported component it is not possible to open it and add the translations since the changes needed for this to be done would be huge and out of the scope of this team.To mitigate this, we're currently closing a version of OS UI where some locales will be already present and with the translations in place.If any is missing, we count on the community to bring us use cases and help us help you as much as possible to improve this topic.
Cheers,GM
Hi Daniël Kuhlmann,
Yes, you're right. We already aware of that, and will be working in a solution in the near future.
Best regards,
Bernardo Cardoso
Nice to know! That will be a solution.
Hi @Bernardo Cardoso
Is there a solution to translate widgets from OutSystems UI or still on Your list?
Hi @Gonçalo Martins ,
great to see an effort is made to improve on translations.
I just switched to version 1.17.0, and have some remarks/questions on the translations for the pagination widget, specifically for dutch.
1) is it possible to discuss the correct translations ?
1a) 'items' is translated as 'artikelen', this is a correct word, but it is not very generic, it is more suited for lists of things (like products), if you show lists of people, events, requests, logs, incidents, places,... 'artikelen' doesn't really sound right.
I am not a linguist or UI expert, but to me it feels like just leaving it to 'items' would be the better choice, or maybe a more neutral / generic term like 'rijen' (dutch for rows) or 'resultaten' (dutch for results).
For comparison, in the StackedCards widget, translation is sometimes Item, but also sometimes Artikel (in German by the looks of it :-( ) In the DEPRECATED carousel 'artikel' was used for previous and 'item' was used for next.
1b) 'to' is translated as 'naar', this is wrong, nobody would use that word in this context, 'naar' is about direction in the physical world (i.e. I went to ONE Lisbon => Ik ben naar ONE Lisbon geweest) For describing a range of values, you would use the word 'tot' as a translation for 'to'.
Or to be completely exact 'tot en met', which emphasis that the last value of the range is included, so '1 tot en met 10' would emphasise that result 10 is also displayed. This is a matter of taste, if you just use 'tot' for brevity, everyone will still understand.
2) how does it decide to use dutch translation ? Or how can I keep that decision in sync with the language of my application? I am now scaffolding a list screen in a module without any locale defined, I expect everything to always be in English, but the pagination is in dutch.
3) perfect solution would be to add a optional input parameter so as developer we can give a word instead of 'items' that suits the type of thing that is being displayed in the list. Is that something Outsystems would consider adding ?
Dorine
Hi @Dorine Boudry
Thanks for your feedback.
1) We already answered you directly by DM
2) The translation are applied based on application language. You just need to use the change locale action to set the locale on your app, add language on Multilingual Locales under the Data tab and the application will apply the translations accordingly to the file added. For the translations that are missing, will apply the defaults (EN).
3) This is already identified and is on our backlog. As soon as we can, we will make this improvement and release it, but for now, we can't share a date for this.
Thanks
thanks @b.marcelino ,
my point 2 is about all those applications that do not use setlocale, because they are not multilingual. For example, if I just create a new module, and scaffold some screens, set locale is not used anywhere, and the assumption is that the whole application is in English by default, but the pagination text is in dutch.
This could affect all existing list screens in all modules that are not multilingual, once they upgrade to version 2.17.0.