Skip to content

unicode: upgrade to Unicode 16.0.0 #73388

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.

Sign up for GitHub

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

Jump to bottom
Open
cowtoolz opened this issue Apr 15, 2025 · 4 comments
Open

unicode: upgrade to Unicode 16.0.0 #73388

cowtoolz opened this issue Apr 15, 2025 · 4 comments
Labels
NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Backlog

Comments

@cowtoolz
Copy link
Contributor

cowtoolz commented Apr 15, 2025 •
edited
Loading

Upgrade all of the versioned Unicode code to use new code generated for the current version 16.0.0, released September 10, 2024. Go is currently on Unicode v15.0.0

Closes #65141
@prattmic prattmic added the NeedsFix The path to resolution is known, but the work has not been done. label Apr 18, 2025
@prattmic prattmic added this to the Backlog milestone Apr 18, 2025
@prattmic
Copy link
Member

cc @golang/security @robpike

@rolandshoemaker
Copy link
Member

This doesn't seem like an easy upgrade. Simply running UNICODE_VERSION=16.0.0 go generate fails, seemingly due to the introduction of some new scripts that have complex layouts that we don't properly handle in unicode/norm/maketables.go.

I do not have a firm enough grasp of Unicode to understand how this would be fixed.

@rolandshoemaker
Copy link
Member

In particular it seems like we will need to do something about https://www.unicode.org/reports/tr15/tr15-56.html#Contexts_Care.

@cowtoolz
Copy link
Contributor Author

@rsc seems to be actively doing some related work #70780

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@prattmic @rolandshoemaker @cowtoolz