[Bug 12279] [polyglot] Add section on http-equiv and HTTP

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12279

Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CLOSED                      |REOPENED
                URL|http://dev.w3.org/html5/htm |http://dev.w3.org/html5/htm
                   |l-xhtml-author-guide/html-x |l-xhtml-author-guide/html-x
                   |html-authoring-guide.html#e |html-authoring-guide.html#h
                   |lements                     |ttp-headers-and-http-equiv
         Resolution|FIXED                       |

--- Comment #8 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-03-19 14:52:54 UTC ---
(In reply to comment #6)
The HTMLwg just decided that http-equiv="Content-Language" should be illegal.
http://www.w3.org/mid/4D84B9B4.3040809@intertwingly.net
As a result, here is and amandment of the current text. I tried to make it
shorter too.


]]
6.5.1.1 Content-Language

 The HTTP Content-Language: header warrants special discussion in polyglot
markup. 

Example
HTTP header: Content-language: ru

 Whenever there is a HTTP Content-Language: header whose value is no more and
no less than exactly  one language tag, polyglot markup must declare the lang
and the xml:lang attribute on the root element to avoid a difference between
HTML and XML in regard to whether the HTTP Content-Language: header, in the
absense of lang and xml:lang,  sets a fallback language or not.

Note
 For the sake of simplicity and expediency, content to be delivered as polyglot
markup may always include both the xml:lang as well as the lang attributes on
the root element. 
[[

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Saturday, 19 March 2011 14:52:56 UTC