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

ICU-22922 initial ICU 77 download page; incomplete #3370

Merged
merged 1 commit into from
Feb 7, 2025

Conversation

markusicu
Copy link
Member

@markusicu markusicu commented Feb 6, 2025

First cut of the download page. To be refined.
Not yet linked from other pages.
Also add known issues to the ICU 76 download page.

Checklist

  • Required: Issue filed: ICU-22922
  • Required: The PR title must be prefixed with a JIRA Issue number. Example: "ICU-1234 Fix xyz"
  • 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

richgillam
richgillam previously approved these changes Feb 6, 2025
Copy link
Contributor

@richgillam richgillam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

docs/download/77.md Outdated Show resolved Hide resolved
docs/download/77.md Outdated Show resolved Hide resolved
* Note: ICU 76 does not yet support `portion-per-1e9` (aka per-billion). (See [ICU-22781](https://unicode-org.atlassian.net/browse/ICU-22781))
* Subtle segmentation changes to make ICU fully conform to Unicode 16
* Word break: Root tailoring of colon reverted, Swedish & Finnish tailorings removed ([ICU-22941](https://unicode-org.atlassian.net/browse/ICU-22941))
* These tailorings were introduced in ICU 72, but feedback has been negative
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure what this is supposed to be telling me.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am trying to say that this has been a relatively recent thing which we are now reverting

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it's the "fully conform to Unicode 16" thing that's throwing me. We diverged from Unicode 16 and now we're going back into sync with it? Or something else?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The root rules want to match the Unicode segmentation specs.
Sometimes CLDR & ICU experiment with changes before we upstream them back into Unicode proper.
This is a change that hadn't even been discussed with the UTC, and feedback has been negative, and the UTC disagreed with upstreaming this change, so it was decided to revert it in CLDR & ICU.
We should have done this as part of the Unicode 16 update, but missed it.
See the 2024-03-11 design-wg meeting minutes.

(In that meeting, we also agreed to introduce segmentation profiles, but we haven't designed those yet.)

echeran
echeran previously approved these changes Feb 6, 2025
Copy link
Contributor

@echeran echeran left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good so far. RSLGTM

@markusicu markusicu dismissed stale reviews from echeran and richgillam via 50613c2 February 6, 2025 19:04
@markusicu
Copy link
Member Author

I made a few updates. I think this is as much as I can do now. Please re-stamp?

Copy link
Contributor

@richgillam richgillam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the new wording.

Also add known issues to the ICU 76 download page

See unicode-org#3370
@markusicu markusicu force-pushed the download-77-initial branch from 50613c2 to 6a7f168 Compare February 7, 2025 00:06
@jira-pull-request-webhook
Copy link

Hooray! The files in the branch are the same across the force-push. 😃

~ Your Friendly Jira-GitHub PR Checker Bot

@markusicu markusicu merged commit c4acc44 into unicode-org:main Feb 7, 2025
9 checks passed
@markusicu markusicu deleted the download-77-initial branch February 7, 2025 00:09
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