Re: address@hidden: [patch] url-hexify-string does not follow W3C spec]

[Kenichi Handa]

In article <address@hidden>, Stefan Monnier <address@hidden> writes:

>>> What incompatibility?  If the string only contains ASCII and
>>> eight-bit-*, then encoding it with utf-8 will return the same string
>>> of bytes (except in a unibyte string rather than multibyte string).

>> Here's an example:

>> (encode-coding-string "\x80" 'utf-8)
>> => "\302\200"

> Duh!  Looks like a serious bug to me.
> Handa-san, what's up with that?

??? \x80 == U+0080 is a valid Unicode character in "C1
Controls" block.

However, I agree that the following is very questionable
behaviour:

>> (encode-coding-string (string-as-unibyte "\x80") 'utf-8)
>> => "\302\200"

But, that is a long standing problem, and should be fixed
(if necessary) after the release.

---
Kenichi Handa
address@hidden