ISSUE-17: UTF-16 an invalid encoding in Polyglot Markup

UTF-16 an invalid encoding in Polyglot Markup

Raised by:
Richard Ishida
Opened on:
3. Specifying a Document's Character Encoding

WG Approved: No

Previously the polyglot document allowed only UTF-8 and UTF-16 encodings. Leif Silli has proposed that only UTF-8 be allowed, and the editor of the polyglot document has changed the specification to say that.

The i18n WG should see whether there is consensus on that approach.

Please add comments to bugzilla:
Related Actions Items:
No related actions
Related emails:
  1. [minutes] Internationalization telecon 2018-02-08 (from on 2018-02-12)
  2. Re: [css-text-decor-3] Updated DoC, open issues (from on 2017-04-06)
  3. [css-text-decor-3] Updated DoC, open issues (from on 2016-12-27)
  4. Review of tracker issues for best practices (from on 2015-03-25)
  5. RE: I18N-ISSUE-17: UTF-16 an invalid encoding in Polyglot Markup [Polyglot] (I18N-ISSUE-31) (from on 2011-03-28)
  6. Issues for mail threads (from on 2011-03-23)

Related notes:

The i18n WG agreed to this change.

Richard Ishida, 20 Jul 2011, 11:30:42

Display change log ATOM feed

Addison Phillips <>, Chair, Richard Ishida <>, Bert Bos <>, Fuqiao Xue <>, Atsushi Shimono <>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $