This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 18406 - i18n-ISSUE-165: Add character encoding declaration to section 11
Summary: i18n-ISSUE-165: Add character encoding declaration to section 11
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML/XHTML Compatibility Authoring Guide (ed: Eliot Graff) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Eliot Graff
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-25 19:17 UTC by i18n IG
Modified: 2013-04-24 01:11 UTC (History)
4 users (show)

See Also:

Attachments

Description i18n IG 2012-07-25 19:17:44 UTC 
11. Example Document
http://www.w3.org/TR/html-polyglot/#example-document

The i18n WG would prefer the example code in section 11 to have a visible encoding declaration (ie. <meta charset="utf-8"/>. This would illustrate the points made in section 3.
Comment 1 Eliot Graff 2013-04-24 01:11:08 UTC 
    EDITOR'S RESPONSE: This is an Editor's Response to your comment. If
    you are satisfied with this response, please change the state of
    this bug to CLOSED. If you have additional information and would
    like the Editor to reconsider, please reopen this bug. If you would
    like to escalate the issue to the full HTML Working Group, please
    add the TrackerRequest keyword to this bug, and suggest title and
    text for the Tracker Issue; or you may create a Tracker Issue
    yourself, if you are able to do so. For more details, see this
    document:

       http://dev.w3.org/html5/decision-policy/decision-policy.html

    Status: Accepted
    Change Description: Added the encoding declaration in the published sample page and in the code reproduced in the spec
    

new revision: 1.8; previous revision: 1.7