Re: [WSG] Conflict between Mime Type and Document Type

2008-01-31 Thread Rimantas Liubertas
Why sniff out browsers that accept XML? If the document is marked as XHTML 1.1 it should allways be sent as XML. ... That is true, but Internet Explorer does not support XHTML. HTML 4.01/5 ftw :) Regards, Rimantas -- http://rimantas.com/

Re: [WSG] Conflict between Mime Type and Document Type

2008-01-31 Thread Designer
Thomas Thomassen wrote: Why sniff out browsers that accept XML? If the document is marked as XHTML 1.1 it should allways be sent as XML. Though, I have seen people sniffing out browsers and using server side scripting to change the doctype. XHTML 1.1 to browsers than supports it, and XHTML

Re: [WSG] Conflict between Mime Type and Document Type

2008-01-31 Thread Gunlaug Sørtun
Designer wrote: Maybe, but coding in xhtml1.1 makes you MUCH more fussy about syntax etc. and it shows up any 'well formed' errors as soon as you browse. So, whilst the user will know nothing about all this, it makes you as a designer get lots of practice in using the stricter syntax, ready for

Re: [WSG] Conflict between Mime Type and Document Type

2008-01-31 Thread Thomas Thomassen
] To: wsg@webstandardsgroup.org Sent: Thursday, January 31, 2008 12:10 PM Subject: Re: [WSG] Conflict between Mime Type and Document Type Thomas Thomassen wrote: Why sniff out browsers that accept XML? If the document is marked as XHTML 1.1 it should allways be sent as XML. Though, I have seen

Re: [WSG] Conflict between Mime Type and Document Type

2008-01-31 Thread Keryx Web
Thomas Thomassen skrev: There's no difference between XHTML 1.1 and XHTML 1.0 Strict. XHTML 1.1 only advantage is that it's modulized Not entirely true. XHTML 1.1 includes ruby. and can only be sent as XML so it can be extended. If you're not extending it then you're better off with XHTML

Re: [WSG] Conflict between Mime Type and Document Type

2008-01-31 Thread Thomas Thomassen
Subject: Re: [WSG] Conflict between Mime Type and Document Type Thomas Thomassen skrev: There's no difference between XHTML 1.1 and XHTML 1.0 Strict. XHTML 1.1 only advantage is that it's modulized Not entirely true. XHTML 1.1 includes ruby. and can only be sent as XML so it can be extended

Re: [WSG] Conflict between Mime Type and Document Type

2008-01-31 Thread Rimantas Liubertas
... FWIW - and I do not wish to reopen the considered harmful debate - appendix C allows for sending XHTML 1.1 as well as XHTML 1.0 as text/html. (That's a recent change in the specs that few seem to know about.) Can you elaborate what appendix C are you talking about?

Re: [WSG] Conflict between Mime Type and Document Type

2008-01-31 Thread Keryx Web
Rimantas Liubertas skrev: Can you elaborate what appendix C are you talking about? http://www.w3.org/TR/xhtml-media-types/xhtml-media-types.html#summary (latest version, supposedly) does not confirm this. The 2nd edition opens things up a bit:

Re: [WSG] Conflict between Mime Type and Document Type

2008-01-30 Thread David Hucklesby
On Tue, 29 Jan 2008 21:37:26 +1100, Andrew Freedman wrote: Conflict between Mime Type and Document Type http://www.bigbaer.com/css_tutorials/css.image.text.wrap.htm Yah. DOCTYPE is XHTML 1.1, which should only be served as XML. I suggest HTML 4.01 or XHTML 1.0 instead, unless you want to

Re: [WSG] Conflict between Mime Type and Document Type

2008-01-30 Thread Thomas Thomassen
to older browsers. Which is meaningless since the document effectivly is XHTML 1.0. - Original Message - From: David Hucklesby [EMAIL PROTECTED] To: wsg@webstandardsgroup.org Sent: Thursday, January 31, 2008 7:07 AM Subject: Re: [WSG] Conflict between Mime Type and Document Type On Tue

Re: [WSG] Conflict between Mime Type and Document Type

2008-01-29 Thread Joe Ortenzi
which site is the this site that is showing you the message: Conflict between Mime Type and Document Type On Jan 28 2008, at 23:22, Andrew Freedman wrote: G'day, I see this warning often when using the W3C validator and figured I must be doing something wrong, but as it is a warning I

Re: [WSG] Conflict between Mime Type and Document Type

2008-01-29 Thread Andrew Freedman
Joe Ortenzi wrote: which site is the this site that is showing you the message: Conflict between Mime Type and Document Type My apologies. In my haste before the Hail storm hit I sent this off without the URL. http://www.bigbaer.com/css_tutorials/css.image.text.wrap.htm Andrew

Re: [WSG] Conflict between Mime Type and Document Type

2008-01-28 Thread Christian Snodgrass
Usually, it is something simple like trying to use a DOCTYPE of XHTML, with the extension html or whatever, and your server is, in reality, serving it up as text/html. Basically, you need to make sure that your server either: a) assumes no MIME type, or b) use an extension like .xhtml and tell

[WSG] Conflict between Mime Type and Document Type

2008-01-28 Thread Andrew Freedman
G'day, I see this warning often when using the W3C validator and figured I must be doing something wrong, but as it is a warning I never bothered looking into it. Now I've seen it on the results from this site so it has roused my curiosity. Can some explain to me why this is occurring and

Re: [WSG] Conflict between Mime Type and Document Type

2008-01-28 Thread David Dorward
On 28 Jan 2008, at 23:22, Andrew Freedman wrote: I see this warning often when using the W3C validator and figured I must be doing something wrong, but as it is a warning I never bothered looking into it. Now I've seen it on the results from this site so it has roused my curiosity. Can