W3C home > Mailing lists > Public > public-html@w3.org > February 2011

Re: Running heuristic encoding detection

From: Anne van Kesteren <annevk@opera.com>
Date: Thu, 10 Feb 2011 10:21:52 +0100
To: "HTML WG" <public-html@w3.org>, "Henri Sivonen" <hsivonen@iki.fi>
Message-ID: <op.vqokaqg764w2qv@anne-van-kesterens-macbook-pro.local>
On Mon, 03 Jan 2011 11:36:14 +0100, Henri Sivonen <hsivonen@iki.fi> wrote:
> Do the other browsers indeed not start parsing until the heuristic  
> detector has committed to an encoding?

Per Leif's email that seems not true for Opera.

> Is there a timeout or a max number of bytes as a cutoff after the  
> browser commits to an encoding even though the heuristic detector hasn't  
> yet made its decision?
> Do other browsers default to heuristic detection enabled in any locale?  
> (Since having different buffering behavior would likely lead to  
> different perf characteristics, it would seem interesting to ship with  
> different perf on a per-locale basis.)

We only enable it for certain locales based on some combination of domain  
name, Content-Language, and encoding of the referring document. When  
enabled it looks at the entire resource. I am not sure what our timeout  
strategy is if any. This is an area we would like to improve at some  
point. It would be nice if more were standardized or at least documented.

Anne van Kesteren
Received on Thursday, 10 February 2011 09:22:31 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:09 UTC