From: Eli Zaretskii <eliz@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: 7626@debbugs.gnu.org
Subject: bug#7626: 23.2.91; Rmail shows incorrect message encoding in the mode line
Date: Sat, 01 Jan 2011 13:20:38 +0200 [thread overview]
Message-ID: <83tyhsq395.fsf@gnu.org> (raw)
In-Reply-To: <83ei9miqef.fsf@gnu.org>
The new Rmail/Rmail-MIME code (revision 100323 on the emacs-23 branch)
solved most of the problems originally reported here, but it still has
some issues. Here are the problems I see with the new code, based on
less than an hour of testing:
. If the message has an explicit specification of its charset, the
EOL type of the RMAIL buffer is left unspecified (displayed as `:'
in the mode line). By contrast, when there's no charset= spec, the
EOL type is correctly set to -unix.
. Sometimes, the RMAIL buffer's encoding is set to windows-1252,
which is not present anywhere in the message headers. The only
source of non-ASCII characters in the 2 messages where I saw this
problem was in the RFC 2047 encoded addresses, but those used
8859-1, as in "Jan =?iso-8859-1?Q?Dj=E4rv?=", not windows-1252.
`describe-text-properties' indeed shows the charset of the decoded
address as windows-1252, so the reason is probably somewhere in
`rfc2047-decode-region'.
Thanks.
next prev parent reply other threads:[~2011-01-01 11:20 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
2010-12-13 3:47 ` Eli Zaretskii
2011-01-01 11:20 ` Eli Zaretskii [this message]
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=83tyhsq395.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=7626@debbugs.gnu.org \
--cc=handa@m17n.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.