- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 07 Apr 2009 09:57:58 +0200
- To: Adam Barth <w3c@adambarth.com>
- CC: Lisa Dusseault <lisa.dusseault@messagingarchitects.com>, HTTP Working Group <ietf-http-wg@w3.org>
Adam Barth wrote: > On Tue, Apr 7, 2009 at 12:02 AM, Julian Reschke <julian.reschke@gmx.de> wrote: >>> As far as I know, none of the major implementations of content >>> sniffing provide user overrides. This is in contrast to charset >>> detection, where most major implementations let the user override. (I >>> believe this is because charsets are a huge mess in Asia.) I think it >>> makes sense to discuss this in the draft. I'll add it to the next >>> version. >>> ... >> I think that is incorrect; it even has been discussed over here in this very >> context: >> >> <http://lists.w3.org/Archives/Public/ietf-http-wg/2008JanMar/0173.html> >> >> and >> >> <http://blogs.msdn.com/ie/archive/2005/02/01/364581.aspx#364853> > > Honestly? Undocumented, numerical registry keys are hardly a user > interface. By contrast, I can override the charset encoding in Safari > (which is the browser I happen to have in front of me) by selecting > "Text Encoding" from the View menu. It is badly documented, yes. But it is a user override. BR, Julian
Received on Tuesday, 7 April 2009 07:58:51 UTC