GNU bug report logs - #39689
26.3; browse-url-mail not supporting RFC6068 (UTF-8-Based Percent-Encoding)

Previous Next

Package: emacs;

Reported by: Vegard Vesterheim <vegard.vesterheim <at> uninett.no>

Date: Thu, 20 Feb 2020 13:49:01 UTC

Severity: normal

Found in version 26.3

Fixed in version 28.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Robert Pluim <rpluim <at> gmail.com>
To: Vegard Vesterheim <vegard.vesterheim <at> uninett.no>
Cc: 39689 <at> debbugs.gnu.org, larsi <at> gnus.org
Subject: bug#39689: 26.3; browse-url-mail not supporting RFC6068 (UTF-8-Based Percent-Encoding)
Date: Thu, 27 Feb 2020 11:51:35 +0100

>>>>> On Thu, 20 Feb 2020 14:48:54 +0100, Vegard Vesterheim via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org> said:

    Vegard> Emacs does not seem to correctly handle UTF-8-Based Percent-Encoding as
    Vegard> illustrated in Chapter 6.2 from RFC6068.

    Vegard> The command 
    Vegard>    emacs -Q -l browse-url -eval '(browse-url-mail "mailto:user <at> example.org?subject=caf%C3%A9&body=caf%C3%A9")'

    Vegard> should result in a message buffer with the string "café" insterted into the
    Vegard> body part of the message. Instead the string "café" is inserted.

Yes, the assumption in rfc2368-unhexify-string is that percent
escaping is being done of ASCII characters.

epg--decode-percent-escape-as-utf-8 in epg.el does the
right thing, it could be renamed and moved. I think rfc2047 decoding
needs doing on the result as well. Lars, should I just stick these in
rfc2368.el but named something like rfc6068-unhexify-string and
rfc6068-decode-2047-string or something?

Robert
This bug report was last modified 3 years and 261 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.