[Bug 18397] Encoding Sniffing Algorithm: Clarify what "information on the likely encoding" covers

https://www.w3.org/Bugs/Public/show_bug.cgi?id=18397

Robin Berjon <robin@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |robin@w3.org
         Resolution|---                         |WONTFIX

--- Comment #1 from Robin Berjon <robin@w3.org> ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:

   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: none
Rationale:

For context, this is about
http://www.w3.org/html/wg/drafts/html/master/syntax.html#determining-the-character-encoding

The point of this clause is *precisely* to be open ended. The rest of the
algorithm provides good foundations for interoperability in the vast majority
of cases. But then you have situations in which something extra might be
required. For instance, as mentioned in the spec, you may have manually
overridden the encoding in a previous visit to this page. Or the browser may be
calling to a third-party service that has some smart heuristics about encodings
that it can use to override. Or it may believe that during the full moon pages
from the .paris domain switch to being encoded in UTF-9.

The important point is that for decisions that are covered by this clause, the
confidence be set to "tentative". This allows the parser to change the encoding
to something else if it gets better information.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 11 June 2013 11:41:09 UTC