all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alexandre Duret-Lutz <adl@lrde.epita.fr>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44307@debbugs.gnu.org
Subject: bug#44307: 27.1; UTF-8 parts transferred as 8bit in multipart messages fail to decode
Date: Tue, 05 Jan 2021 12:17:38 +0100	[thread overview]
Message-ID: <87czyjfx9p.fsf@goulash.lrde.epita.fr> (raw)
In-Reply-To: <87turv1yhw.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 05 Jan 2021 11:14:51 +0100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Alexandre Duret-Lutz <adl@lrde.epita.fr> writes:
>
>> Here is the file.  But see by previous message from today.  Reading this
>> with nndoc will appear bogus with emacs 27.1, but not with emacs 28.
>> However if there is a way to read that mail with nnmaildir, you should
>> see the issue with both versions.
>
> Thanks for the test file (and the analysis of the differences between
> 27.1 and 28 here).  I'll try to work on fix for this in Emacs 27
> tomorrow -- I'm not sure the simple fix you outlined won't have adverse
> effects if the part in question is binary (i.e., an image or the like).

Sorry, you can ignore my simple "fix": I have now found a case that it
breaks.

I was testing mainly on utf-8 messages.  But I've now looked (through
nnmaildir) at a mail containing a part encoded as follow:

Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

However the rendering was garbled.  Looking ag the output of "C-u g" I
can see that the buffer contains utf-8 code (I'm guessing because that
the windows-1252 representation was decoded when nnmaildir read the mail
from file), and that will make no sense once Gnus attempts to decode
that in windows-1252.

Without my incorrect patch, displaying such an email would appear to
work (by luck?), because when mm-with-part inserts the multibyte buffer
into the unibyte buffer, the utf-8 characters are somehow converted to
their windows-1252 equivalent encoding.

I guess the real issue is that mmaildir does not correctly deal with
multibyte files et may return multibyte buffer, just like nndoc used to.
-- 
Alexandre Duret-Lutz





  reply	other threads:[~2021-01-05 11:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 14:09 bug#44307: 27.1; UTF-8 parts transferred as 8bit in multipart messages fail to decode Thomas Schneider
2020-10-30 13:10 ` Lars Ingebrigtsen
2020-10-30 13:26   ` Andreas Schwab
2020-10-30 13:35     ` Lars Ingebrigtsen
2020-10-30 14:53       ` Andreas Schwab
2020-11-01 12:10         ` Lars Ingebrigtsen
2020-11-01 12:15           ` Andreas Schwab
2020-11-02 14:56             ` Lars Ingebrigtsen
2020-10-30 13:28 ` Andreas Schwab
2021-01-02 20:26 ` Alexandre Duret-Lutz
2021-01-04 21:54   ` Alexandre Duret-Lutz
2021-01-05 10:00     ` Alexandre Duret-Lutz
2021-01-07 13:43       ` Lars Ingebrigtsen
2021-01-05  9:30   ` Lars Ingebrigtsen
2021-01-05 10:07     ` Alexandre Duret-Lutz
2021-01-05 10:14       ` Lars Ingebrigtsen
2021-01-05 11:17         ` Alexandre Duret-Lutz [this message]
2021-01-07 14:14       ` Lars Ingebrigtsen
2021-01-07 16:06         ` Alexandre Duret-Lutz
2021-01-07 16:10           ` Lars Ingebrigtsen
2021-01-07 17:07             ` Alexandre Duret-Lutz
2021-01-10 12:27           ` Lars Ingebrigtsen
2021-01-10 14:02             ` Alexandre Duret-Lutz
2021-01-10 14:11               ` Lars Ingebrigtsen
2021-01-10 14:48                 ` Alexandre Duret-Lutz
2021-01-10 15:21                   ` Alexandre Duret-Lutz
2021-01-11 14:28                     ` Lars Ingebrigtsen
2021-02-02 11:36                       ` Alexandre Duret-Lutz
2021-02-04  8:04                         ` Lars Ingebrigtsen

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=87czyjfx9p.fsf@goulash.lrde.epita.fr \
    --to=adl@lrde.epita.fr \
    --cc=44307@debbugs.gnu.org \
    --cc=larsi@gnus.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.