Missing localization support for all user-facing texts in Rich Text (Web) widget

[valczak]

The widget doesn't support local languages for all the texts that users see.

The Rich Text (Web) widget doesn't currently provide a way to translate or localise texts that users see, including not only the labels of buttons on the toolbar (e.g. Bold, Italic, Left align, Insert link), but also any other texts rendered by the component itself.

Also, the widget doesn't give developers access to the Quill instance, which stops them from applying translations via Quill's configuration or a custom locale.
This means that any time you try to adapt something for a different country, you have to use workarounds that are difficult to keep up and not very good for large-scale use.

Current situation
At the moment, Mendix developers who need to display texts in their editor that are written in the local language have only two difficult options:

1. Write custom JavaScript actions to manually change HTML attributes (like title, aria-label, placeholder, etc.) after the editor has been rendered. This approach is fragile (not very stable), takes a long time, and doesn't work well with applications in more than one language.
2. Get the widget source code, change the TypeScript code, and then recompile their own version with translations that are hardcoded. This means it won't work with future Mendix releases and it's not suitable for production apps.

Quill itself doesn't support full i18n, but the Mendix implementation already defines all labels and messages programmatically.
So, it would be easy to show these texts as settings, which would let developers provide localised strings through the Mendix Modeler.

Things are likely to get better.

Please think about adding:

• A "Localization / Labels" property group that lets users change all the user-visible strings directly in the widget configuration.
• This provides support for finding labels in the current application language ($currentLanguage or i18n resource bundles).
• Ideally, it should cover every text that can appear in the component, such as toolbar items, tooltips, placeholders, link dialogues and other messages.

This is important for the following reason:

Mendix applications are often designed to support multiple languages, and this widget is officially maintained by Mendix.
It's very important to provide full localisation support to make sure that users have the same experience every time and that it's in line with the platform's localisation standards.

Without this support, developers have to use unstable JavaScript fixes or keep separate widget builds, which go against Mendix's "low-code, multi-language" promise.

Adding proper i18n support would:

• Make the widget much easier to use in global applications.
• Don't use workarounds.
• And make this part of the software work better with other Mendix widgets.

[gjulivan]

currently, we don't have a way to translate widgets aside from making everything as text template.
the proper way to do this should be through system text translation.
currently on discussion as feature request.

[valczak]

I can help ;)
I can even prepare a ready-made widget code that includes these changes. It really seems simple, just a bit of clicking and it's done.