Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Work around a currency service defect for localization #2302

Merged
merged 2 commits into from
Feb 21, 2025

Conversation

tian-lt
Copy link
Contributor

@tian-lt tian-lt commented Feb 21, 2025

What

The currency service seems have changed their fallback rules for unrecognized language code about Chinese, which causes users who selected zh-Hant-TW get simplified Chinese content in the currency converter.

Fix

Regarding the standard of BCP47, manually construct a two-segment language code (e.g. zh-TW) from multi-segment language code (e.g. zh-Hant-TW) to ensure the localization service can recognize the language code and provide the correct content.

@tian-lt tian-lt changed the title Work around a currency service regression for localization Work around a currency service defect for localization Feb 21, 2025
@tian-lt tian-lt merged commit 9d6d6be into microsoft:main Feb 21, 2025
5 checks passed
@tian-lt tian-lt deleted the fixcurr branch February 21, 2025 08:53
tian-lt added a commit to tian-lt/calculator that referenced this pull request Feb 21, 2025
* always use `lang-region` for localization

* language code may have a single segment
tian-lt added a commit that referenced this pull request Feb 21, 2025
* always use `lang-region` for localization

* language code may have a single segment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants