W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2014

Re: DOMString UTF-16

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 14 Jan 2014 17:28:34 +0000
Message-ID: <CADnb78jsGddKGQajpms4khwCs52AM7fGnH3bLrPt1P6c-5=ShA@mail.gmail.com>
To: Graham Houston <housty.g@gmail.com>
Cc: "www-dom@w3.org" <www-dom@w3.org>
On Tue, Jan 14, 2014 at 3:56 PM, Graham Houston <housty.g@gmail.com> wrote:
> Was pondering the requirement for UTF-16 for DOMString and it seems it could
> be more beneficial if this was an implementation decision on Unicode and not
> a requirement, after all UTF-8 is now the more favourable encoding in use
> today not to mention its more to do with internal handling of strings than
> the final overall use of those strings. How my DOM handles Unicode inside
> should not affect how my DOM handles transfer encodings overall as an API
> and on that grounds I see no reason for DOMString to be a UTF-16
> requirement.
> ??

It's actually more a 16-bit array than UTF-16 and this is all because
of JavaScript. And JavaScript is not going to change.

Received on Tuesday, 14 January 2014 17:29:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:22 UTC