translation process before releases #3925

See this comment on https://bitcointalk.org/index.php?topic=522014.msg5797051#msg5797051.

Even the german translation contains some untranslated strings and I'm always trying to keep all strings translated. Any ideas, how we could give that translation process/handling the priority it needs? It feels really ugly and unsatisfying for translators AND users to observe untranslated strings in releases.

Could we add the translation update as automatic process into the gitian build process so that we don't need to keep the translation files here on Github perhaps? Everytime a build is done fetch current TX translations...

Any ideas, how we could give that translation process/handling the priority it needs?

It'd be possible to automatically submit transifex pulls bi-weekly in a cron script, for example, so if anyone feels like doing a bit of scripting...

Could we add the translation update as automatic process into the gitian build process so that we don't need to keep the translation files here on Github perhaps? Everytime a build is done fetch current TX translations...

That would defeat the purpose. A deterministic process cannot rely on third-party websites.

AFAIK this is fixed by having branch translations now and a much better process for importing new and changed translations. Going to close.