[Feature Request] i18n

[bcourtel]

It may be interesting to bundle a bunch of translation files for commonly used terms (ie. the labels of buttons).

There are a few questions to answer before starting the implementation:

• [ ] which kind of architecture to use? Ideally it should be something relying on as few dependencies as possible as to not make the final bundle size a problem for library users
• [ ] is it possible to integrate with a crowdsourced translation service like Transifex? This would allow non-coders to help with the translation
• [ ] how to make it easily overridable by library users?

[WebMechanic]

@bcourtel is this still relevant for you? did you compile alist of places where the GUI needs translation? I only use a few components so far. I might eventually run into the issue of having a multi-lingual GUI. I'd be happy to help with a common proposal that does not involve having to install some arbitrary l10n/i18n package. I do have a favourite, but it's none of the "obvious" choices, 'cos neither would satisfy the linguistic needs I have for a certain language teaching tool.