From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: yuri.v.khan@gmail.com, suzume@protonmail.com, emacs-devel@gnu.org
Subject: Re: Encoding issue in the digest (Re: Emacs-devel Digest, Vol 240, Issue 25)
Date: Wed, 28 Feb 2024 15:40:23 +0200 [thread overview]
Message-ID: <861q8wu2pk.fsf@gnu.org> (raw)
In-Reply-To: <87msrk1zw3.fsf@igel.home> (message from Andreas Schwab on Wed, 28 Feb 2024 14:28:44 +0100)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, "suzume@protonmail.com"
> <suzume@protonmail.com>, emacs-devel@gnu.org
> Date: Wed, 28 Feb 2024 14:28:44 +0100
>
> On Feb 28 2024, Yuri Khan wrote:
>
> > I think the operative word here is “digest”. The above encoded string
> > is quoted not from the Subject header field on an individual message
> > but from the body of a message that combines multiple mailing list
> > messages.
>
> The non-digest message that was received by the mailing list has exactly
> the same encoded subject header, so the digest context does not change
> anything here.
Right, I see that as well.
So I guess if the subject is not correctly encoded, the culprit is the
MUA used by Jean-Christophe, or maybe some of the MTA servers on the
way between his MUA and us the recipients.
prev parent reply other threads:[~2024-02-28 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.47.1708880407.9373.emacs-devel@gnu.org>
2024-02-28 0:18 ` Encoding issue in the digest (Re: Emacs-devel Digest, Vol 240, Issue 25) suzume
2024-02-28 12:09 ` Eli Zaretskii
[not found] ` <2DD5484A-C4DB-47AA-9690-D8C6ED1F0727@protonmail.com>
2024-02-28 12:20 ` Eli Zaretskii
2024-02-28 12:23 ` Jean-Christophe Helary
2024-02-28 12:32 ` tomas
2024-02-28 13:02 ` Kazuhiro Ito
2024-02-28 12:31 ` tomas
2024-02-28 12:54 ` Yuri Khan
2024-02-28 12:58 ` Jean-Christophe Helary
2024-02-28 13:01 ` tomas
2024-02-28 13:28 ` Andreas Schwab
2024-02-28 13:40 ` Eli Zaretskii [this message]
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=861q8wu2pk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.org \
--cc=suzume@protonmail.com \
--cc=yuri.v.khan@gmail.com \
/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.