W3C XHTML Spec C.9. - "If a document is to be served as multiple media types, the HTTP server must be used to set the encoding of the document."
If you are working on an Intranet or Dedicated web-server then I would say you shouldn't have to worry about it too much, but if you're on a shared web server (as most people on this list would be) then I would definitely include a Content Type meta-tag as this will ensure the user agent recognises any character encoding, and the text is rendered correctly. Cheers Jeff Lowder Accessibility 1st Website: www.accessibility1st.com.au Blog: www.accessibility1st.com.au/journal/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kay Smoljak Sent: Wednesday, 9 June 2004 12:34 PM To: [EMAIL PROTECTED] Subject: RE: [WSG] www.seoed.com - Please review > 1. <meta http-equiv="Content-type" content="text/html; > charset=UTF-8" /> > - or another appropriate character set. Isn't this only an issue if your server is not sending the encoding in the headers? I've been removing this as unnecessary code bloat seeing as our server is configured correctly. If that's not the case I'd better start putting them back! -- Kay Smoljak Senior Developer/QC Leader/Search Optimisation PerthWeb Pty Ltd - http://www.perthweb.com.au/ Ph: 08 9226 1366 - Fax: 08 9226 1375 ***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ***************************************************** ***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *****************************************************
