HThuren

Right, we have the setup now, what do you think are next step ? I can mark missing, but who will make the doc files (there are many of them...

Ready to go ! @haslinghuis @blckmn @McGiverGim

> Can you look at https://github.com/prusa3d/Prusa-Firmware/blob/MK3/Firmware/language.h and related tooling (https://github.com/prusa3d/Prusa-Firmware/tree/MK3/lang)? It seems considerably less intrusive for programmers Insteresting setup in prusa, but I believe we will use Crowdin, as already...

My first idea, are to use the crowdin XML to write the language apporiate bf_locale.h, ie. traverse with search in XML for specific key and from here generate the defines.

I'm not sure about next step here, merge this and build update by crowdin scripts in another PR ?

@haslinghuis before a new rebase arise, can you merge this PR ?

> My personal opinion is that this change is too intrusive and will add too much on developers side. Adapting gettext is feasible alternative, with existing, time-proven tooling. It will...

> @HThuren: Let other developers decide.. > > Did you look at https://github.com/ledvinap/bf_gettext ? It makes Crowdin integration easy (.po files are supported) and it has zero overhead (`_("English")` is...

@hydra, right, in fact, this is why I don't from start wasn't fancy about marcos from outside, or crowdin. But there are a strong opnion to use crowdin, and I...

@MedlinDrone, you don't have to change language other than *en* since Crowin will add to the other languages.