- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Sun, 22 Apr 2012 09:12:18 +1000
- To: public-texttracks@w3.org
FYI, Silvia. ---------- Forwarded message ---------- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com> Date: Sun, Apr 22, 2012 at 9:11 AM Subject: Re: [whatwg] Encoding Sniffing To: Anne van Kesteren <annevk@opera.com> Cc: WHATWG <whatwg@whatwg.org>, Henri Sivonen <hsivonen@iki.fi>, Alexey Proskuryakov <ap@webkit.org>, Simon Montagu <smontagu@smontagu.org>, Peter Krefting <peter@opera.com> On Sat, Apr 21, 2012 at 8:21 PM, Anne van Kesteren <annevk@opera.com> wrote: > Hey, > > This morning I looked into what it would take to define Encoding Sniffing. > http://wiki.whatwg.org/wiki/Encoding#Sniffing has links as to what I looked > at (minus Opera internal). As far as I can tell Gecko has the most > comprehensive approach and should not be too hard to define (though writing > it all out correctly and clear will be some work). > > I have some questions though: > > 1) Is this something we want to define and eventually implement the same > way? > 2) Does this need to apply outside HTML? For JavaScript it forbidden per the > HTML standard at the moment. CSS and XML do not allow it either. Is it used > for decoding text/plain at the moment? We've had some discussion on the usefulness of this in WebVTT - mostly just in relation with HTML, though I am sure that stand-alone video players that decode WebVTT would find it useful, too. Cheers, Silvia. > 3) Is there a limit to how many bytes we should look at? > > Thanks, > > > -- > Anne van Kesteren > http://annevankesteren.nl/
Received on Saturday, 21 April 2012 23:13:10 UTC