[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#36098: 26.1; Incorrect epg--decode-percent-escape
From: |
Christophe TROESTLER |
Subject: |
bug#36098: 26.1; Incorrect epg--decode-percent-escape |
Date: |
Wed, 5 Jun 2019 17:05:45 +0000 |
On 5 June 2019 at 18:57 CEST, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Christophe TROESTLER <Christophe.TROESTLER@umons.ac.be>
>> CC: "36098@debbugs.gnu.org" <36098@debbugs.gnu.org>
>> Disposition-Notification-To: Christophe TROESTLER
>> <Christophe.TROESTLER@umons.ac.be>
>> Date: Wed, 5 Jun 2019 15:53:23 +0000
>>
>> > Isn't the problem inside epg--decode-percent-escape? I think it
>> > should be fixed there, it shouldn't produce a multibyte string.
>>
>> That's what the patch does.
>
> But you also moved decode-coding-string into that function; is that
> correct? Are we sure the original string was necessarily encoded in
> UTF-8?
This is because this is an internal function and is always called with the same
conversion.
> What I mean was only to let that function return a unibyte string, and
> let the caller perform coding conversions.
I can do that. To avoid repetitions, what about introducing
epg--decode-percent-escape-as-utf-8?