Leif S. wrote:
Currently, XML Editor issues a warning whenever an (X)HTML5 document
contains this meta element:
|<meta Content-Type="http-equiv" content="text/html; charset=UTF-8" /> |
However, that variation of the Content-Type meta element (that is: a
meta element of Content-Type="http-equiv" *and* content="text/html;
charset=UTF-8") *is* permitted, in both HTML and XHTML - *provided* that
the encoding is "UTF-8":
https://www.w3.org/TR/html51/single-page.html#statedef-http-equiv-content-type
«The encoding declaration state may be used in HTML documents and in XML
Documents. If the encoding declaration state is used in XML Documents,
the name of the character encoding must be an ASCII case-insensitive
match for the string "UTF-8" (and the document is therefore forced to
use UTF-8 as its encoding).»
Thus, the rules for when
|<meta Content-Type="http-equiv" content="text/html; charset=UTF-8" /> |
and
|<meta charset="UTF-8" /> |
can be used in XML documents, are identical: They can be used when the
encoding of the document is UTF-8.
XMLmind XML Editor does not report any error or warning for an (X)HTML5
document containing either:
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
or:
<meta charset="UTF-8" />
My guess is that you simply made a typo:
Content-Type="http-equiv"
should read:
http-equiv="Content-Type"
However, it's true that XMLmind XML Editor only accepts:
http-equiv="content-type" LOWER CASE
and not:
http-equiv="Content-Type" MIXED CASE
This is a limitation because the values allowed for attribute http-equiv
should not be case-sensitive.
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
