From: Christophe TROESTLER <Christophe.TROESTLER@umons.ac.be>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "36098@debbugs.gnu.org" <36098@debbugs.gnu.org>
Subject: bug#36098: 26.1; Incorrect epg--decode-percent-escape
Date: Wed, 5 Jun 2019 17:05:45 +0000 [thread overview]
Message-ID: <87pnns3qtz.fsf@poincare.umons.ac.be> (raw)
In-Reply-To: <83lfygrmus.fsf@gnu.org>
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?
next prev parent reply other threads:[~2019-06-05 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 13:49 bug#36098: 26.1; Incorrect epg--decode-percent-escape Christophe TROESTLER
2019-06-05 14:49 ` Eli Zaretskii
2019-06-05 15:53 ` Christophe TROESTLER
2019-06-05 16:57 ` Eli Zaretskii
2019-06-05 17:05 ` Christophe TROESTLER [this message]
2019-06-05 17:29 ` Eli Zaretskii
2019-06-05 18:12 ` Christophe TROESTLER
2019-06-22 9:26 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnns3qtz.fsf@poincare.umons.ac.be \
--to=christophe.troestler@umons.ac.be \
--cc=36098@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.