W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2013

Re: ByteString in Web IDL

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 10 Jul 2013 18:32:24 -0400
Message-ID: <CADnb78g9AjEBO3FOx_b6XyWnJKodo6WFbd+_KUAkSCUweUQhKg@mail.gmail.com>
To: Norbert Lindenberg <ecmascript@lindenbergsoftware.com>
Cc: Robin Berjon <robin@w3.org>, Boris Zbarsky <bzbarsky@mit.edu>, "public-script-coord@w3.org" <public-script-coord@w3.org>
On Wed, Jul 10, 2013 at 6:21 PM, Norbert Lindenberg
<ecmascript@lindenbergsoftware.com> wrote:
> Using ByteString effectively imposes ISO 8859-1. That seems to be required for legacy reasons in XMLHttpRequest, but it would generally be the wrong choice for any new API.

It's absolutely the right choice (though calling it iso-8859-1 is
confusing as that means windows-1252 in browsers) as that preserves
the value space. Exposing the bytes works too of course, but given
most byte sequences are "ASCII-compatible" that would be a bad API.

Received on Wednesday, 10 July 2013 22:32:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:17 UTC