code review 9103046: doc: only U+FEFF is a byte-order mark; U+FFFE is not

doc: only U+FEFF is a byte-order mark; U+FFFE is not

[rsc, 2013-05-02 18:49:55]

Hello golang-dev@googlegroups.com,

I'd like you to review this change to
https://code.google.com/p/go/

[r, 2013-05-02 18:53:36]

LGTM
although really it's not that simple. unicode.org explicitly says that FFFE is
not a character but can be used in contrast to FEFF to determine byte order.

[rsc, 2013-05-02 19:01:20]

Right, but in a Go program, only FEFF is allowed.

[rsc, 2013-05-02 19:03:01]

*** Submitted as https://code.google.com/p/go/source/detail?r=9557a7d76d60 ***

doc: only U+FEFF is a byte-order mark; U+FFFE is not

R=golang-dev, r
CC=golang-dev
https://codereview.appspot.com/9103046

[nitrix, 2013-05-02 19:06:19]

We can re-update the doc when U+FFFE is supported. For now I'd rather have
something that is consistent. It looks good to me. The verdict?

[rsc, 2013-05-02 19:10:57]

The implementation has always been correct; the doc now agrees.

FFFE will not be supported. It is not a byte-order mark. It only appears if
you are reading a UCS-2 or UTF-16 file incorrectly (meaning you have the
byte order backward and misread the real FEFF value).

Russ

[alexb_frankandoak.com, 2013-05-02 19:19:17]

Amazing then (: