Full Unicode strings strawman
allen at wirfs-brock.com
Mon May 16 17:07:19 PDT 2011
On May 16, 2011, at 4:21 PM, Shawn Steele wrote:
> > Not in my proposal! "\ud800\udc00"=== "\u+010000" is false in my proposal.
I think you'll find that the actual JS engines are currently UCS-2 centric. The surrounding browser environments are doing the UTF-16 interpretation. That why you see 𐀀 instead of �� in browser generated display output.
> In other words I don’t think you can get the engine to be completely UTF-32. At least not without declaring a page as being UTF-32.
I agree that application writer will continue for the foreseeable future have to know whether or not they are dealing with UTF-16 encoded data and/or communicating with other subsystems that expect such data. However, core language support for UTF-32 is a prerequisite for ever moving beyond UTF-16APIs and libraries and getting back to uniform sized character processing.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss