From: Ricardo Wurmus <rekado@elephly.net>
To: 49115@debbugs.gnu.org
Cc: guile-email@systemreboot.net
Subject: Mumi inserts spurious underscore in bug title
Date: Sat, 24 Dec 2022 23:53:02 +0100 [thread overview]
Message-ID: <87y1qwbdlr.fsf@elephly.net> (raw)
> See http://issues.guix.gnu.org/49114, which Mumi currently
> titles
>
> ‘guix_ lint’ should catch certificate validation exceptions
>
> There's no underscore in the original subject.
The debbugs “.log” file for issue 49114 contains this line:
Subject: bug#49114: =?UTF-8?Q?=E2=80=98guix_?= =?UTF-8?Q?lint=E2=80=99?= should catch certificate validation exceptions
This is MIME Q encoding (similar to “quoted printable” encoding), as
specified in RFC 2047.
The underscore is mentioned in 4.2 (2):
(2) The 8-bit hexadecimal value 20 (e.g., ISO-8859-1 SPACE) may be
represented as "_" (underscore, ASCII 95.). (This character may
not pass through some internetwork mail gateways, but its use
will greatly enhance readability of "Q" encoded data with mail
readers that do not support this encoding.) Note that the "_"
always represents hexadecimal 20, even if the SPACE character
occupies a different code position in the character set in use.
So, the underscore above ought to be replaced with a space. This seems
to be a bug in guile-email.
--
Ricardo
next reply other threads:[~2022-12-24 23:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 22:53 Ricardo Wurmus [this message]
2022-12-29 19:36 ` Arun Isaac
2023-01-01 12:15 ` Ricardo Wurmus
2023-01-02 17:43 ` [PATCH 0/1] Do not check for MIME encoded words Arun Isaac
2023-01-02 17:43 ` [PATCH 1/1] debbugs: Do not check for MIME encoded words in subject Arun Isaac
2023-01-02 19:34 ` Ricardo Wurmus
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=87y1qwbdlr.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=49115@debbugs.gnu.org \
--cc=guile-email@systemreboot.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox