note jonadab <div>&gt; The only option is for browsers to suddenly stop </div> <div>&gt; working on invalid X?HTML, but the chances of that </div> <div>&gt; happening are appoximately zero.</div> <p> Suddenly? No. Most of the web is still a non-wellformed mixture of HTML3, HTML4, and imaginary tags made up by specific browsers. However, current browsers <strong>do</strong> choke on non-wellformed markup if it is served with a content-type of text/xml, and that's a first step. As things like XSLT and RDF start to catch on, sites that want to harness the value of those things will have to be redone in wellformed XML, and that's that. (They won't necessarily have to provide and validate against Schemata, but we have to start someplace.) </p> <p>Incidentally, if CGI.pm is now improved to the point of being capable of producing anything that remotely resembles XHTML, maybe I should have another look at it; I've been avoiding it because of two things, and one was the execrable state of its output. If that has been shaped up, maybe the other thing (the tendency to obfuscate the Perl code) has been improved too, since I looked at it (which <em>has</em> been a bit), and I should have a second look.</p> <p><code> --jonadab</code></p> 51012 51120