Comment #2 on issue 2875 by [email protected]: Can generate (and parse)
invalid UTF-8
http://code.google.com/p/v8/issues/detail?id=2875
I feared that might be the conclusion.
One much less intrusive option was proposed at
http://esdiscuss.org/topic/code-points-vs-unicode-scalar-values#content-14
which was just to fix it for JSON encoding.
The JSON RFC says that strings are a sequence of unicode "characters", and
Unicode says that surrogates are not characters (confusingly enough the 66
noncharacters are considered characters); though I suspect that the RFC
authors didn't chose that word particularly carefully.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
