Re: [Emacs-diffs] emacs-25 2e524034: ; * etc/NEWS: Mention incompatible change in url-http-create-request.

Re: [Emacs-diffs] emacs-25 2e524034: ; * etc/NEWS: Mention incompatible change in url-http-create-request.

[Dmitry Gutov]

On 08/17/2016 05:41 AM, Eli Zaretskii wrote:

> If non-ASCII characters should be part of the URL
> +payload, then `url-request-data' should be encoded to become a unibyte
> +string.

And if not? Multibyte strings with ASCII-only characters are still not 
allowed.

Re: [Emacs-diffs] emacs-25 2e524034: ; * etc/NEWS: Mention incompatible change in url-http-create-request.

[Dmitry Gutov]

On 08/17/2016 06:53 AM, Dmitry Gutov wrote:
> On 08/17/2016 05:41 AM, Eli Zaretskii wrote:
>
>> If non-ASCII characters should be part of the URL
>> +payload, then `url-request-data' should be encoded to become a unibyte
>> +string.
>
> And if not? Multibyte strings with ASCII-only characters are still not
> allowed.

Or maybe they are. Sorry for the alarm.

Re: [Emacs-diffs] emacs-25 2e524034: ; * etc/NEWS: Mention incompatible change in url-http-create-request.

[Andreas Schwab]

On Aug 17 2016, Dmitry Gutov <dgutov@yandex.ru> wrote:

> And if not? Multibyte strings with ASCII-only characters are still not
> allowed.

Multibyte strings by definition contain non-ASCII characters.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

Re: [Emacs-diffs] emacs-25 2e524034: ; * etc/NEWS: Mention incompatible change in url-http-create-request.

[Andreas Schwab]

On Aug 17 2016, Andreas Schwab <schwab@suse.de> wrote:

> Multibyte strings by definition contain non-ASCII characters.

Of course, this is wrong, sorry.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

Re: [Emacs-diffs] emacs-25 2e524034: ; * etc/NEWS: Mention incompatible change in url-http-create-request.

[Eli Zaretskii]

> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Wed, 17 Aug 2016 07:07:04 +0300
> 
> On 08/17/2016 06:53 AM, Dmitry Gutov wrote:
> > On 08/17/2016 05:41 AM, Eli Zaretskii wrote:
> >
> >> If non-ASCII characters should be part of the URL
> >> +payload, then `url-request-data' should be encoded to become a unibyte
> >> +string.
> >
> > And if not? Multibyte strings with ASCII-only characters are still not
> > allowed.
> 
> Or maybe they are.

Right, because the number of bytes in a pure-ASCII string is identical
to the number of characters, no matter if the string is unibyte or
multibyte.