-
-
Notifications
You must be signed in to change notification settings - Fork 736
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
ICU-22325 Integrate CLDR release-44-m1 to ICU #2530
ICU-22325 Integrate CLDR release-44-m1 to ICU #2530
Conversation
/azp run CI-Exhaustive |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Too big to review, and looks to be all mechanically generated anyway. Rubber-stamping.
Suggestion for future integration pull requests:
|
What is “unit of pressure: gasoline-equivalent”? |
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.
rslgtm2 after spot check
but that new unit seems fishy
@macchiati is the best person to answer that. It may be a pressure dimensionally even though it is not used for pressure measurements. |
I think you found a problem, Markus!
It is ~33.705 kilowatt-hours, so the base unit should be watt-seconds.
Since watt is "*kilogram-square-meter-per-cubic-second*" it should
be kilogram-square-meter-per-*square*-second which is joules, not pascals.
…On Fri, Jul 21, 2023, 15:48 Peter Edberg ***@***.***> wrote:
What is “unit of pressure: gasoline-equivalent”?
I know of mpge
<https://en.wikipedia.org/wiki/Miles_per_gallon_gasoline_equivalent> but
that's a energy consumption unit, not a pressure unit.
@macchiati <https://github.com/macchiati> is the best person to answer
that. It may be a pressure dimensionally even though it is not used for
pressure measurements.
—
Reply to this email directly, view it on GitHub
<#2530 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJLEMA5JE5FWPREAWX3U3TXRMBKBANCNFSM6AAAAAA2SDF6U4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
3c86935
to
ab86739
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
/azp run CI-Exhaustive |
Commenter does not have sufficient privileges for PR 2530 in repo unicode-org/icu |
/azp run CI-Exhaustive |
Azure Pipelines successfully started running 1 pipeline(s). |
@macchiati Can you file a CLDR ticket to fix gasoline-equivalent on the CLDR side? That should be fixed with a future CLDR-ICU integration for the current integration we will use the existing category. |
Will do. |
Hi,
https://unicode-org.atlassian.net/browse/CLDR-15296?focusedCommentId=170939
is not yet closed, so will make a PR for that right away.
…On Wed, Jul 26, 2023 at 1:49 PM Peter Edberg ***@***.***> wrote:
I think you found a problem, Markus! It is ~33.705 kilowatt-hours, so the
base unit should be watt-seconds. Since watt is "
*kilogram-square-meter-per-cubic-second*" it should be
kilogram-square-meter-per-*square*-second which is joules, not pascals.
@macchiati <https://github.com/macchiati> Can you file a CLDR ticket to
fix gasoline-equivalent on the CLDR side? That should be fixed with a
future CLDR-ICU integration for the current integration we will use the
existing category.
—
Reply to this email directly, view it on GitHub
<#2530 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJLEMHG4KTN4OHS3UFJ2IDXSF7FZANCNFSM6AAAAAA2SDF6U4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
After investigating and writing some tests, I realized that the quantity
was correct (because it simply represents the most common usage of the base
unit). I also documented why the unit seems so odd.
description="Constructed so that 1 gallon-gasoline-equivalent = 33.705 kWh
as per https://www3.epa.gov/otaq/gvg/learn-more-technology.htm"
unicode-org/cldr#3121
…On Wed, Jul 26, 2023 at 4:31 PM Mark Davis Ⓤ ***@***.***> wrote:
Hi,
https://unicode-org.atlassian.net/browse/CLDR-15296?focusedCommentId=170939
is not yet closed, so will make a PR for that right away.
On Wed, Jul 26, 2023 at 1:49 PM Peter Edberg ***@***.***>
wrote:
> I think you found a problem, Markus! It is ~33.705 kilowatt-hours, so the
> base unit should be watt-seconds. Since watt is "
> *kilogram-square-meter-per-cubic-second*" it should be
> kilogram-square-meter-per-*square*-second which is joules, not pascals.
>
> @macchiati <https://github.com/macchiati> Can you file a CLDR ticket to
> fix gasoline-equivalent on the CLDR side? That should be fixed with a
> future CLDR-ICU integration for the current integration we will use the
> existing category.
>
> —
> Reply to this email directly, view it on GitHub
> <#2530 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ACJLEMHG4KTN4OHS3UFJ2IDXSF7FZANCNFSM6AAAAAA2SDF6U4>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
dfb4033
to
123e0de
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
123e0de
to
340ce7c
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
/azp run CI-Exhaustive |
Azure Pipelines successfully started running 1 pipeline(s). |
55bdec8
to
d23d741
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
/azp run CI-Exhaustive |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
I spot-checked the data files. Markus and Rich would be better suited to check the rest.
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.
Either I forgot to actually rubber-stamp this the first time around, or my stamp got removed by activity in here in the meantime. Rubber-stamping again.
7c4af1f
to
9500fa4
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
/azp run CI-Exhaustive |
Azure Pipelines successfully started running 1 pipeline(s). |
@richgillam Well I needed to update this again to add a copyright for the personName testdata files (currently most of them say they are for unit tests, known issue that I will fix in CLDR). But this will need another look, sorry. |
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.
Still looks good. Huge thanks (and deep apologies) for the PersonName changes!
String[] FILENAMES_TO_SKIP = {"gaa.txt", "dsb.txt", "syr.txt", "hsb.txt", "lij.txt", | ||
"yue_Hans.txt", "fa.txt", "ja.txt", "ka.txt", "zh_Hant_HK.txt", "zh_Hant.txt", | ||
"bn.txt", "zh.txt", "nl.txt", "to.txt", "uk.txt", "my.txt", "yue.txt", | ||
"bg.txt", "tk.txt", "ps.txt", "ko.txt", "kk.txt", "ms.txt"}; |
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.
Thanks; I'll try to fix this after I get the algorithms back in sync and Mark regenerates the test data files (or I figure out how to do it).
// { "nl_NL", "LONG", "MONOGRAM", "FORMAL", "DEFAULT", "", "WvP" }, Temporary change the test because data was set to provisional | ||
// { "nl_NL", "LONG", "MONOGRAM", "INFORMAL", "DEFAULT", "", "WvP" }, | ||
{ "nl_NL", "LONG", "MONOGRAM", "FORMAL", "DEFAULT", "", "WV" }, | ||
{ "nl_NL", "LONG", "MONOGRAM", "INFORMAL", "DEFAULT", "", "WV" }, |
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.
Sounds like I have some cleanup and sync to do here too...
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.
NO, this is because we reset a lot of personName data to provisional before the beginning of data collection for CLDR 44; provisional data dopes not get picked up for ICU. Once we have the CLDR 44 Survey Tool data in xml and redo the integration, these problems should go away.
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.
Oh, okay.
@@ -556,7 +558,8 @@ public void TestLocaleDerivation() { | |||
{"en", "MEDIUM", "REFERRING", "FORMAL", "DEFAULT", "", "陳港生Test"}, | |||
}), | |||
new NameAndTestCases("given=港生,surname=陳,given2=Test,locale=zh_Hant", new String[][]{ | |||
{"en", "MEDIUM", "REFERRING", "FORMAL", "DEFAULT", "", "陳港生T."}, | |||
// {"en", "MEDIUM", "REFERRING", "FORMAL", "DEFAULT", "", "陳港生T."}, Temporary change the test because data was set to provisional | |||
{"en", "MEDIUM", "REFERRING", "FORMAL", "DEFAULT", "", "陳港生Test"}, |
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.
And here...
@richgillam No problem. But can you re-approve? All of the updates to this PR cancelled the previous approvals. |
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.
Approving again.
Done. Thank you! Was my response to Frank in https://unicode-org.atlassian.net/browse/ICU-22304 accurate? If not, would you mind commenting over there? If so, I'll close it again after this PR lands. |
@richgillam @markusicu @macchiati We have had some updates to this PR to get exhaustive tests to pass. Can one of you re-approve? Thanks! |
I did re-approve. I think you're okay (at least it looks like it on my side...). |
Yes, that is accurate... |
Checklist
Integrates CLDR release-44-m1 plus the fix for ko_CN in unicode-org/cldr#3107 and the fix for personName test data in unicode-org/cldr#3122.
Some tests results are temporarily changed because CLDR reverted some data items to provisional at the beginning of the submission cycle (these will be fixed with the alpha0 integration).
Fixed pre-existing bug in RBBITestMonkey and logged a known issue for problem with testing limits on Hebrew calendar ICU-22441
Also needed to add personName test data from CLDR per
ant copy-cldr-testdata
intools/cldr
. Had to add a copyright header for those files in CLDR (currently a known issue with most of them saying they are for unit tests, will fix in CLDR). This also entailed changing the tools/cldr/build.xml code to add a copyright header for the generated catalog.txt file.