icerockdev
Add option to fill in missing string translations with base translation
The issue here is what is the fallback behavior if a string does not have a translation. This happens for us because our translation department follows a weekly cadence of updating translations.
For Android it is not an issue. If a translation is missing it just falls back and supplies the base string. For iOS however, it does not fall back to the base string, it falls back to the actual key name. This can have some very weird behavior if for example the string represents a date format.
So I would like a way to tell moko resources to use the base translation if the translation is missing, not the string key. I would turn this on for development. We have a task that will fail release builds for missing translations
Hello, I still encounter this issue to this day. Can we please get some updates regarding the possibility of adding a solution in the future?
This has also been problematic for our app. We're not guaranteed to have all of our translations before any given release, so the iOS app could be showing the key name for any string instead of a reasonable fallback.
Somewhat related, we accidentally had an invalid escape sequence in the translations for German (it was a \") which resulted in none of the German translations making it into the app so in German every string was coming out as the key.
I'd also really appreciate if this feature could be added.
If the translation is driven by volunteers from the community, the translation for each language is never finished in time, so there are lots of new texts in each release that should at least default to the text from the base locale instead of showing the key, which no user can make any sense of.
