Castopod
/
AntennaPod
mirror of https://github.com/AntennaPod/AntennaPod.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Updating Translations (markdown)

Koen Glotzbach 2016-01-17 18:40:15 +01:00
parent 666ce82a7d
commit c70d0199a4
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Updating-Translations.md

@ -53,11 +53,11 @@ A: All data ever entered for a project gets stored in the 'Translation Memory' o
Reference: [#1257 Old translated strings still available?](https://github.com/AntennaPod/AntennaPod/issues/1257) Reference: [#1257 Old translated strings still available?](https://github.com/AntennaPod/AntennaPod/issues/1257)
**Q: How to update the English (source) strings?** **Q: How to update the English (source) strings?**<br />
A: Source strings (English) are stored in [ AntennaPod/core/src/main/res/values/strings.xml A: Source strings (English) are stored in [ AntennaPod/core/src/main/res/values/strings.xml
](https://github.com/AntennaPod/AntennaPod/blob/develop/core/src/main/res/values/strings.xml); you do a Pull Request to update that file. When making changes to the source language, please use American spelling. ](https://github.com/AntennaPod/AntennaPod/blob/develop/core/src/main/res/values/strings.xml); you do a Pull Request to update that file. When making changes to the source language, please use American spelling.
**Q: Why don't you run automatic checks to approve that strings in all languages are present, before merging pull requests into the master branch?** **Q: Why don't you run automatic checks to approve that strings in all languages are present, before merging pull requests into the master branch?**<br />
A: This is simply a matter of convention; we didn't do it in the past and introducing such checks might lead to some difficulties. What to do with the information that a language is incomplete, for example? Do we halt roll-out of an update, or do we put effort in chasing volunteers? Or do we ignore the warning and just let it be? A: This is simply a matter of convention; we didn't do it in the past and introducing such checks might lead to some difficulties. What to do with the information that a language is incomplete, for example? Do we halt roll-out of an update, or do we put effort in chasing volunteers? Or do we ignore the warning and just let it be?
On the other hand, if we don't set up such checks, Android will simply use the English strings if a language lacks a translation. If there are not volunteers to translate a language or new strings, we just have to live with that. Noting of course that some kind of check [is done](https://github.com/AntennaPod/AntennaPod/commit/a8566a62233ddc1a2ebd57c92cb3dc8b23919cf8) by the developers themselves (if there's really few translations, we won't provide the few strings to the end-user). And users bumping into untranslated strings might be motivated to help out ;) On the other hand, if we don't set up such checks, Android will simply use the English strings if a language lacks a translation. If there are not volunteers to translate a language or new strings, we just have to live with that. Noting of course that some kind of check [is done](https://github.com/AntennaPod/AntennaPod/commit/a8566a62233ddc1a2ebd57c92cb3dc8b23919cf8) by the developers themselves (if there's really few translations, we won't provide the few strings to the end-user). And users bumping into untranslated strings might be motivated to help out ;)