New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support Google Play upload tools: Fastlane and Triple-T Gradle Play Publisher #1525

Open
eighthave opened this Issue Jun 19, 2017 · 6 comments

Comments

4 participants
@eighthave
Copy link

eighthave commented Jun 19, 2017

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:

  1. Weblate pulls source from git
  2. translators work in Weblate
  3. translations get pulled into app's source directly where Fastlane or Triple-T expect them
  4. F-Droid automatically uses those translations from git
  5. 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:

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.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@eighthave

This comment has been minimized.

Copy link

eighthave commented Jun 19, 2017

Here's one hard part of this whole setup: the hard character limits for full_description and changelog. So 4000 and 500 chars are pretty big blocks of text for a single translation string. But I haven't found a way to set a character limit for a group of strings, only for a single string.

@azachar

This comment has been minimized.

Copy link

azachar commented Feb 17, 2018

Hello, is here any progress?

@nijel

This comment has been minimized.

Copy link
Member

nijel commented Feb 20, 2018

AFAIK nobody is working on this right now.

@eighthave

This comment has been minimized.

Copy link

eighthave commented Feb 20, 2018

@PanderMusubi

This comment has been minimized.

Copy link

PanderMusubi commented Oct 17, 2018

Any luck with that grant proposal?

@eighthave

This comment has been minimized.

Copy link

eighthave commented Oct 17, 2018

yeah, I got a small grant to work on this, so I should be able to get
something done.

@nijel nijel added this to To do in Linguine Oct 17, 2018

@nijel nijel self-assigned this Nov 11, 2018

@nijel nijel moved this from To do to In progress in Linguine Nov 11, 2018

@nijel nijel referenced this issue Nov 12, 2018

Merged

File formats cleanup #2379

4 of 4 tasks complete

@nijel nijel moved this from TODO to In progress in File format support Nov 12, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment