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: Thu, 15 Mar 2012 11:03:22 +0100
Message-ID: <op.wa7h7wnj64w2qv@annevk-macbookpro.local>
On Wed, 14 Mar 2012 23:53:12 +0100, Glenn Maynard <glenn at zewt.org> wrote:
> On Wed, Mar 14, 2012 at 6:52 AM, Anne van Kesteren <annevk at opera.com>  
> wrote:
>> 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.
>
> We don't have any untagged content to support yet, so let's not create an
> API that guarantees it'll come into existence.  The heuristics you need
> depend heavily on the content, anyway (for example, heuristics that work
> for HTML probably won't for ID3 tags, which are generally very short).

What I replied to suggested reusing an existing undocumented code path  
which is definitely used to support existing content. From what I remember  
reading about the detector in Gecko it can be quite useful regardless of  
context.


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Thursday, 15 March 2012 03:03:22 UTC

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