Feature request: Use GitLocalize for translations

[BDVGitHub]

Is your feature request related to a problem? Please describe.
Now it is difficult for a novice to contribute to translations. Therefore, it could possibly be useful to use GitLocalize so that people can contribute to translations in an easy way.

Describe the solution you'd like
Using GitLocalize to get people to contribute to translations in a relatively simple way.
GitLocalize supports json files, all you have to do is keep one file as an example file, preferably a language that many people can handle. When adding text, for instance, you can easily see which text is missing from the other languages.
GitLocalize needs to be granted access to the repo so pull requests can be created to add or update a translation. GitLocalize also checks at regular intervals whether the main translation file has been updated or not.

https://gitlocalize.com/

Describe alternatives you've considered
Weblate seems overkill to me
https://weblate.org

Additional context

[BJReplay]

Thanks for the suggestion. I was thinking about how to improve translation support, as well as other approaches that use community sourcing.

Definitely something to look into!

[autoSteve]

Totally worth looking into. Converted into a discussion for tracking.

[BJReplay]

@autoSteve I've just set this up to test it out, and I think it works...

integration_prior_crash doesn't exist in es.json :)

Now, I've sort of bodged the set up - I've just been playing, and started (incorrectly, perhaps), with en as the source language, rather than strings.json as the source language, but it shows this at first set up:

Here's the link - I don't know what you see when you click on it: https://gitlocalize.com/repo/10620.

If you sign into GitLocalize at least once, I can invite you (and anyone else, for that matter).

[autoSteve]

I'm in.

[BJReplay]

I've broken it. Starting over...

[BJReplay]

OK, started over: https://gitlocalize.com/repo/10621

Now set up properly, I think:

Source is strings.json

Target is translation directory:

English-UK is set up as a target language (and is recognised as 100% synced).

If you are willing to live with the crunched spacing, accepting those PRs will bring the other languages into sync.

That then means that you could just maintain strings in source, and all languages in GitLocalise, and we could crowdsource both additional languages, as well as readme and other translations.