i18n support for webcomponents

[alexgarel]

What

• Do we need to support translations in webcomponents ?
• If yes, integrate an existing library to handle that (the most standard one).
• If no (because it can be done by the integrator with his framework of choice), just add documentation on how to do it.

[alexgarel]

@alexfauquette, @VaiTon I would appreciate your insights on that (if you have some ;-))

[alexfauquette]

What I usually see is a localeText object:

• AGgrid
• MUI

The object can either be set globally (defined once for the entire app) or locally (defined for only one component

Its value can either be string for fixed translation. For example: { nextPage: "Page suivante" } or functions { currentPage: (pageNumber) => page numéro ${pageNumber} }

[Kout95]

i18n for lit.dev https://lit.dev/docs/localization/overview/

[Kout95]

https://crowdin.com/

[alexgarel]

Being compatible with crowdin is useful, see https://support.crowdin.com/supported-formats/