<webben> pgimeno: There is currently no big advantage in *serving* XHTML 1.0 as text/html. And there is unlikely to ever be a big advantage.
<webben> The *only* advantage is that it the validator checks for a few more things when it's XHTML.
<webben> e.g. alt tags on images
<webben> but you should be doing that anyway
<webben> that is, people should know how to author html properly even without a validator
<webben> since validators do not in fact enforce the full constraints/recommendations of the (x)html syntax
<webben> pgimeno: and in any case, serving as text/html means that you have to be aware of the guidelines mentioned in my faq in topic
<webben> which the validator doesn't check
<webben> so you lose more than you gain
<webben> here's the stated objective of XHTML: http://www.w3.org/TR/xhtml1/#why
<webben> none of that stuff really applies to you
<webben> in particular, the current table based layout messes up your mobile device compatibility anyway
<webben> There are plenty of disadvantages to serving XHTML as text/html.
<webben> Above all, it's broken SGML that only works at all because browsers actually parse tag soup.
<webben> But the disadvantages are summarized by the Hixie doc: http://hixie.ch/advocacy/xhtml
<webben> pgimeno: let me know if you want more info on anything
<webben> There are advantages to using XML on the server side; and there are putative (largely unrealized) advantages to serving application/xhtml+xml