Re: HTML5 Issue 11 (encoding detection): I18N WG response...

Larry Masinter wrote:

> What benefits to the Internet, the Web, to anyone else, is there
> in specifying what the default configuration should be for various
> "demographics", independent of the actual user's language and
> preference? Does it help a Kenyan who brings a laptop for use
> by his Egyptian wife living in Finland?
I assume the rationale is that there needs to be a default encoding for 
when legacy content does not indicate its encoding.

Essentially its a crude numbers game, that assumes :
1) browsers actually support the encoding a legacy document is in. which 
isn't always true. the number of current blogs posts i've been seeing 
lately using one of the VNI encodings is a case in point.
2) it assumes that countries or regions are homogeneous, with everyone 
using the same language. Most of my friend's in Melbourne (Australia) 
may surf the net in English, but just as often use another language on 
the web, a few using encodings not supported by modern web browsers.



Andrew Cunningham
Senior Manager, Research and Development
State Library of Victoria
328 Swanston Street
Melbourne VIC 3000

Ph: +61-3-8664-7430
Fax: +61-3-9639-2175

Alt email:

Received on Monday, 12 October 2009 02:19:46 UTC