Translate all components

[jscheffl]

Translate all components in the UI

Uff... sorry this is a large one :-(

related: #50861

[shahar1]

Great job!
Before merging, we probably want to merge #51269 first to avoid inconsistencies between existing translations. Also, I think it's worth thinking of a policy of how we manage changes regarding language files. I'll raise a discussion about it in the dev list.

cc: @potiuk

[potiuk]

Before merging, we probably want to merge #51269 first to avoid inconsistencies between existing translations. Also, I think it's worth thinking of a policy of how we manage changes regarding language files. I'll raise a discussion about it in the dev

No need to wait - the script for now is just flagging the differences but it's not (and should not be) run as pre-commit - because we need to sort out the process of updating the translation. I can't imagine the one who adds a new string is also adding translations for all the unfamiliar languages. That is one of the challenges of the i18n that we need to solve that whatever change in structure or new string we add, we should also figure out how we are doing it for all translations - @jscheffl implemented it all for German and English, but now other languages will need to catch up and we need to figure out how to make it happen.

that's why the script is for now just runnable - but it's not run as pre-commit and individual authors might run it to fix things for example: #51271

But there is no "hard" dependency between these.

[jscheffl]

the script for now is just flagging the differences but it's not (and should not be) run as pre-commit - because we need to sort out the process of updating the translation. I can't imagine the one who adds a new string is also adding translations for all the unfamiliar languages. That is one of the challenges of the i18n that we need to solve that whatever change in structure or new string we add, we should also figure out how we are doing it for all translations - @jscheffl implemented it all for German and English, but now other languages will need to catch up and we need to figure out how to make it happen.

that's why the script is for now just runnable - but it's not run as pre-commit and individual authors might run it to fix things for example: #51271

But there is no "hard" depende

Agree. I just added the new German stuff to check the translation outcome. And there are other German gaps also but I'd add them in a different PR.

[TJaniF]

Few suggestions on the German parts :)

[jscheffl]

Few suggestions on the German parts :)

Thanks for the review. Amoungst too many changes it seems I need to get a new keyboard where the letter "e" is typed when I press - it seems in a couple of cases the "e" was just missed...

[pierrejeambrun]

Nice, thanks for the PR.

I feel like it remains plenty of other places untranslated, still with the english fallback. A couple of example in the drop down bellow. Also you can run eslint to see where we are still using string literal:

yarn lint

Carefull, dynamic labels and stuff coming from js variable do not seem do be detected. So there might be more to fix.

More than a 100 occurences still remain like this:

[jscheffl]

Nice, thanks for the PR.

I feel like it remains plenty of other places untranslated, still with the english fallback. A couple of example in the drop down bellow. Also you can run eslint to see where we are still using string literal:

I think this is a mis-understanding :-D I was not intending to translate ALL leftovers in the UI (and there are plenty left!) but attempted to translate all "UI components" (modular things that are in the "components" subfolder.
I am sure there is plenty room for next PRs but all at the same time would be crazy complex. (=merge conflict generator)

That also means there are not all parts of the UI, especially "pages" translated. Also some TS files have terms as enums and lists which need some separate efforts.

[pierrejeambrun]

Ah got it! Thanks