-
-
Notifications
You must be signed in to change notification settings - Fork 49
Handle Chinese autonyms explicitly in IetfLanguageTag #1475
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
Conversation
This fixes a bug reported in Bloom (BL-15436)
Palaso Tests 4 files ±0 4 suites ±0 10m 26s ⏱️ +19s Results for commit 02628e5. ± Comparison against base commit dce7400. This pull request skips 1 test. |
imnasnainaec
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@imnasnainaec reviewed 1 of 2 files at r1, all commit messages.
Reviewable status: 1 of 2 files reviewed, 1 unresolved discussion
SIL.WritingSystems/IetfLanguageTag.cs line 1328 at r1 (raw file):
{ return kTraditionalChineseAutonym; }
What about the (generalCode == ChineseSimplifiedTag && uiLanguageTag == ChineseTraditionalTag) and (generalCode == ChineseTraditionalTag && uiLanguageTag == ChineseSimplifiedTag) cases?
StephenMcConnel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: 1 of 2 files reviewed, 1 unresolved discussion (waiting on @imnasnainaec)
SIL.WritingSystems/IetfLanguageTag.cs line 1328 at r1 (raw file):
Previously, imnasnainaec (D. Ror.) wrote…
What about the
(generalCode == ChineseSimplifiedTag && uiLanguageTag == ChineseTraditionalTag)and(generalCode == ChineseTraditionalTag && uiLanguageTag == ChineseSimplifiedTag)cases?
I have no idea what the logograms would be in the mixed code situations that you describe. That's why I stuck to the pure autonym assignments. If you know that the logograms would be the same regardless of the specific uiLanguageTag, I'd be happy to change the code.
imnasnainaec
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: 1 of 2 files reviewed, 1 unresolved discussion (waiting on @StephenMcConnel)
SIL.WritingSystems/IetfLanguageTag.cs line 1328 at r1 (raw file):
Previously, StephenMcConnel (Steve McConnel) wrote…
I have no idea what the logograms would be in the mixed code situations that you describe. That's why I stuck to the pure autonym assignments. If you know that the logograms would be the same regardless of the specific uiLanguageTag, I'd be happy to change the code.
I just noticed that GetLanguagePart will return zh and neither ChineseSimplifiedTag nor ChineseTraditionalTag, so the two new cases are currently never met.
I think it would be safe to go with
else if (generalCode == ChineseSimplifiedTag && uiLanguageTag == "zh")
{
// Chinese autonyms are also messed up in various ways, so we hard-code them here.
return kSimplifiedChineseAutonym;
}
else if (generalCode == ChineseTraditionalTag && uiLanguageTag == "zh")
{
return kTraditionalChineseAutonym;
}
|
I've decided to let Noel fix this problem since she has a better grasp on the issues. |
|
Replaced with #1477 |
This fixes a bug reported in Bloom (BL-15436)
This change is