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

[whatwg] API for encoding/decoding ArrayBuffers into text

From: Anne van Kesteren <annevk@opera.com>
Date: Wed, 14 Mar 2012 12:52:18 +0100
Message-ID: <op.wa5lp1l164w2qv@annevk-macbookpro.local>
On Wed, 14 Mar 2012 00:50:43 +0100, Joshua Bell <jsbell at chromium.org>  
> For both of the above: initially suggested use cases included parsing  
> data as esoteric as ID3 tags in MP3 files, where encoding unspecified  
> and is
> guessed at by decoders, and includes non-Unicode encodings. It was
> suggested that the encoding sniffing capabilities of browsers be  
> leveraged. (Cue a strong "nooooooo!" from Anne.)

If we can make it a deterministic, unchanging, and defined algorithm, I  
think that would actually be acceptable. And ideally we do define that  
algorithm at some point so new browsers can enter the existing market more  
easily and existing browsers interpret existing content in the same way.

Anne van Kesteren
Received on Wednesday, 14 March 2012 04:52:18 UTC

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