Hmmm... perhaps the team should shoot for XHTML 1[.0 Strict|.1]
compliance? ;-) I am still seeing errors/warnings in HTML 4.01
Transitional, though.
That'd be great; I did that half a year or so ago - Steph stopped me
then since it looked bad on her MSIE erm, browser.
Chris,
I only just figured out what you're on about!
When you talked about XHTML back then, you were talking about adding an XHTML DOCTYPE declaration into the manual build system at a point when the entire site used HTML 4.01. Nothing to do with my browser; php.net as a whole uses HTML 4.01 Transitional, that's just the way it is. The phpweb folk are experimenting with XHTML 1.0 Strict, but that's an experiment on their part, and the site itself - including the phpdoc system - actually uses HTML 4.01. As far as I can figure out, the reason their declaration works and ours doesn't is they send HTTP headers via PHP to correct it.
When the manual is displayed on the site, it calls the site headers - this has nothing whatsoever to do with the build system. The only way it'd make sense to add a doctype declaration into the build system would be if you were talking about applying it to the print/html version only. If you're planning to do that, it would be sensible to have it match the declaration for the rest of the site, since the print/html version is displayed on the site as well as on your own box. At present, that declaration happens to be HTML 4.01. (Note: I didn't discover until this week that the DOCTYPE declaration on our site was broken.)
I'd like to upgrade our site to use XHTML 1.0 Transitional (not Strict, note) and possibly revert the recent font size changes - but not the rest of the good work Scott's done over the last few days - depending on how the new sizing looks under XHTML when someone gets a chance to test that. The old sizing looked fine under XHTML Transitional here.
Does anyone know of any good reasons against?
- Steph