> ...if the server is sending the character encoding...Is there > any other reason to include it, client-side?
<ominous tone>Did you read the W3C link posted?</ominous tone> ;) I can't speak with any authority on this matter, and not meaning to break the unwritten rule of not answering unless you know the answer, but: Some servers can be configured to set the HTTP header from the meta http-equiv or examining the first few bytes of the document. In the case of server or configuration limitations, the meta http-equiv can provide user agents with the encoding. >From http://www.w3.org/TR/REC-html40/charset.html#h-5.2.2 <quote> ...conforming user agents must observe the following priorities when determining a document's character encoding (from highest priority to lowest): 1. An HTTP "charset" parameter in a "Content-Type" field. 2. A META declaration with "http-equiv" set to "Content-Type" and a value set for "charset". 3. The charset attribute set on an element that designates an external resource. </quote> -ben ***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *****************************************************
