Re: bug#23750: 25.0.95; bug in url-retrieve or json.el

[Dmitry Gutov]

On 02.12.2016 17:48, Lars Ingebrigtsen wrote:
> Dmitry Gutov <address@hidden> writes:
>
> > On 02.12.2016 17:29, Lars Ingebrigtsen wrote:
> >
> > > This is going to break many current callers.  Most people aren't doing
> > > anything as weird as trying to transmit non-ASCII text via any of these
> > > headers (it's a very uncommon thing to do), but are just passing in
> > > normal Emacs strings (containing nothing by ASCII, as is proper).
> >
> > Do you have some examples?
>
> (multibyte-string-p (symbol-name 'a))
> => t

Examples of things "most people" are doing "trying to transmit" "nothing 
but ASCII" using the URL package, please.

> > I'm sure a well-defined interface will need to have a required
> > "encoding" step, or an argument somewhere, at least.
>
> Yes, of course.  The interface will allow the caller to specify the
> charset of the data.

And at least make it clear that the parameter with default to UTF-8, right?