Open OscarBeiro opened 4 years ago
The current approach by Weblate is that everything gets committed to Git. This way people working on Git have same view as Weblate it works without any problems to work on the translations in both Weblate and Git. Delaying committing some files would break this assumption. Another reason is that this reduces vendor lock-in - the translations main source is the Git repository, not Weblate.
I bet there is way to filter available languages in Android as that's what I'd expect from most apps...
This issue has been put aside. Currently, it is unclear whether it will be ever implemented as it seems to cover too narrow use case or doesn't seem to fit into Weblate. Please try to clarify the use case or consider proposing something more generic to make it useful to more users.
This is also an issue for the F-Droid client app. We currently have a complex process with lengthy python scripts to exclude incomplete translations which is very painful.
I get the part about everything being in git. However, maybe there's a way that for example when making merge/pull requests those are made from a branch that only includes the complete translations.
I bet there is way to filter available languages in Android as that's what I'd expect from most apps...
As far as I know, Android will look into translation directories to find a matching translation. I can exclude the translation from showing up in the "Set language manually" preference, however that won't prevent users which have this language as their main Android language to use it.
Maybe .gitignore could be used to add those files until they meet the required translation limit.
I get the part about everything being in git. However, maybe there's a way that for example when making merge/pull requests those are made from a branch that only includes the complete translations.
Could one of these solutions fit? Or maybe add a way to commit incomplete translations to a separate directory on Git such as .weblate/ if a different branch is not appropriate?
At least, not making a commit if there is nothing in it could be a good start? Some people add new languages but they don't translate anything :/
In another discussion, I explained how I would see this feature with a special case for existing translations below threshold:
We've just moved https://github.com/AntennaPod/AntennaPod app translations from Transifex to Weblate (in addition to the website translations which were already on Weblate). On Transifex we had set a threshold of 40% for app translations.
I get the part about everything being in git. However, maybe there's a way that for example when making merge/pull requests those are made from a branch that only includes the complete translations.
We would support an approach like this - our intention is to have Weblate create PRs from https://hosted.weblate.org/git/antennapod/app/ to https://github.com/AntennaPod/AntennaPod/tree/develop. If we could set the threshold for these PRs, that'd be great :-)
Is your feature request related to a problem? Please describe. We are developing an Android App, and we are thrilled with our recent Weblate integration to manage translations, however, when a new translation language is started, and the percentage of strings translated is low, the app doesn't look right.
Describe the solution you'd like A threshold that could be configured in order to meet a minimum percentage of translation before it was pushed from Weblate GIT to VCS repository. It could be per Project or per Component.
For instance, if we set minimum valid translation to 60%, no language files with less than 60% of strings translated will be pushed to our repository.
Maybe .gitignore could be used to add those files until they meet the required translation limit.
Thanks