Transifex automation and file depenent mappings don't work together

[EmmanuelMess]

There is an interesting issue with translations, the yml configuration doesn't allow for specific mappings (that we need to support Fastlane and Android translations) but does allow for smooth integration (automatic pull/push of translations). The .tx/config has file specific mappings but no direct support for integration.
So,

• To use ".tx/config": We have to create/obtain a CI pipeline that will integrate GitHub and Transifex
• To use "yml": We need to find a way to use the same mapping for both android and Fastlane

Ping @yurtpage @IzzySoft hoping there is an easier way out.

References:
https://community.transifex.com/t/using-tx-config-with-github-integration/5152/6
https://help.transifex.com/en/collections/5049978-github
https://developers.transifex.com/docs/cli
https://developer.android.com/guide/topics/resources/providing-resources

[yurtpage]

This is the basic thing that they should handle themselves but they didn't for years.

Let's just use the Weblate instead https://toolate.othing.xyz/projects/amazefilemanager/
I created and configured the translation project. The Weblate will send a PR on translation changes. You probably want to pull manually so let me know and I'll disable the PR sending. If also will reformat the strings.xml so the first PR will be hard to understand but all next will be fine.
If you wish I'll send you an invitation to become an admin of the project (needed sometimes to resolve merge conflicts).

The Weblate isn't ideal but it's better that Transifex in all aspects.
The Tx already eaten a lot of our time and messed with files #4534 so that translators had to re-translate completely from scratch.

[IzzySoft]

For a little while now, Weblate even gives you the means to enforce specifications (here: string lengths – e.g. max 80 chars for shortdesc, 4000 for fulldesc, 500 for per-release changelogs). If you need a quick guide for that, see e.g. Crazy-Marvin/VacationDays#309 (comment)

[yurtpage]

@IzzySoft the Weblate already shows alerts if a string is larger than it should be. It still can be submitted by a translator but this should happens rarely and others will fix it. An app store will just truncate.

[IzzySoft]

@yurtpage "shows" was the "old standard", where translators could still ignore it. Sylvia's PR introduced to make sure it cannot be ignored, but is a "hard setting".

Yes, our tooling would truncate it if it were still submitted. But it would also raise alerts with our monthly quality check (yes, we take care for quality here) – especially as the truncation might not only make it shorter, but also lead to a different meaning (made up example: "this is a tool to make image[s disappear]" – quite confusing if the term in brackets were truncated, no?). So it should better be ensured this situation does not come up in the first place.

[yurtpage]

ok, then let's wait when the Weblate team fix this and the Toolate server will be updated.

@EmmanuelMess if you fine with using the Toolate then I'll send a PR with to the README with a link