i18n

[joyshmitz]

internationalization is provided, if so, how to carry it out correctly?

[nhoening]

Not provided yet, but a great idea to do, of course!

I'm assuming you are referring to the UI right?

It is pretty straightforward, using Flask-Babel, explained here or here.

After getting Flask-Babel to work, the bigger part of the work is to go through templates and views, and replacing text with a translation function. Also, we'd like to have a language switcher in the menu.

Then, creating translations. Which language would you like to add? We would like to add Dutch and German.

[joyshmitz]

That's right, UI Thanks for the tip, I'll try Flask With Dutch and German using a translator, and I think that the technical editor is extremely important, to convey the nuances of the application, і will translate into Ukrainian and Russian

[nhoening]

Awesome, if you open a PR I will help you along the way.

I speak German and Dutch very well, so I will provide those translations.

[joyshmitz]

ok It will take some time, and I plan on i18n and l10n, right?

[nhoening]

Sounds good. l10n really is the smaller part here, making a good guess at the user's preferred language from their browser settings, right?

We can add a language selector in a different PR.

[nhoening]

As I said, don't hesitate asking me to help/review on the way!

[joyshmitz]

Sounds good. l10n really is the smaller part here, making a good guess at the user's preferred language from their browser settings, right?

what about cli?

[nhoening]

My first thought is that the audience for UI and CLI is maybe not the same, but maybe I'm not correct. I can imagine there might be engineers working with FlexMeasures who are not good at English and are using the CLI.

There is a lot of command documentation in there, so longer strings.

Maybe do one thing after another, and plan CLI for another PR?

There is also the FlexMeasures documentation, but there I'd definitely stop :)

[joyshmitz]

You are right, there is no limit to perfection,

so, one piece at a time

[nhoening]

@joyshmitz Is this still relevant for your side?

[joyshmitz]

@nhoening yes, it's time to find reasons why not to do it, the opportunity will appear on April 10. Nothing has changed since then?

[nhoening]

Great to hear. Nothing has changed. In #579 I upgraded dependencies, also babel is at the latest version.

[nhoening]

We listed a few things here which could use translation, and decided to do others in other PRs. To that I'd add emails. There are not many, mostly around account setup (e.g. password change) and monitoring. Once work starts here, I'll make a Github project so we can start tracking all of these and discuss which are actually needed.