[TxMt] Misguided use of content-type in XHTML/1.1 template

[Allan Odgaard]

On 5. Mar 2007, at 01:00, porneL wrote:

> I've just noticed that template for XHTML/1.1 has been changed to  
> include application/xhtml+xml content type in <meta> element.
>
> This is completly misguided as <meta> is there only for backwards- 
> compatibility non-XHTML user-agents -- that is only those which *do  
> not* support application/xhtml+xml.
>
> From W3C XHTML FAQ:
> "Note that a meta http-equiv statement will not be recognized by  
> XML processors, and authors SHOULD NOT include such a statement in  
> an XHTML document served as 'application/xml' (and 'application/ 
> xhtml+xml' as well for that matter)."

The reason it says SHOULD NOT (which means “not recommended”, see RFC  
2119) is that for an XML document, you declare the content type using  
processing instructions. Though I have no idea how the “content type”  
processing instruction looks, anyone?

> Please change it back to text/html or remove <meta> element completly.

The type of an XHTML 1.1 document is application/xhtml+xml, so if we  
want to actually serve XHTML, we should not change it, and if we  
don’t want to serve XHTML 1.1, we probably should not use the XHTML  
1.1 template ;)

We can remove it, but then we should add the proper XML processing  
instruction, as we can’t IMO rely on the document always being served  
over http. Though as said, I have no idea how this PI looks.