From: Eli Zaretskii <eliz@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: 7626@debbugs.gnu.org
Subject: bug#7626: bug#7651: 23.2.91; Rmail doesn't allow displaying text attachments conveniently
Date: Thu, 13 Jan 2011 07:12:33 -0500 [thread overview]
Message-ID: <E1PdM2b-00011L-Cr@fencepost.gnu.org> (raw)
In-Reply-To: <tl7lj2pha3m.fsf@m17n.org> (message from Kenichi Handa on Thu, 13 Jan 2011 10:21:33 +0900)
> From: Kenichi Handa <handa@m17n.org>
> Cc: 7626@debbugs.gnu.org
> Date: Thu, 13 Jan 2011 10:21:33 +0900
>
> I found that rfc2047-decode-region (called while preparing
> the message header) sets last-coding-system-used to
> windows-1252. That is because mm-util.el defines
> mm-charset-override-alist as this:
>
> '((gb2312 . gbk)
> (iso-8859-1 . windows-1252)
> (iso-8859-8 . windows-1255)
> (iso-8859-9 . windows-1254))
>
> And explains it as this:
>
> i.e. treat iso-8859-1 as windows-1252. windows-1252 is a
> superset of iso-8859-1."
I guess this is because some broken mailers state Latin-N while
actually using the corresponding Windows codepage, and when the
message includes characters not in Latin-N, they are not displayed
correctly.
But even if we keep this "feature" (see below for an alternative
suggestion), I don't see a need to force this on users. We should
have a user option to do this. Personally, I think it should be off
by default, but if someone feels strongly about that, I won't mind
having it on by default, in which case I will customize it on my
system.
> At the moment, I don't know how (or where) to fix this
> problem, but at least, it seems that setting
> buffer-file-coding-system to windows-1252 for iso-8859-1
> message won't cause an actual problem.
It's surprising and kludgey, IMO. A better solution would be to
decode by windows-12XX, but set last-coding-system-used to Latin-N.
That way, only if I reuse the text that is not encodable by Latin-N, I
will need to do something. Otherwise, I get to have the cake and eat
it, too.
next prev parent reply other threads:[~2011-01-13 12:12 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 6:15 bug#7651: 23.2.91; Rmail doesn't allow displaying text attachments conveniently Eli Zaretskii
2010-12-16 7:08 ` Kenichi Handa
2010-12-16 17:33 ` Eli Zaretskii
2010-12-17 15:28 ` Eli Zaretskii
2010-12-24 4:50 ` Kenichi Handa
2010-12-24 8:17 ` Andreas Schwab
2010-12-24 11:22 ` Kenichi Handa
2010-12-27 11:08 ` Kenichi Handa
2010-12-30 12:39 ` Chong Yidong
2011-01-04 5:36 ` Kenichi Handa
2011-01-04 6:35 ` Eli Zaretskii
2011-01-01 11:00 ` Eli Zaretskii
2011-01-01 15:26 ` Eli Zaretskii
2011-01-04 7:16 ` Kenichi Handa
2011-01-04 5:01 ` Kenichi Handa
2011-01-04 6:34 ` Eli Zaretskii
2011-01-07 7:13 ` Kenichi Handa
2011-01-07 7:53 ` Eli Zaretskii
2011-01-12 6:22 ` Kenichi Handa
2011-01-12 10:57 ` bug#7626: " Eli Zaretskii
2011-01-13 1:21 ` Kenichi Handa
2011-01-13 12:12 ` Eli Zaretskii [this message]
2011-01-14 4:23 ` Kenichi Handa
2011-01-18 8:07 ` bug#7626: mm-charset-override-alist (was: bug#7626: bug#7651: 23.2.91; Rmail doesn't allow displaying text attachments conveniently) Reiner Steib
2011-01-18 15:10 ` Eli Zaretskii
2011-01-18 18:00 ` bug#7626: mm-charset-override-alist Stefan Monnier
2011-01-19 21:23 ` Reiner Steib
2011-01-20 0:40 ` Eli Zaretskii
2011-01-20 1:57 ` Stefan Monnier
2011-01-20 2:08 ` Eli Zaretskii
2011-01-20 15:32 ` Stefan Monnier
2011-01-20 15:37 ` Eli Zaretskii
2011-01-20 2:05 ` Kenichi Handa
2011-01-20 2:12 ` Eli Zaretskii
2011-01-20 3:51 ` Kenichi Handa
2011-02-05 13:36 ` Eli Zaretskii
2011-02-07 0:45 ` Kenichi Handa
[not found] ` <8339o0ts6k.fsf@gnu.org>
2011-02-07 5:36 ` Kenichi Handa
2011-02-07 6:07 ` Eli Zaretskii
2011-10-07 0:32 ` Glenn Morris
2011-10-07 12:14 ` Eli Zaretskii
2011-01-20 2:27 ` Eli Zaretskii
2011-01-12 10:58 ` bug#7651: 23.2.91; Rmail doesn't allow displaying text attachments conveniently Eli Zaretskii
2011-10-19 7:56 ` 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=E1PdM2b-00011L-Cr@fencepost.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 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).