From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: rmailmime.el Date: Mon, 31 Dec 2007 09:42:46 -0500 Message-ID: References: <200712261620.BAA23474@latour.cad.ci.kyutech.ac.jp> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: ger.gmane.org 1199112224 19507 80.91.229.12 (31 Dec 2007 14:43:44 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 31 Dec 2007 14:43:44 +0000 (UTC) Cc: emacs-devel@gnu.org To: umerin@ci.kyutech.ac.jp Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 31 15:43:52 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1J9Lrs-0000Uh-1U for ged-emacs-devel@m.gmane.org; Mon, 31 Dec 2007 15:43:52 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J9LrV-0005pK-DI for ged-emacs-devel@m.gmane.org; Mon, 31 Dec 2007 09:43:29 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J9Lqr-0005Y9-86 for emacs-devel@gnu.org; Mon, 31 Dec 2007 09:42:49 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J9Lqp-0005XG-Df for emacs-devel@gnu.org; Mon, 31 Dec 2007 09:42:48 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J9Lqp-0005X5-8a for emacs-devel@gnu.org; Mon, 31 Dec 2007 09:42:47 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J9Lqp-0001Mf-2K for emacs-devel@gnu.org; Mon, 31 Dec 2007 09:42:47 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1J9Lqo-0007PD-5H; Mon, 31 Dec 2007 09:42:46 -0500 In-reply-to: <200712261620.BAA23474@latour.cad.ci.kyutech.ac.jp> (message from Masanobu UMEDA on Thu, 27 Dec 2007 01:20:37 +0900) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:85737 Archived-At: Following your idea will work well for text/plan of us-ascii charset in 7bit transfer-encoding. In case of quoted-printable or base64 encoding, or non-us-ascii charsets, even if a message is text/plain, it should be decoded and internalized according to its designated charset to display it in an Emacs buffer. In some cases it can be decoded in the current buffer. The very simple mime-handler I use does that for quoted-printable. For base64, by contrast, it puts the attachment text into another buffer. I decided to do it that way because the things that are encoded in base64 are often not text at all; they are jpeg or pdf, for instance. But if we use metamail to handle the other formats in a special way, then text which is encoded in base64 could be decoded in the same buffer.