W3C home > Mailing lists > Public > www-international@w3.org > January to March 2014

Re: Re: Guessing the fallback encoding from the top-level domain name before trying to guess from the browser localization

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Thu, 20 Mar 2014 04:32:16 +0100
To: Henri Sivonen <hsivonen@hsivonen.fi>
Cc: John Cowan <cowan@mercury.ccil.org>, "www-international@w3.org" <www-international@w3.org>
Message-ID: <20140320043216884559.49035449@xn--mlform-iua.no>
Henri Sivonen, Wed, 26 Feb 2014 13:25:17 +0200:

> The TLD-based guessing feature is on Firefox trunk now. However, not
> all country TLDs are participating. 
  [ … ]

It works: Browsing a sub page of www.ria.ru with a Norway-localized 
Firefox, I experienced a different origin iframe document[1] that 
rendered in garbled Latin instead of Cyrillic. But, upgrading my 
browser to Firefox 31 nightly, the iframe in question displayed in 


I believe your current plan to be to exclude from TLD-based guessing 
all country domains for which the locale-based default encoding is 
Win-1252. Assuming I am right, then, for a Russian locale user, 
browsing pages under the .co.uk domain but without encoding 
information, would see the page rendered in Windows Cyrillic.

Would it not be better to let the Russian locale user experience the 
page in Windows 1252, based on the domain? And thus, would it not be 
better to let, in this case, the .co.uk domain participate in the 
TLD-based guessing? It might not be necessary if the browser itself 
defaults to Windows 1252. But for e.g. Russian locale, and other 
locales with non-Windows-1252 default, including even TLDs for which 
the default fallback encoding is Win 1252, would make the user 
experience less gotcha.

leif halvard silli
Received on Thursday, 20 March 2014 03:32:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:04 UTC