Try and improve the translation situation #960
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There a few issues with Monerujo maintenance issues.
A handful of strings are outdated; the source string was modified but the translation was never removed; this is where we get inconsistent strings that can only be corrected if the translators goes through every string, which is even harder since monerujo is not on something like Weblate as a translation platform #958 !
Newly added strings are added into the translation files because monerujo does not ignore the linter flag "MissingTranslation", because monerujo does crowd-sourced translation, this flag doesn't make sense to keep enabled! These english strings also mean can also affect how Android deals with fallbacks, e.g. when there are strings for PT available that could be used but the user is using PT-BR
This PR should help with integrating with #958 as a possibility in the future and it is its main focus
It is important to note, ideally when source strings are changed or removed, they are also altered in translations, so they don't take effect in the app anymore. This makes translators' jobs easier.