bug#16733: messed up unicode chars in package description

[Juanma Barranquero]

On Thu, Mar 20, 2014 at 5:21 PM, Eli Zaretskii <eliz@gnu.org> wrote:

> This is suboptimal when the URL already tells its charset.  In that
> case, you should use the information; you should fall back to
> detect-coding-string only if that information is not available.

That would mean to manually parse the headers and/or duplicate part of
what url-insert / url-insert-file-contents do. In that case, I'd
prefer one of the other fixes.

   J