Comment #20 on issue 761 by [email protected]: Incorrect UTF-8 encoding/decoding for non-BMP characters in String related functions
http://code.google.com/p/v8/issues/detail?id=761
I've been reading up on websockets, and splitting into surrogate pairs before sending it from the server is probably not the way to go (it is if you want to inject strings directly into V8 using the UTF-8 API, but that's not what Chromium normally does). The websocket protocol expects valid UTF-8.
If you are sending *from* JavaScript, you'll have to use properly matched surrogate pairs (because all you have is strings as 16-bit number sequences), and the web-socket send method must convert that to valid UTF-8.
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
