Introducing a Unified Translation Policy Across the Mendix Platform - Mendix Forum

Introducing a Unified Translation Policy Across the Mendix Platform

1

I think we should create a formal translation availability policy in Mendix. At the moment, translations across the platform are incomplete, even for components directly provided by Mendix.

Often, text is hardcoded in the widget or module source, meaning it can't be translated. Mendix is great for building apps in multiple languages. But there are some things that just can't be translated.

This includes widgets, modules and system elements like enumerations, which can't be translated because the permissions are missing. This means developers find it hard to deliver fully localized apps for customers in different countries, who expect all visible text to be translated.

This issue affects a lot of components across the platform. I suggest that Mendix come up with a clear policy that says all Mendix-provided elements have to fully support translations, and that they update the widgets and modules they already have.

Developers should be able to translate any text that end users can see. The Rich Text widget is a good example of this issue. It has hardcoded button labels, tooltips and messages like character count text. Also, you can't translate the dialogues for inserting attachments or links without injecting JavaScript. This approach is unprofessional and not maintainable, which severely limits the ability to build multilingual applications.

I'm urging Mendix to make sure that all the components it delivers have full translation support, so that developers have the tools they need to offer complete localisation for their users.

asked
0 answers