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: Sun, 10 Jan 2021 15:02:27 +0100 [thread overview]
Message-ID: <874kjoc2ks.fsf@lrde.epita.fr> (raw)
In-Reply-To: <wwublglceet.fsf@chaotikum.eu>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> What about the following patch?
>
> @@ -1351,7 +1351,8 @@ nnmaildir-request-article
> - (nnheader-insert-file-contents nnmaildir-article-file-name))
> + (let ((nnheader-file-coding-system nnmail-file-coding-system))
> + (nnheader-insert-file-contents nnmaildir-article-file-name)))
I was playing with something similar this morning:
@@ -1351,7 +1351,9 @@ nnmaildir-request-article
(throw 'return nil))
(with-current-buffer (or to-buffer nntp-server-buffer)
(erase-buffer)
- (nnheader-insert-file-contents nnmaildir-article-file-name))
+ (mm-disable-multibyte)
+ (let ((coding-system-for-read mm-text-coding-system))
+ (nnheader-insert-file-contents nnmaildir-article-file-name)))
(cons gname num-msgid))))
mm-text-coding-system and nnmail-file-coding-system both default
to 'raw-text.
Without (mm-disable-multibyte), the patch makes no difference to me.
The documentation for 'raw-text on
https://www.gnu.org/software/emacs/manual/html_node/emacs/Coding-Systems.html
states that 'raw-text causes enable-multibyte-characters to be set to
nil, but it's not clear when this should occur, and printing
enable-multibyte-characters after the call to
nnheader-insert-file-contents still shows t.
Adding (mm-disable-multibyte) to the patch seems help a lot, although
the first impression is much worse:
1. When a mail is first displayed (using RET or g), the article buffer
is unibyte with all non-ascii characters displayed as backslash
sequences. This occurs for all mails, even QP-encoded ones.
2. When a mail is displayed for the second time (using g on the same
article or RET to change article and come back), the display is
*perfect*. I.e., plain/text and plain/html parts that are encoded
with either utf-8 or windows-1252 are correctly displayed for me.
3. Running M-x gnus-backlog-shutdown gets me back to 1. where
all non-ascii characters are displayed as backslashes.
PS: all of this is with an updated emacs 28, including the reverted
mm-with-part change.
--
Alexandre Duret-Lutz
next prev parent reply other threads:[~2021-01-10 14:02 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
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 [this message]
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=874kjoc2ks.fsf@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.