Description
There are two major tools for managing the localized files for Google Play: Fastlane Supply and Triple-T Gradle Play Publisher. F-Droid also supports the same file/dir structure. If Weblate would directly support those files, then there would be a clean, simple, automated way to translate Android apps using Weblate. Here's the ideal workflow:
- Weblate pulls source from git
- translators work in Weblate
- translations get pulled into app's source directly where Fastlane or Triple-T expect them
- F-Droid automatically uses those translations from git
- those translations are directly published to Google Play via the respective tool (Fastlane Supply or Gradle)
Both Fastlane and Triple-T use plain text for the source and translation file format. title and short_description would be easy to support directly as plain text, changelog and full_description much less so:
- title: 30 char limit, one line, plain text
- short_description: 80 char limit, one line, plain text
- full_description: 4000 char limit, multiple lines, can contain basic HTML
- changelog: 500 char limit, multiple lines, plain text
But perhaps this setup is just too different from standard translation workflows that assume strings are in a single source file. I've also opened issues on those tools to get feedback there:
- Improve support for 3P translation tools Triple-T/gradle-play-publisher#227
- integrating with Continuous Translation tools like Weblate, Transifex, etc. fastlane/fastlane#9520
I really want to find a way to get this workflow working really smoothly. Translations are really important, and something that really should be as automated as possible.