WIP: Implement international language support

[abraunegg]

• Initial start on implementing international language support

[ghost]

Hi,
I just saw this PR, did you by chance create the german translation automatically?
I think at least the first log message sounds a bit off.
I think this sounds better:
"Keine Benutzer- oder Systemkonfigurationsdatei gefunden, es werden die Standardwerte verwendet"

[abraunegg]

@oohjio
Many thanks for looking at this PR in its very early stage of development.

This is a WIP at the moment. The DE.json is just a 'google' translate of the first few messages, so that I can ensure, when building the PR (as it is not complete), is able to provide the right 'translations' for the language being selected. I could have also used dummy text (eg 'asdfasdfasfdasfdasdf') .. but I didnt.

When this PR is ready, there will only be the EN-US.json file, with the community able to provide a language.json file, which then can be used / loaded into the application for folks to use.

Please keep an eye on this, and if you are interested in providing the DE.json when the main code changes are done, please create / update the file so that this feature can launch with accurate & correct language translations for Deutsche.

[ghost]

@abraunegg
Thanks for the reply.
I see, that makes sense,
Will keep an eye on this.

[norbusan]

Hi Alex
I just looked into this and thought wouldn't it be better to use the default msgfmt/gettext style approach, and the https://github.com/FreeSlave/mofile library? That way we could profit from normal translation environment (editors, cloud translations, ...) - just as an idea ...

[abraunegg]

@norbusan

Hi Alex
I just looked into this and thought wouldn't it be better to use the default msgfmt/gettext style approach, and the https://github.com/FreeSlave/mofile library? That way we could profit from normal translation environment (editors, cloud translations, ...) - just as an idea ...

Always happy for other ideas / alternate approaches

Looking at https://github.com/FreeSlave/mofile/blob/master/examples/ru.po - that is 'kind of' the approach currently taken - that is - key value pairs.

What I need to do, is get v2.4.13 out, then get back to finishing the PR with my current line of thinking - and see if that works, if not, happy to look at other approaches.

The approach I have (which the PR is a mess on here as compared to what I have locally) is that the translation file is separate - thus can be updated / amended by the end user, restart the application and the new translations are used.