i18n support for templates

[ripla]

When creating templates,
I want to use i18n keys as values,
so that I can use the same i18n strategy in my whole UI

The user should be able to use some predefined format in text content and attribute values to input i18n keys.

[gianluca-valentini]

I am very surprised, since this strongly affects the development of a web application with Vaadin 10.

This means that, currently, it is not feasible to create an enterprise web application, and I need to use 'old' approach using all java code to localize the web presentation pages.

It's a big limitation as well as a big problem.

[lightoze]

I've created a mixin and a server-side class which can attach to any Component to alleviate the problem: https://gist.github.com/lightoze/04a115e4331f6cbee9e875d192a7cd46

In your Java component constructor you add I18nBinding.create(this) line and then in template code use it like so:

<vaadin-text-field id="name" label="[[translate('Name')]]"></vaadin-text-field>

Translation parameters are not supported.

[jcgueriaud1]

Any ideas of how it could be handled for the next LTS?

There are 2 libraries for i18n lit that looks quite promising:

• https://www.npmjs.com/package/@lit/localize from the lit team and currently in active development
• https://github.com/andreasbm/lit-translate