Re: DOMString UTF-16
Anne van Kesteren <[email protected]>
| Newsgroups | gmane.comp.web.dom.general |
|---|---|
| Message-ID | <CADnb78jsGddKGQajpms4khwCs52AM7fGnH3bLrPt1P6c-5=ShA@mail.gmail.com> |
On Tue, Jan 14, 2014 at 3:56 PM, Graham Houston <[email protected]> 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. -- http://annevankesteren.nl/