[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: eww doesn't decode %AA%BB%CC URL names
From: |
Yuri Khan |
Subject: |
Re: eww doesn't decode %AA%BB%CC URL names |
Date: |
Fri, 25 Dec 2015 00:07:40 +0600 |
On Thu, Dec 24, 2015 at 11:40 PM, Lars Ingebrigtsen <address@hidden> wrote:
> (decode-coding-string (url-unhex-string
> "%D0%A1%D0%B5%D1%80%D0%B4%D1%86%D0%B5")
> 'utf-8)
> => "Сердце"
>
> Right. What charset do we choose? I guess using the charset of the
> document we're in doesn't make much sense (because it's linking to
> something off-site which may be in a different charset)...
By RFC 3986, percent-encoded URLs SHOULD use UTF-8 encoding. If the
URL does not decode into a valid UTF-8 string, it is ok to fall back
to a heuristic, though.
- Re: eww doesn't decode %AA%BB%CC URL names, Lars Ingebrigtsen, 2015/12/24
- Re: eww doesn't decode %AA%BB%CC URL names,
Yuri Khan <=
- Re: eww doesn't decode %AA%BB%CC URL names, Eli Zaretskii, 2015/12/24
- Re: eww doesn't decode %AA%BB%CC URL names, Lars Ingebrigtsen, 2015/12/24
- Re: eww doesn't decode %AA%BB%CC URL names, Eli Zaretskii, 2015/12/24
- Re: eww doesn't decode %AA%BB%CC URL names, Lars Ingebrigtsen, 2015/12/24
- Re: eww doesn't decode %AA%BB%CC URL names, Eli Zaretskii, 2015/12/24
- Re: eww doesn't decode %AA%BB%CC URL names, Lars Ingebrigtsen, 2015/12/24
- Re: eww doesn't decode %AA%BB%CC URL names, Lars Ingebrigtsen, 2015/12/24
- Re: eww doesn't decode %AA%BB%CC URL names, Eli Zaretskii, 2015/12/24
- Re: eww doesn't decode %AA%BB%CC URL names, Lars Ingebrigtsen, 2015/12/24
- Re: eww doesn't decode %AA%BB%CC URL names, Eli Zaretskii, 2015/12/24