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

unicode: update to Unicode 6.2.0 #2874

Closed
rsc opened this issue Feb 3, 2012 · 8 comments
Closed

unicode: update to Unicode 6.2.0 #2874

rsc opened this issue Feb 3, 2012 · 8 comments
Assignees
Milestone

Comments

@rsc
Copy link
Contributor

@rsc rsc commented Feb 3, 2012

unicode 6.1 is official as of a few days ago.
We should update both lib9/utf and package unicode.
Assuming r will want to do this, probably for Go 1.
@robpike
Copy link
Contributor

@robpike robpike commented Feb 3, 2012

Comment 1:

I'm not so sure. New unicode standards come out all the time. 6.0 seems like a fine,
tested base for Go 1.
A more important question is how the unicode standards that roll out during the life of
Go 1 will affect compatibility. Do we need to say something in the compatibility
document?
@ianlancetaylor
Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Feb 3, 2012

Comment 2:

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.
@rsc
Copy link
Contributor Author

@rsc rsc commented Feb 6, 2012

Comment 3:

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.

@rsc
Copy link
Contributor Author

@rsc rsc commented Sep 12, 2012

Comment 4:

Unicode 6.2.0 is slated for release in September. That's probably the one to use for Go
1.1.

Labels changed: added go1.1.

@robpike
Copy link
Contributor

@robpike robpike commented Oct 17, 2012

Comment 5:

6.2.0 is out.
@robpike
Copy link
Contributor

@robpike robpike commented Oct 31, 2012

@rsc
Copy link
Contributor Author

@rsc rsc commented Oct 31, 2012

Comment 7:

One more: lib9/utf

Owner changed to @robpike.

Status changed to Accepted.

@robpike
Copy link
Contributor

@robpike robpike commented Oct 31, 2012

Comment 8:

This issue was closed by revision c15afa8.

Status changed to Fixed.

@rsc rsc added fixed labels Oct 31, 2012
@rsc rsc added this to the Go1.1 milestone Apr 14, 2015
@rsc rsc removed the go1.1 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.