The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

That's good, as I'm of the opinion that a Strict doctype is more appropriate (for new websites - for example if I were to code a website, it would be with a Strict doctype). I'll be attempting my first WordPress theme soon.

Have you found a way for WordPress to serve pages with the correct content type instead of "Content-Type: text/html" ??
I suppose "fake" XHTML Strict is better than "fake" XHTML Transitional. But if you know of a way to have it doctype-switch I'm interested.

Have you found a way for WordPress to serve pages with the correct content type instead of "Content-Type: text/html" ??
I suppose "fake" XHTML Strict is better than "fake" XHTML Transitional. But if you know of a way to have it doctype-switch I'm interested.

Correct me if I'm wrong but isn't the problem the same if you serve it as transitional or strict? It would be nice if someone would rewrite the backend to put out proper html 4 type syntax, though, instead of faking xhtml.

If someone hacks the html on the back end to put out the right header, that would mean that IE just couldn't display it sensibly at all, right?

There are other variations of this, but AFAIK, this is OK, although apparently some bots don't send HTTP ACCEPT headers.
But I have not figured out a way to do something similar for the "blog" or "forum" parts of my site yet.