On Fri, Mar 16, 2007 at 07:16:55PM -0700, Ben Wiley Sittler wrote: > I believe it's more "DHTML" that is the problem. > > DOMString is specified to be UTF-16. Likewise for ECMAScript strings, > IIRC, although they may still be officially UCS-2.
Indeed, this was what I was thinking of. Thanks for clarifying. BTW, any idea WHY they brought the UTF-16 nonsense to DOM/DHTML/etc.? As far as I can tell there's no reason JS and such were restricted to 16bit types for characters; changing it to 32bit (or 21bit or whatever) shouldn't be able to break anything... It's not like JS is a systems programming language with pointers and type casts between pointer types. It's just working with abstract character numbers. I wonder if there's any hope that the madness will eventually be fixed, or if we'll be stuck with UTF-16 forever here.. Rich -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
