RE: HTML5 Issue 11 (encoding detection): I18N WG response... from Phillips, Addison on 2009-08-20 (public-i18n-core@w3.org from July to September 2009)

From: Phillips, Addison <addison@amazon.com>
Date: Thu, 20 Aug 2009 00:23:27 -0700
To: Henri Sivonen <hsivonen@iki.fi>
CC: "public-html@w3.org" <public-html@w3.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Message-ID: <4D25F22093241741BC1D0EEBC2DBB1DA01ACCE9B9B@EX-SEA5-D.ant.amazon.com>

> 
> > This is after all, after everything, even autodetection, has
> failed.
> > Some encoding must be used to interpret the bytes into characters.
> > Why prefer a legacy encoding here?
> 
> 
> Because the autodetection has already recognized UTF-8 with a high
> probability, so there are only legacy encodings left at this point.
> 

Exactly so, assuming the optional step 6 has been paid attention to.

Addison

Received on Thursday, 20 August 2009 07:24:08 UTC