Comment #27 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
Your are right, native library we were using to create json object (json-glib) was replacing single \ in string passed to it with double \\ (!!) and it was getting transmitted as such. We can conclude that there is no rendering issue, our mistake in not analysing all aspects properly.
As said earlier we were sending non BMP as utf8 only but as it was getting replaced by U+FFFD we tried sending surrogate pairs instead in format \ud834\udf56 for non BMP.
As already updated, in chrome v15 our existing implementation of sending everything as utf8 over websocket works fine, don't know where is the fix(v8 or chrome)
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
