-
I don't think it's necessarily harmful to render XHTML 1.0 as text/html, because text/html is an officially supported MIME type in the specification. XHTML 1.1 and 2.0, however, should not use text/html, but rather text/xml, application/xml, or application/xhtml+xml, only the first of which can be implemented...
-
The character set you use depends largely on your preference. I usually use either ISO-8859-1 or ISO-8859-15, depending on the characters I need to use, because they're more specific to my demographic so they're a bit smaller than Unicode. Rarely does browser implementation take any longer than Unicode...
-
If it weren't for the BOM issue I'd say use UTF-8 but frankly XML parsers are not something I'm going to worry about with my xml since I never serve raw xml on my web pages.
-
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css"> Also found this (somewhere). "There are three MIME types that we can use for XHTML documents, which will make compliant user agents recognise the document as XML: application/xhtml+xml (recommended) application/xml text/xml (not recommended...
-
Sorry to butt in, because I'm no expert, but if this is a long-term project, maybe you should think about server-side XML translation. Then you'd only have to worry about it once. I've briefly done some XSLT, but after learning some PHP methods, it made it a lot easier to integrate my XML with the rest...