From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 7626@debbugs.gnu.org
Subject: bug#7626: 23.2.91; Rmail shows incorrect message encoding in the mode line
Date: Mon, 13 Dec 2010 09:29:01 +0900 [thread overview]
Message-ID: <tl739q2348i.fsf@m17n.org> (raw)
In-Reply-To: <83ei9miqef.fsf@gnu.org> (message from Eli Zaretskii on Mon, 13 Dec 2010 00:21:12 +0200)
In article <83ei9miqef.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> The new rmail-mime feature causes Rmail to set
> buffer-file-coding-system to an incorrect value. Expected result:
> buffer-file-coding-system is according to the charset= header, but in
> fact buffer-file-coding-system is almost always set to undecided.
> This is a regression from Emacs 23.2.90.
> Also, once the headers were decoded by rfc2047-decode-region, it would
> be good to set buffer-file-coding-system to last-coding-system-used,
> if the buffer's encoding is still undecided.
I'm now working on various bug-fixing and improvement of
rmail's mime handling, and fixing the above is included in
the work. The problem is that which coding system to set if
the header and each text part of multipart have different
"charset". At the moment, I'm going to commit a code that
set the FIRST coding system used for decoding some part
(header, parts of multipart, forwarded message, etc).
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2010-12-13 0:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 22:21 bug#7626: 23.2.91; Rmail shows incorrect message encoding in the mode line Eli Zaretskii
2010-12-13 0:29 ` Kenichi Handa [this message]
2010-12-13 3:47 ` Eli Zaretskii
2011-01-01 11:20 ` Eli Zaretskii
2011-01-14 4:28 ` Kenichi Handa
2011-01-14 17:22 ` Eli Zaretskii
2011-01-17 1:22 ` Kenichi Handa
2011-01-17 11:06 ` Eli Zaretskii
2011-01-17 11:35 ` Kenichi Handa
2011-01-17 12:24 ` Eli Zaretskii
2011-01-18 11:44 ` Kenichi Handa
2011-01-18 15:23 ` Eli Zaretskii
2011-01-20 3:53 ` Kenichi Handa
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=tl739q2348i.fsf@m17n.org \
--to=handa@m17n.org \
--cc=7626@debbugs.gnu.org \
--cc=eliz@gnu.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.