Jeff wrote: > Hi Razvan > I'd only pick up 2 thinks to include: > 1. <meta http-equiv="Content-type" content="text/html; charset=UTF-8" > /> - or another appropriate character set.
Then Kay wrote: > Isn't this only an issue if your server is not sending the > encoding in the headers? Correct. There is no need to specify a content-type meta tag in your HTML if your webserver is sending the correct HTTP headers, as seoed.com seems to be doing: Content-Type: text/html; charset=iso-8859-2 <meta http-equiv> is exactly what it sounds like: an equivalent to a HTTP header /me thinks about doing a WSG HTTP presentation for about the 1000th time -- Lindsay Evans. Developer, Red Square Productions. [p] 8596.4000 [f] 8596.4001 [w] www.redsquare.com.au ***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *****************************************************
