- From: <bugzilla@jessica.w3.org>
- Date: Mon, 02 Aug 2010 09:16:24 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10283
Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xn--mlform-iua@xn--mlform-i
| |ua.no
--- Comment #2 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2010-08-02 09:16:24 ---
You right ...
But to answer your question: Because the note (which stands out, than thus
calls for attention), unlike the sentence before the note, makes it seem as if
meta@charset is permitted regardless of its content.
For example, in the debate in public-html before I filed this bug, I did not
spot anyone that pointed to this limitation in the XHTML5 syntax as
justification for not permitting anything more than UTF-8 inside the
meta@charset element.
I suggest the following clarification:
<blockquote cite="http://dev.w3.org/html5/spec/semantics#meta">
The charset attribute on the meta element has no effect in XML
documents<ins>.</ins><del>,</del><ins>But the presence of the charset attribute
with the value "UTF-8"</ins> is <del>only</del> allowed in order to facilitate
migration to and from XHTML.
</blockquote>
--
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 Monday, 2 August 2010 09:16:27 UTC