(December 18, 2012 at 10:05 am)Aractus Wrote: The purpose of XHTML is to be a reformulation of HTML.This strikes me as a complete contradiction to what you said earlier:
Aractus Wrote:XHTML is XML (it isn't HTML).
Quote:You can't just add the XHTML doctype tag into any HTML document and expect it to behave correctly.True, but then again you can't just add the XHTML doctype to any XML document and expect it to behave correctly or even validate either.
Observe: http://atheistforums.org/valid-xml.xml (Perfectly valid XML)
With an XHTML doctype: http://atheistforums.org/invalid-xhtml.html (Completely invalid XHTML)
Even your scheme validator rejects it: http://schneegans.de/sv/?url=http://athe...xhtml.html
Quote:XML speed is important for more limited devices like smartphones. I'll also point out that it consumes less memory than the same HTML document does.Yup, but then again, smartphones are already fast enough to handle complex websites, and they are only getting faster. It would only be really noticeable on websites that are heavily complex.
Quote:In a way I see HTML 5 as a huge step backwards when we could have simply moved forward with XHTML if people had actually known how to use it. The compatibility issues are far less than with traditional HTML.[quote]My point was, if I.E. cared about standards at all, there would be no need for HTML if statements. This was probably best shown with the Acid tests, more specifically, Acid3, which browsers like Chrome, Opera, and Firefox made a real effort to pass, whilst I.E. only passed it for the first time in 2011, and even then, didn't render the image perfectly.
The advantage of XHTML is that you can easily turn any HTML document into an XHTML document, even if it is HTML5. As long as you abide by the specs, there is no reason why an HTML5 document can't be written in a valid XML structure.
[quote]That's what I use to determine if the document is sent as XML or not. And no part of it is plagiarized, FYI. XHTML behaves in different ways to HTML. But the compatibility is so easily managed, I don't think I can ever remember needing to use <!--[if ...]> outside of CSS, and even then only i I'm doing something silly like embedding fonts.