- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Wed, 14 Jul 2004 06:36:06 +0200
- To: www-i18n-comments@w3.org
Hi, http://www.w3.org/TR/i18n-html-tech-char/#ri20030509.100837166 in the latest draft states: [...] For XHTML served as text/html, where practical use an XML declaration with an encoding attribute. [...] This seems a bit inconsistent to me. My reading of the XHTML 1.0 Second Edition Recommendation is that you either must specify the encoding of the document in the HTTP header or use both the corrsponding <meta> element and an encoding declaration in the XML declaration, from <http://www.w3.org/TR/xhtml1/#C_9>: [...] If this is not possible, a document that wants to set its character encoding explicitly must include both the XML declaration an encoding declaration and a meta http-equiv statement (e.g., <meta http-equiv="Content-type" content="text/html; charset=EUC-JP" />). [...] As it is per RFC 2854 mandatory to follow this requirement in order to serve the document as text/html, it seems that the discussion around omitting the XML declaration in the document misses the fact this is only allowed if the Content-Type header has a corresponding charset header. So please reflect this in the document. regards.
Received on Wednesday, 14 July 2004 00:37:00 UTC