sure, putting it directly into the platform would not work out that well as time goes on. Doing the changes on a Github repository seems reasonable from a “translation maintenance” point of view. But as a developer i would wish a little more convenience for importing different languages. Would a button in studio for downloading the translations and importing it to the project be possible (either download the excel files and automatically execute the binary, or downloading directly the .properties files for the correct version of the platform and the translations)?
I think it depends a little on your preferences how tightly coupled the platform should be with the “community addons” in its public image.
From a maintenance perspective it would be cool, if changes on the keys could be communicated via the Github repository as well, so there is no hurdle to translate the deltas. I’m not even sure, how this could work, but it would increase the chance that the translation will keep up with the development. A possible thing would be to use Github Issues for this.
Do you have any glue, how other open source projects handle this issue? It seems to be a solved problem, right?
Regarding to 6.0 - well when i read what you wrote, i should have said no, right? :=) What i did was to create a test project in 6, import the translation and starting it. On the surface, everything looks good. I’ll check it in the next days in a little more detail. I’ll let you know about it.