Re: url issues

[Stefan]

> I realize that it's not entirely clear what should be done with the
> actual data in general.  For instance, W3 makes some effort to extract
> a charset from an http-equiv element (which requires an HTML parse).
> Other details probably aren't clear-cut, especially in the absence of
> useful MIME info, but I never looked at this closely, I'm afraid.

The code I installed also looks for an http-equiv element AFAIK.

> I think if the charset is specified, it should be obeyed like
> `coding-system-for-read'.  Emacs shouldn't be incorrect because some
> web servers don't DTRT and penalize systems that do.

I think we mostly agree: the http header's coding info should be taken into
account (contrary to what the current code does).  Actually that's what my
comment says.

Where we disagree is about what to do when that info is
insufficient/incorrect.  My experience when using url-handler-mode (which
is what I'm talking about, remember the function is in url-handlers.el)
is that headers are often incorrect, so it'd be good to make use of them,
but they should be taken with a grain of salt.

>> PS: Haven't had time to look at the rest of your points.  If you
>> could do those changes yourself, it would be great.
> Sorry, I can't.

How come?  You do have commit-access to the repository.


        Stefan