ISSUE-30: Allow utf-16 meta encoding declarations

Allow utf-16 meta encoding declarations

State:
CLOSED
Product:
html
Raised by:
Richard Ishida
Opened on:
2011-06-20
Description:
4.2.5.5 Specifying the document's character encoding
[http://www.w3.org/TR/2010/WD-html5-20100624/semantics.html#charset]


WG Approved: Yes


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.


Please add comments to bugzilla:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10890


IMPORTANT: This issue was moved from our old review tracking system to the new tracker system. For previous mail relating to this issue, see: http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&hdr-1-name=subject&hdr-1-query=%20Allow%20utf-16%20encoding%20declarations&hdr-2-name=from&hdr-2-query=&hdr-3-name=message-id&hdr-3-query=&index-grp=Member__FULL+Public__FULL&index-type=t&type-index=public-i18n-core%40w3.org&resultsperpage=20&sortby=date
Related Actions Items:
No related actions
Related emails:
  1. Review of tracker issues for best practices (from addison@lab126.com on 2015-03-25)
  2. RE: [I18N-ACTION-150] Review of HTML open issues (from addison@lab126.com on 2014-02-22)
  3. Re: [I18N-ACTION-150] Review of HTML open issues (from ishida@w3.org on 2014-02-21)
  4. [minutes] Internationalization telecon 2014-02-20 (from ishida@w3.org on 2014-02-21)
  5. [I18N-ACTION-150] Review of HTML open issues (from addison@lab126.com on 2014-02-18)
  6. [minutes] Internationalization WG telecon 2011-07-27 (from ishida@w3.org on 2011-07-27)

Related notes:

[aphillip]: allow 'utf-16' in charset declarations. wontfix. Last commenter suggested we reopen.

20 Feb 2014, 16:48:21

per teleconference of 2014-02-27

Addison Phillips, 27 Feb 2014, 21:24:58

Display change log ATOM feed


Addison Phillips <addison@amazon.com>, Chair, Richard Ishida <ishida@w3.org>, Fuqiao Xue <xfq@w3.org>, Atsushi Shimono <atsushi@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $