Re: [WSG] XHTML again - was:[Claiming compliance when a site doesn't' actually comply]

[Lynne Pope]

I didn't want my first contribution to the group to be a comment on another person's website, but as you said you are learning Bob I thought you might find this helpful.  The problem with browser sniffing is that you have to be very careful to serve the right information.  At the moment, your site does not validate for css or for HTML 4.01.  In IE, your site shows <meta http-equiv="Content-Type"      content="application/xhtml+xml; charset=utf-8">. It needs to be sent with the "text/html" mime type.  A little tweak to your php code and you will have it nailed ;)

Regards,
Lynne

On 1/6/06, designer <[EMAIL PROTECTED]> wrote:

The approach I use (I'm learning, incidentally)  was triggered originally by Georg :  write your page as XHTML ( 1.1 even) and serve it whilst testing as application/xhtml+xml.  When it validates and there are no well formedness errors, you can serve it in any way you want/need, knowing that 'it's ready'.  For anyone who hasn't seen it, a great way to actually use the resulting code is to use PHP to check the http_accept and insert the DTD header/mimetype as appropriate (see

http://www.workingwith.me.uk/articles/scripting/mimetypes/


I have used this approach on my site ( [1 ]below) and this serves the pages as html 4.01 to IE , and xhtml1.1 to 'modern browsers like FF, Opera, etc.  I'm not sure of the real world value at this time, but certainly it is an excellent discipline in helping me write well formed pages.


Best Regards,

Bob McClelland

Cornwall (UK)
[1]  http://www.gwelanmor-internet.co.uk