ISSUE-17: UTF-16 an invalid encoding in Polyglot Markup
UTF-16 an invalid encoding in Polyglot Markup
- State:
- CLOSED
- Product:
- polyglot
- Raised by:
- Richard Ishida
- Opened on:
- 2011-03-18
- Description:
- 3. Specifying a Document's Character Encoding
http://dev.w3.org/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html#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:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12242 - Related Actions Items:
- No related actions
- Related emails:
- [minutes] Internationalization telecon 2018-02-08 (from ishida@w3.org on 2018-02-12)
- Re: [css-text-decor-3] Updated DoC, open issues (from fantasai.lists@inkedblade.net on 2017-04-06)
- [css-text-decor-3] Updated DoC, open issues (from fantasai.lists@inkedblade.net on 2016-12-27)
- Review of tracker issues for best practices (from addison@lab126.com on 2015-03-25)
- RE: I18N-ISSUE-17: UTF-16 an invalid encoding in Polyglot Markup [Polyglot] (I18N-ISSUE-31) (from addison@lab126.com on 2011-03-28)
- Issues for mail threads (from ishida@w3.org on 2011-03-23)
Related notes:
The i18n WG agreed to this change. http://lists.w3.org/Archives/Public/public-i18n-core/2011JanMar/0132.html
Richard Ishida, 20 Jul 2011, 11:30:42Display change log