P
(Pete Cresswell)
What I've read so far indicates that there are two ways to avoid Validator.w3's
"No Character Encoding Found! Falling back to UTF-8." message:
1) Tell the server to send down a header of "Content-Type: text/html;
charset=ISO-8859-1"
2) Place this tag in <header>:
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
#2 won't pass "Strict" validation...in fact I can't even get it past
Transitional... I guess that leaves #1.
The zinger is that this web page is not coming from what I'd think of as a
"Server". Instead, it's going TB burned on to a CD and the user will read it by
inserting the CD into their local drive.
Obviously this isn't a religious issue, but it would be nice if I could get a
page past Validator with zero errors.
Can anybody explain?
"No Character Encoding Found! Falling back to UTF-8." message:
1) Tell the server to send down a header of "Content-Type: text/html;
charset=ISO-8859-1"
2) Place this tag in <header>:
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
#2 won't pass "Strict" validation...in fact I can't even get it past
Transitional... I guess that leaves #1.
The zinger is that this web page is not coming from what I'd think of as a
"Server". Instead, it's going TB burned on to a CD and the user will read it by
inserting the CD into their local drive.
Obviously this isn't a religious issue, but it would be nice if I could get a
page past Validator with zero errors.
Can anybody explain?