Fallback to using variations of language code, script, and region for unknown Locale
(ex: zh_CN
will look for zh_Hans
)
#4870
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.
Motivation
Fixes #4829
Description
Improves
LocaleFinder
by falling back to different variations of language code, script, and region.Previously, it would use the locale's identifier to find the matching locale in our localizations. However, this didn't work well for language codes like
zh_CN
(shorthand forzh_Hans_CK
orzh_HK
(shorthand forzh_Hant_HK
.With this change,
LocaleFinder
will now useLocale
to find the script (ex:Hans
orHant
) and region (ex:CN
orHK
). It will go in this order: