Re: url issues

[Dave Love]

Stefan <address@hidden> writes:

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

It actually requires an SGML parse, though I can't remember all the
details.  (Note that `sgml-html-meta-auto-coding-function' won't even
work for HTML generated by the current makeinfo.)

> 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.

OK.  It says use it `as a hint', and I thought you were arguing
against believing it.

> Where we disagree is about what to do when that info is
> insufficient/incorrect.

HTTP and HTML define the default charset to be latin-1.  If the
charset is wrong, I don't think there's anything you can do about it
other than obey a coding-system-for-read set by C-x C-m c.

> My experience when using url-handler-mode (which
> is what I'm talking about, remember the function is in url-handlers.el)

Sure.

> 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.

I don't see what you can do other than ignore the specification, and
surely that's wrong.  Anyhow, you need to deal with Content-Encoding
&c.

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

I lost that some time ago, but I can't work on it anyhow.