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

[whatwg] API for encoding/decoding ArrayBuffers into text

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 13 Mar 2012 22:59:49 +0000 (UTC)
Message-ID: <Pine.LNX.4.64.1203132255070.6189@ps20323.dreamhostps.com>
On Tue, 13 Mar 2012, Jonas Sicking wrote:
> 
> Something that has come up a couple of times with content authors
> lately has been the desire to convert an ArrayBuffer (or part thereof)
> into a decoded string. Similarly being able to encode a string into an
> ArrayBuffer (or part thereof).
> 
> Something as simple as
> 
> DOMString decode(ArrayBufferView source, DOMString encoding);
> ArrayBufferView encode(DOMString source, DOMString encoding,
> [optional] ArrayBufferView destination);
> 
> would go a very long way. The question is where to stick these
> functions. Internationalization doesn't have a obvious object we can
> hang functions off of (unlike, for example crypto), and the above
> names are much too generic to turn into global functions.

Shouldn't this just be another ArrayBufferView type with special 
semantics, like Uint8ClampedArray? DOMStringArray or some such? And/or a 
getString()/setString() method pair on DataView?

Incidentally I _strongly_ suggest we only support UTF-8 here.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 13 March 2012 15:59:49 UTC

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