- From: <bugzilla@jessica.w3.org>
- Date: Thu, 30 Sep 2010 18:56:10 +0000
- To: public-i18n-core@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10890 Summary: i18n comment : Allow utf-16 meta encoding declarations Product: HTML WG Version: unspecified Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: public-i18n-core@w3.org QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org, public-i18n-core@w3.org Comment from the i18n review of: http://dev.w3.org/html5/spec/ Comment 8 At http://www.w3.org/International/reviews/0802-html5/ Editorial/substantive: S Tracked by: RI Location in reviewed document: 4.2.5.5 Specifying the document's character encoding [http://www.w3.org/TR/2010/WD-html5-20100624/semantics.html#charset] Comment: Currently you are not allowed to use <meta charset="utf-16"> or the equivalent pragma directive in utf-16 encoded documents. While logically it is not needed to identify the character encoding, it introduces a special case for authors to remember, and almost certainly many authors will be unaware that this is disallowed and will do it. In addition, in-document declarations of this kind are particularly useful for developers, testers, or translation production managers who want to visually check the encoding of a document (since the bom cannot be seen). Furthermore, there would appear to be no risk incurred by allowing this, since the document would be encoded in utf-16 anyway. Note that the ask is not that the encoding of the document be determined by the meta element - the bom remains the way of determining that information - solely that no error or warning be raised if the meta element is used. Please make an exception in the spec for utf-16 so that it is allowed to use <meta charset="utf-16"> or the equivalent pragma directive in utf-16 encoded documents. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You reported the bug.
Received on Thursday, 30 September 2010 18:56:13 UTC