Help with new translations
LivingWithHippos opened this issue · 7 comments
Use a service such as Crowdin or Weblate to let contributors add their own translation to the project.
Using the platform is not strictly required, it is also possible to just fork the project, clone and switch to the dev branch, create a new branch and create a new strings.xml file under a values-LANGUAGE_CODE folder like it was done for this one and open a PR to merge it.
Official docs on localization:
Why create a new branch?
Ah that's right it is not necessary since you just fork it. I was thinking about more complex issues where it could be helpful.
It's probably done so it can be understood immediately what is being asked to be merged. Seeing a new-language-spanish branch is better than seeing a dev branch
The translation app has been put on hold while I fix some issues
Crowdin support has been added but there is a last bug that needs to be solved
https://community.crowdin.com/t/android-translation-of-plurals-changes-attribute-and-fails-ci/3013
The timeline is Q1 2023, in the meanwhile strings can be translated "manually" by just editing the corresponding strings.xml file, no need to install any software (a text editor with xml support will make this easier, see notepad++, jetbrains fleet, vscode, sublime text editor...). Ask here if you need any help setting it up
todo:
- reset crowdin when ready
- remove/update shield on readme when crowdin is enabled