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

[whatwg] API for encoding/decoding ArrayBuffers into text

From: Glenn Maynard <glenn@zewt.org>
Date: Thu, 15 Mar 2012 16:09:27 -0500
Message-ID: <CABirCh87hgWV+P_7SJg5rycaH6dEtnAdO+vVviBEhoaC_9GMQw@mail.gmail.com>
On Thu, Mar 15, 2012 at 5:03 AM, Anne van Kesteren <annevk at opera.com> wrote:

> 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.

It's used to support text/html content.  There's no content using *this
API* that exists yet, because this API doesn't exist yet.

If we really wanted to expose heuristics, it should be a separate method,
eg. guessEncoding(view) == "Shift-JIS".

Glenn Maynard
Received on Thursday, 15 March 2012 14:09:27 UTC

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