From: Eli Zaretskii <eliz@gnu.org>
To: Evil Boris <evilborisnet@netscape.net>
Cc: emacs-devel@gnu.org
Subject: Re: Rmail-mbox branch
Date: Mon, 01 Sep 2008 22:19:03 +0300 [thread overview]
Message-ID: <umyir8yjc.fsf@gnu.org> (raw)
In-Reply-To: <84abesum0g.fsf@boris.laptop>
> From: Evil Boris <evilborisnet@netscape.net>
> Date: Mon, 01 Sep 2008 07:46:23 -0400
>
> I guess in absense of such support (and hoping etach or equivalent will
> magically support mbox format :-), my main concern would be handling of
> different character sets (Unicode, ISO-8859-x, KOI8-R, are most popular)
> in plain text msgs, so that I can see the text without jumping through
> hoops.
I don't see why the mbox branch would support this any worse than the
trunk. The decoding stuff is pretty much stable and well understood,
after so many releases.
> PS. Reading a multipart/alternative email with a text/plain component
> encoded in quoted-printable [in a non-latin-based character set] or
> base64 is currently a pain, as I have to detach and then play around
> with decoding the character set in the raw RMAIL file...
??? For me, it's as easy as
. Type 'e' to make the message editable
. Make region around the attachment
. For base64-encoded attachments:
M-x base64-decode-region RET
. For quoted-printable:
M-: (mail-unquote-printable-region (mark) (point) nil nil t) RET
. C-c (to exit rmail-edit)
. M-x rmail-redecode-body RET CHARSET-NAME RET
where CHARSET-NAME is whatever appears in the charset= header of the
attachment, if different from US-ASCII.
(Of course, the above are just the primitives; wrapping them with a
single command is left as an exercise for the interested readers.)
next prev parent reply other threads:[~2008-09-01 19:19 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 18:05 Rmail-mbox branch Chong Yidong
2008-06-30 12:20 ` Paul Michael Reilly
2008-06-30 13:06 ` Chong Yidong
2008-06-30 13:50 ` Paul Michael Reilly
2008-06-30 13:59 ` Miles Bader
2008-06-30 15:57 ` Stefan Monnier
[not found] ` <4868F9F0.2060408@pajato.com>
2008-06-30 18:29 ` Miles Bader
2008-06-30 16:03 ` Stefan Monnier
2008-06-30 17:48 ` Paul Michael Reilly
2008-07-03 21:56 ` Stefan Monnier
2008-08-18 5:15 ` Paul Michael Reilly
2008-08-18 6:01 ` Miles Bader
2008-08-18 6:05 ` Paul Michael Reilly
2008-08-18 6:52 ` Miles Bader
2008-08-18 12:18 ` Paul Michael Reilly
2008-08-29 7:04 ` Glenn Morris
2008-08-31 4:27 ` Paul Michael Reilly
2008-08-31 18:50 ` Chong Yidong
2008-08-31 19:15 ` Evil Boris
2008-09-01 3:09 ` Eli Zaretskii
2008-09-01 11:46 ` Evil Boris
2008-09-01 19:19 ` Eli Zaretskii [this message]
2008-09-01 19:57 ` Stefan Monnier
2008-09-02 3:21 ` Eli Zaretskii
2008-09-01 23:46 ` Evil Boris
2008-09-02 2:38 ` Evil Boris
2008-09-02 3:32 ` Eli Zaretskii
2008-09-02 11:53 ` Evil Boris
2008-09-03 20:12 ` Paul Michael Reilly
2008-09-02 14:13 ` Richard M. Stallman
2008-09-03 2:46 ` Stephen J. Turnbull
2008-09-03 4:41 ` Richard M. Stallman
2008-09-03 6:28 ` Stephen J. Turnbull
2008-09-04 0:10 ` Richard M. Stallman
2008-09-04 2:26 ` Stephen J. Turnbull
2008-09-04 7:03 ` Paul Michael Reilly
2008-09-04 8:44 ` Stephen J. Turnbull
2008-09-04 13:58 ` Stefan Monnier
2008-09-04 21:58 ` Paul Michael Reilly
2008-09-04 15:58 ` Eli Zaretskii
2008-09-04 22:00 ` Paul Michael Reilly
2008-09-05 2:20 ` Richard M. Stallman
2008-09-05 5:33 ` Stephen J. Turnbull
2008-09-06 21:05 ` Richard M. Stallman
2008-09-08 4:57 ` Stephen J. Turnbull
2008-09-08 8:36 ` Francesco Potorti`
2008-09-08 9:53 ` Stephen J. Turnbull
2008-09-08 13:03 ` Stefan Monnier
2008-09-09 1:58 ` Stephen J. Turnbull
2008-09-08 19:15 ` Eli Zaretskii
2008-09-08 16:42 ` Richard M. Stallman
2008-09-08 17:55 ` David De La Harpe Golden
2008-09-09 2:54 ` Stephen J. Turnbull
2008-09-09 14:11 ` Richard M. Stallman
2008-09-10 9:10 ` Stephen J. Turnbull
2008-09-10 11:43 ` Paul Michael Reilly
2008-09-10 12:23 ` tomas
2008-09-10 17:55 ` Stefan Monnier
2008-09-11 2:39 ` Stephen J. Turnbull
2008-09-10 15:07 ` David De La Harpe Golden
2008-09-03 16:08 ` Stefan Monnier
2008-09-03 19:56 ` Paul Michael Reilly
2008-09-04 0:45 ` Kenichi Handa
2008-09-04 4:35 ` Stefan Monnier
2008-09-04 2:36 ` Stephen J. Turnbull
2008-09-04 7:27 ` Paul Michael Reilly
2008-09-02 3:28 ` Eli Zaretskii
2008-09-01 6:11 ` Richard M. Stallman
2008-09-01 8:42 ` Francesco Potorti`
2008-09-01 11:25 ` Evil Boris
2008-09-01 19:39 ` Paul Michael Reilly
2008-09-01 20:20 ` Chong Yidong
2008-09-01 20:52 ` Stefan Monnier
2008-09-02 1:09 ` Richard M. Stallman
2008-09-02 3:29 ` Eli Zaretskii
2008-09-03 2:41 ` Richard M. Stallman
2008-09-03 3:17 ` Eli Zaretskii
2008-09-03 19:46 ` Paul Michael Reilly
2008-09-03 20:20 ` Chong Yidong
2008-09-03 23:37 ` Glenn Morris
2008-09-04 0:10 ` Richard M. Stallman
2008-09-02 19:17 ` Paul Michael Reilly
2008-09-01 1:06 ` Glenn Morris
2008-09-01 19:19 ` Paul Michael Reilly
2008-08-19 4:31 ` Chong Yidong
2008-08-19 7:15 ` Paul Michael Reilly
2008-08-20 16:27 ` Stefan Monnier
2008-08-21 13:55 ` Paul Michael Reilly
2008-08-27 15:47 ` Stefan Monnier
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=umyir8yjc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=evilborisnet@netscape.net \
/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).