- From: <bugzilla@jessica.w3.org>
- Date: Thu, 10 Mar 2011 01:58:43 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12279
Summary: [polyglot] Add section on http-equiv and HTTP
Product: HTML WG
Version: unspecified
Platform: PC
URL: http://dev.w3.org/html5/html-xhtml-author-guide/html-x
html-authoring-guide.html#elements
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: HTML/XHTML Compatibility Authoring Guide (ed: Eliot
Graff)
AssignedTo: eliotgra@microsoft.com
ReportedBy: xn--mlform-iua@xn--mlform-iua.no
QAContact: public-html-bugzilla@w3.org
CC: ishida@w3.org, mike@w3.org,
public-html-wg-issue-tracking@w3.org,
public-html@w3.org, eliotgra@microsoft.com
Depends on: 12278
Proposed text:
<section>
<h1>6.x HTTP headers and http-equiv declarations</h1>
Some HTTP headers and http-equiv declarations need special attention in
Polyglot Markup.
<h2>6.x.1 Content-Language</h2>
Example - http-equiv: <meta http-equiv="Content-Language" content="ru"/>
Example - HTTP header: Content-language: ru
There are no direct issues with regard to the use of Content-Language. However,
this is based on the precondition that the <a href=#language-attributes
>language on the root element is declared</a> (to stay clear of the nuances of
how Content-Language affects HTML vs XML) is followed.
<h2>6.x.2 Content-Type</h2>
The HTTP Content-Type: header have no extra rules or restrictions.
Whereas the http-equiv="Content-Type" declaration is forbidden in polyglot
markup.
Also seee <a href="#character-encoding">Specifying a Document's Character
Encoding</a>.
</section>
--
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 Thursday, 10 March 2011 01:58:44 UTC