-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
unicode: update to Unicode 6.2.0 #2874
Labels
Milestone
Comments
The only real issue I could see would be if a Unicode character moved in or out of class Lu or out of classes Ll, Lt, Lm, Lo, or Nd. If we want to be really precise we should list those as possibly breaking backward compatibility for Go 1 source code. I don't think we should worry about the fact that future Unicode standards could change the behaviour of Go 1 programs that use the unicode package. I think that is an acceptable sort of package change, even though it will cause program behaviour to change. I don't think we need to mention this specifically. |
Marking this Later, given the disinclination to update. The people who need Meroitic Cursive will have to wait. I did a trial maketables to skim the diffs. The most significant change in Unicode 6.1.0 (beyond putting blank lines in CaseFolding.txt and thereby breaking maketables) is that the ordinal indicators ª º are now Lo instead of Ll. This breaks the assumption in IsLetter that all Latin-1 letters are either Ll or Lu, which will mean adding a way to express that in the properties table, but we're out of bits. Probably we could use pLl|pLu to mean Lo. If you want to see the diffs, http://golang.org/cl/5616077/diff/3/src/pkg/unicode/tables.go Labels changed: added priority-later, removed priority-go1. |
http://golang.org/cl/6818067 http://code.google.com/p/go/source/detail?r=a8ed5d22b36e Owner changed to @mpvl. Status changed to Fixed. |
One more: lib9/utf Owner changed to @robpike. Status changed to Accepted. |
This issue was closed by revision c15afa8. Status changed to Fixed. |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The text was updated successfully, but these errors were encountered: