-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Transifex: use .tx/config instead of the transifex.yml #4421
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
Conversation
EmmanuelMess
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to check that the file will link correctly the already translated resources.
|
To avoid loss of any existing translations it would be great to pull them first and then merge the PR. |
This would be blocked by #4416 then |
|
Friendly remind on this |
|
It is a good idea to test with #4416 first though |
|
I've rebased to the base branch and removed wrong luri mapping. |
|
Thank you |
Replaces #4417
I don't know what's a difference between the
transifex.ymland the.tx/configbut at least it clearly supports thelang_map.Here is docs: https://developers.transifex.com/docs/using-the-client
Additionally I sorted the lang codes. But in the https://github.com/equeim/tremotesf-android/blob/master/.tx/config there are more mappings so we can merge them and it will result in a bigger list:
But this may affect existing
values-*folders: https://github.com/TeamAmaze/AmazeFileManager/tree/release/4.0/app/src/main/res