unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Encoding issue in the digest (Re: Emacs-devel Digest, Vol 240, Issue 25)
Date: Wed, 28 Feb 2024 12:58:50 +0000	[thread overview]
Message-ID: <32B38B26-4426-47A7-AFB7-188A4BB8E01D@traductaire-libre.org> (raw)
In-Reply-To: <CAP_d_8Vm59=G9gXEnd27xA6u1aBsaPmUdd-N88x=5F6-Ok8TsA@mail.gmail.com>



> On Feb 28, 2024, at 21:54, Yuri Khan <yuri.v.khan@gmail.com> wrote:
> 
> On Wed, 28 Feb 2024 at 19:21, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>>>>>> Subject:
>>>>>>  =?utf-8?Q?Traduction_fran=C3=A7aise_des_manuels_d=E2=80=99Emacs,
>>>>>>  _=C3=A9tat_des_lieux.?=
> 
>>> This is how it looks in the digest listing here:
>> 
>> Which is okay, I think.  That's how the author's MUA sent it; the
>> Subject is encoded using quoted-printable method, I think.
>> 
>> Maybe something is wrong here, then.  I'm not an expert on this stuff;
>> does anyone know whether this Subject encoding is OK or not?
> 
> I think the operative word here is “digest”.

Indeed.

> 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.

That's correct.

> In the ideal world, the server software producing digests will take
> each individual message, decode its subject according to the encoding
> declared, decode the body according to the Content-Type: text/plain;
> charset= header, build the digest in Unicode land, then encode to
> UTF-8 and mail that to digest subscribers.
> 
> I’m suspecting the digest formatter might not be MIME-aware with
> respect to subject encoding.

Is that something that we need to report to the GNU project? Other 
mailman lists that I use don't seem to have that issue.



  reply	other threads:[~2024-02-28 12:58 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 [this message]
2024-02-28 13:01           ` tomas
2024-02-28 13:28           ` Andreas Schwab
2024-02-28 13:40             ` 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=32B38B26-4426-47A7-AFB7-188A4BB8E01D@traductaire-libre.org \
    --to=jean.christophe.helary@traductaire-libre.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).