That's fine Lindsay, but I'm citing what is covered in the W3C guidelines regarding this: http://www.w3.org/TR/xhtml1/#C_9
And as I stated in my response to Kay, if you're able to set the header information and be sure it will always stay that way, then by all means don't put in the meta-tag. 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 Lindsay Evans Sent: Wednesday, 9 June 2004 1:14 PM To: [EMAIL PROTECTED] Subject: RE: [WSG] www.seoed.com - Please review 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 ***************************************************** ***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *****************************************************
