-
Notifications
You must be signed in to change notification settings - Fork 398
CLDR-18531 Add long Hawaii time name, remove short names #4717
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
base: main
Are you sure you want to change the base?
Conversation
Isn't this supposed to be an alt? |
I don't think so. it's supposed to be an override of the non-location (metazone) name. |
What does this mean:
|
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
do you know why CI fails? |
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
I think you might be running into a problem (that I filed a ticket on ages ago) than if there is no daylight savings, then the 'standard' version is used, not generic. I'd have to look to the spec to see what the fallback is. If we fallback to whichever exists, then we should fix the test. But it may cause an ICU migration issue too. |
|
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
The only error appears to be the following: Error: (TestCoverageLevel.java:737) Error: Comprehensive & no exception for path => //ldml/dates/timeZoneNames/zone[@type="Pacific/Honolulu"]/long/standard I poked into a bit, but have a doctor's appointment, so have to get back to it later. Here's what I find: That test is checking the coverage for English, and found that that path is at Comprehensive, instead of modern. Searching in coverageLevels.xml, for timeZoneNames/zone in HEAD main/en.xml, I find just one applicable line.
Using SearchXML on en.xml I get:
I need to look back at the test and find out why the short/standard is not triggering a problem while the long one is. |
What does that mean? The path is either there or not there in English. |
Getting back to this. This should probably wait until survey tool XML integration. Otherwise importing the data from XML might restore items. However, in answer to your question: A path can either be physically present in a locale, or inherited from a parent (eg for en that's root), or absent. In any of those cases, the coverage level determines what is actually shown to users. The test in question verifies that for a known locale (English) there are certain paths, and the coverage levels for those paths make sense. In the note I had above, we have the following paths at comprehensive (in main), but I think it might be checking for the long versions and failing.
|
So what do I have to change? |
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.
Looks good, just not approving until we are in XML
CLDR-18531
Also removes short "HT" from all locales that somehow translated it, short names should only be in
en-US
.ALLOW_MANY_COMMITS=true