ICU-23033 Regenerate scx value array

[Manishearth]

This fixes the scx array hardcoded in icuexportdata for Unicode 16 (see: unicode-org/icu4x#6041)

This is a quick and dirty fix, I've tried to include the python script I used to generate this. We should still fix ICU-21821.

Checklist

• Required: Issue filed: https://unicode-org.atlassian.net/browse/ICU-23033
• Required: The PR title must be prefixed with a JIRA Issue number. Example: "ICU-1234 Fix xyz"
• Required: The PR description must include the link to the Jira Issue, for example by completing the URL in the first checklist item
• Required: Each commit message must be prefixed with a JIRA Issue number. Example: "ICU-1234 Fix xyz"
• Issue accepted (done by Technical Committee after discussion)
• Tests included, if applicable
• API docs and/or User Guide docs changed or added, if applicable

[Manishearth]

r? @markusicu @echeran @sffc

[Manishearth]

I haven't tested the output, please do check that the codepoints are the right ones.

[jira-pull-request-webhook]

Notice: the branch changed across the force-push!

• icu4c/source/tools/icuexportdata/icuexportdata.cpp is different

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

[jira-pull-request-webhook]

Notice: the branch changed across the force-push!

• icu4c/source/tools/icuexportdata/icuexportdata.cpp is different

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

[FrankYFTang]

LGTM thanks

[sffc]

This PR does not fix ICU-21821 and therefore should not be tagged with that issue number.

Is there a rush for this? I would rather see the actual fix. There's no good way to review this PR and we rely on the astute observations of people like @FrankYFTang to catch issues.

[Manishearth]

@sffc we have clients reporting discrepancies in their data because of this. The correct fix involves adding APIs to ICU4C, unless that can be done in a short period of time, I think we should land this and get a new icuexportdata. Or we should somehow patch this data into 2.0.0-beta1 datagen: the goal is to get updated data released, it's not important if icuexportdata is fixed in the meantime.

I'm happy to rewrite the Python code to be a bit more readable and reviewable.

[markusicu]

@sffc points out that this PR does not fix what ICU-21821 says, so we need a different ICU ticket for this quick fix and update the PR description and the commit message.

[FrankYFTang]

Agree w/ @sffc, please file a new ticket and change the PR to use that new ticket

[jira-pull-request-webhook]

Notice: the branch changed across the force-push!

• icu4c/source/tools/icuexportdata/icuexportdata.cpp is different

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

[FrankYFTang]

LGTM

[Manishearth]

Artifact is https://github.com/unicode-org/icu/actions/runs/13074992217/artifacts/2517389874

[Manishearth]

@sffc can you do the uplift dance to get a tagged release? I forgot what needs to be done, is it just a cherry-pick PR to maint?

[sffc]

I think we should just tag from the main branch. It has CLDR 47, but we should be integrating CLDR 47 into ICU4X within the next week anyway.

CC @echeran who usually does this.