i18n: Lookup untranslated strings from a fallback language (english) instead of displaying Unknown...
#2637
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is being done to unblock adding partial translations to the game. In the code's current state, we cannot add partial translations because it makes the UX basically unusable, with everything being labelled as Unknown. At the same time, it isn't really a good workflow to require 100% completion, and we should be providing a path that allows for continuous iteration.
So this change is rather simple, load the english (language 0) text file as a fallback. If we cannot find something in a
lookup-text!call, try to look it up in english as well.Tests: