W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2012

[whatwg] API for encoding/decoding ArrayBuffers into text

From: Simon Pieters <simonp@opera.com>
Date: Thu, 15 Mar 2012 07:53:42 +0100
Message-ID: <op.wa69fspvidj3kv@simons-macbook-pro.local>
On Wed, 14 Mar 2012 23:33:06 +0100, Joshua Bell <jsbell at chromium.org>  
wrote:

> FYI, I've updated http://wiki.whatwg.org/wiki/StringEncoding
>
> * Rewritten in terms of Anne's Encoding spec and WebIDL, for algorithms,
> encodings, and encoding selection, which greatly simplifies the spec.  
> This
> implicitly adds support for all of the other encodings defined therein -  
> we
> may still want to dictate a subset of encodings. A few minor issues noted
> throughout the spec.
> * Define a "binary" encoding, since that support was already in this  
> spec.

Maybe atob() and btoa() could be extended to work with ArrayBuffers?

> We may decide to kill this but I didn't want to remove it just yet.
> * Simplify methods to take ArrayBufferView instead of
> any/byteOffset/byteLength. The implication is that you may need to use
> temporary DataViews, and this is reflected in the examples.
> * Call out more of the big open issues raised on this thread (e.g. where
> should we hang this API)
>
> Nothing controversial added, or (alas) resolved.


-- 
Simon Pieters
Opera Software
Received on Wednesday, 14 March 2012 23:53:42 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:40 UTC