| SitePoint Sponsor |
Ok, if you have these relevant codes in your page:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
and
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
Why would :
http://valet.webthing.com say :
No charset specified, but W3C rules for text/html require either an HTTP header or a META hack. I'll try provisional validation with the HTTP default iso-8859-1
? ?
Dez.
A user agent really needs the encoding information before it starts parsing the document. If it's not supplied in the HTTP header, it should come in a <meta> element as early as possible (i.e., right after the <head> opening tag). There must be no characters outside the US-ASCII encoding before the <meta> element.
It seems likely that the validator isn't quite up to it in this instance, but why don't you use W3C's validator instead?
Birnam wood is come to Dunsinane
Posting Permissions
Bookmarks