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.
With the recent changes to only export English strings, we unfortunately broke the one place (that I could find) in our i18n code in which we are using an array of data; in the case of (for example) ar-SA, we were actually returning a value like:
(Note that this was only a problem for languages that had the races list partially translated; for languages that translated the whole thing we were obviously fine, and for languages that had none of them translated, the entire array fell back to English)
So instead, we convert this array into a hash and use a code constant to handle the iteration, so we're just looking up individual keys and the English fallback should now work fine:
I also cleaned up the i18n source and translation files with a simple sed script, and will do an i18n sync with these changes to make sure the translation data coming out of that is also correct.