W3C home > Mailing lists > Public > public-html@w3.org > August 2010

Re: i18n Polyglot Markup/Encodings

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Mon, 2 Aug 2010 04:59:41 +0200
To: Henri Sivonen <hsivonen@iki.fi>
Cc: public-html <public-html@w3.org>, Eliot Graff <eliotgra@microsoft.com>, public-i18n-core@w3.org
Message-ID: <20100802045941217144.48600b9a@xn--mlform-iua.no>
Leif Halvard Silli, Mon, 2 Aug 2010 02:00:48 +0200:
> Henri Sivonen, Thu, 29 Jul 2010 07:19:37 -0700 (PDT):
>>> Next question: if one can specify any encoding via HTTP, why forbid
>>> any encoding inside <meta charset='*'/>?
>> If the meta prescan finds something, the real encoding has to be a 
>> rough ASCII superset.
>> See https://bugzilla.mozilla.org/show_bug.cgi?id=582788

> Perhaps HTML5 as well should only permit "UTF-8" as the value of <meta 
> charset="*"/>, when present in XHTML? That could solve this dilemma 
> when it comes to Polyglot Markup as well! 
> 	Please file bug, if you think so. 
> If <meta charset="windows-1251"/> can't facilitate migration, then it 
> can much less be polyglot, one should think ... However, by the letter, 
> then <meta charset="windows-1251"/> is permitted in both XHTML5 and 
> HTMl5. Thus it is polyglot. OK, <meta charset="windows-1251"/> creates 
> some problems - some possibilities for misunderstanding and so on. But 
> it is still polyglot - it is still permitted.

I filed a bug myself: 
leif halvard silli
Received on Monday, 2 August 2010 03:00:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 2 August 2010 03:00:25 GMT