[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: eww doesn't decode %AA%BB%CC URL names
From: |
Eli Zaretskii |
Subject: |
Re: eww doesn't decode %AA%BB%CC URL names |
Date: |
Thu, 24 Dec 2015 22:40:09 +0200 |
> From: Lars Ingebrigtsen <address@hidden>
> Cc: address@hidden, address@hidden
> Date: Thu, 24 Dec 2015 20:55:13 +0100
>
> > I think you should use UTF-8 literally as the first choice.
>
> Right. How do I check whether the bytes are a valid utf-8 sequence,
> though? I thought I remembered something called
> `valid-something-something-p', but I can't find it now...
I think you can run find-charset-string on the decoded string, and if
the result is just (unicode), you can be sure.
- 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, 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, Eli Zaretskii, 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/25
- Re: eww doesn't decode %AA%BB%CC URL names, Lars Ingebrigtsen, 2015/12/25