W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2013

[Bug 13394] i18n-ISSUE-74: Remove Content-Language meta from polyglot

From: <bugzilla@jessica.w3.org>
Date: Wed, 30 Oct 2013 21:37:33 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-13394-2486-iAkP8VzSJt@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13394

Eliot Graff <eliotgra@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Eliot Graff <eliotgra@microsoft.com> ---
    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

I believe that this bug has previously been fixed, and so I am marking it so. 

The current editor's draft states: 

When specifying the language mapping of an element, polyglot markup uses both
the lang and the xml:lang attributes. Neither attribute is to be used without
the other, and polyglot markup maintains identical values for both lang and
xml:lang.

The root element SHOULD always specify the language, or else HTML’s fallback
language effect may step in and cause the language to vary depending on whether
the document is consumed as XML (where the fallback language is not required to
work) or consumed via file URI (where fallback language via external HTTP
Content-Language would not work). Note that the internal
http-equiv="Content-Language meta element is non-conforming in HTML5. For more,
see e.g. HTML5’s language determination rules.

http://dev.w3.org/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html#language-attributes


When specifying the language mapping of an element, polyglot markup uses both
the lang and the xml:lang attributes. Neither attribute is to be used without
the other, and polyglot markup maintains identical values for both lang and
xml:lang.

The root element SHOULD always specify the language, or else HTML’s fallback
language effect may step in and cause the language to vary depending on whether
the document is consumed as XML (where the fallback language is not required to
work) or consumed via file URI (where fallback language via external HTTP
Content-Language would not work). Note that the internal
http-equiv="Content-Language meta element is non-conforming in HTML5. For more,
see e.g. HTML5’s language determination rules.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 30 October 2013 21:37:38 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:45 UTC