Keeping translations up to date

[systimotic]

We don't really have a way of tracking if issues are up to date. If the English translation in the core gets updated, the only way to get the translations updated here is... There isn't any, really.

I propose: ... Two branches, one Master and one 0.9 dev. Translations inside corresponding to the version for Anchor. In every translation is a text file, naming contributors, for which Anchor version, date it was last updated, and maybe more. In the root is also a text file like it, telling when the core of this version was last updated, maybe even where, for easy updating of the translations. This file is always up to date, being updated by the person that merged the pull-request that needed a translations update in the core.

I think this is a good idea, making Anchor translations of a higher quality, without requiring a lot of work. Let me know what you think.

[daviddarnes]

Wow, this issue is a year old. Sorry it's taken so long for anyone to reply. We need to get this repo up to scratch before we do anything else I think.

[systimotic]

Something to consider is using a tool dedicated to translations. I'm not sure if it will be the best solution for us, but maybe it will. Transifex is the only one I know of from the top of my head, and it looks like it could work for us.

[daviddarnes]

Would be good to use but we might need to simply clean up this repo to begin with before throwing additional tools on top.

[systimotic]

For sure

[alexbagirov]

There is a useful project called LingoHub which allows to translate projects from Github and automitically push language files to repository. We probably can organize it and automate the whole process.

[JacobCZ]

+1 for LingoHub

[ghost]

yeah let's do that

[JacobCZ]

@idiot please let me know in this thread or by email when it's set up so I can get back to it, thanks.