From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Alexander Pohoyda Newsgroups: gmane.emacs.devel Subject: Re: [rmail-mbox-branch]: mail-utils Date: 09 Oct 2004 01:17:03 +0200 Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Message-ID: <87r7o8yf4g.fsf@oak.pohoyda.family> References: <1096006177.432792.29828.nullmailer@Update.UU.SE> <1096014084.739640.30529.nullmailer@Update.UU.SE> <200410031040.i93Ae1YS000609@oak.pohoyda.family> <87d5zvwmq9.fsf_-_@oak.pohoyda.family> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1097277896 29336 80.91.229.6 (8 Oct 2004 23:24:56 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 8 Oct 2004 23:24:56 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 09 01:24:46 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CG46Q-0003dE-00 for ; Sat, 09 Oct 2004 01:24:46 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CG4DE-0005EY-EZ for ged-emacs-devel@m.gmane.org; Fri, 08 Oct 2004 19:31:48 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CG4Cu-00057E-R1 for emacs-devel@gnu.org; Fri, 08 Oct 2004 19:31:28 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CG4Cu-00056i-02 for emacs-devel@gnu.org; Fri, 08 Oct 2004 19:31:28 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CG4Ct-000566-Oo for emacs-devel@gnu.org; Fri, 08 Oct 2004 19:31:27 -0400 Original-Received: from [199.232.41.8] (helo=mx20.gnu.org) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1CG45o-0000f7-8B for emacs-devel@gnu.org; Fri, 08 Oct 2004 19:24:08 -0400 Original-Received: from [213.165.64.20] (helo=mail.gmx.net) by mx20.gnu.org with smtp (Exim 4.34) id 1CG3zJ-0008Iq-Fq for emacs-devel@gnu.org; Fri, 08 Oct 2004 19:17:25 -0400 Original-Received: (qmail 10095 invoked by uid 65534); 8 Oct 2004 23:17:07 -0000 Original-Received: from p50842E6A.dip0.t-ipconnect.de (EHLO www2.gmx.net) (80.132.46.106) by mail.gmx.net (mp002) with SMTP; 09 Oct 2004 01:17:07 +0200 X-Authenticated: #14602519 Original-Received: from oak.pohoyda.family (localhost [127.0.0.1]) by www2.gmx.net (8.12.10/8.12.10) with ESMTP id i98NH5as001017; Sat, 9 Oct 2004 01:17:05 +0200 (CEST) (envelope-from alexander.pohoyda@gmx.net) Original-Received: (from apog@localhost) by oak.pohoyda.family (8.12.10/8.12.10/Submit) id i98NH37J001014; Sat, 9 Oct 2004 01:17:03 +0200 (CEST) (envelope-from alexander.pohoyda@gmx.net) X-Authentication-Warning: oak.pohoyda.family: apog set sender to alexander.pohoyda@gmx.net using -f Original-To: rms@gnu.org In-Reply-To: Original-Lines: 90 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 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: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:28104 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:28104 Richard Stallman writes: > For example, the original implementation of `mail-[un]quote-printable' > functions is too limited. I suppose that this is desired: > > (defun mail-quote-printable (string &optional wrapper) > "Encode the STRING in such a way that the resulting octets are unlikely to > be modified by mail transport. Defined by RFC 2045. > If the optional argument WRAPPER is non-nil, decorate the resulting string > with =?charset?Q?....?=, as defined by RFC 2047." > (if wrapper > (rfc2047-encode-string string) > (rfc2045-quoted-printable-encode-string string))) > > I do not know whether that is desired; I don't understand it. I'll try to explain. RFC 2045, among other things, defines quoted-printable encoding. The Quoted-Printable encoding is intended to represent data that largely consists of octets that correspond to printable characters in the US-ASCII character set. RFC 2045 describes a mechanism for denoting textual body parts which are coded in various character sets, as well as methods for encoding such body parts as sequences of printable US-ASCII characters. RFC 2047 defines similar techniques to allow the encoding of non-ASCII text in various portions of a RFC 822 [2] message header, in a manner which is unlikely to confuse existing message handling software. Both techniques are used very often if you live outside of the US. > It looks like you are talking about functions in Gnus; These functions are currently implemented in Gnus, but they are general MIME functions and are needed by Rmail or any other MIME-related software. > Now, there are many other functions and constants which are > defined by some RFCs and I have implemented them in such a way: > > mime/ > rfc2045.el (13 functions) > rfc2047.el (11 functions) > rfc2231.el (7 functions) > (some other less important files) > > I do not understand what "such a way" means. What way do you mean? I propose to create a directory called "mime" in "$EMACSROOT/lisp/mail" and put all MIME-related functionality in there. I further propose to group functions defined by RFCs (Request For Comment) into corresponding files. I have partly implemented RFCs 2045, 2047 and 2231, but other will follow. I ask you because I recall that you are opposed to creating new files in the source tree. > Are you saying you have written files with the same names as certain > files in Gnus? Exactly! Once again, I propose that we move general-purpose MIME functions out of lisp/gnus into lisp/mail/mime directory. Are you OK with this? > If that's what you mean, the simplest way to avoid conflict > is to rename these functions, then add them to mail-utils.el > or put them together in some other new file. Why not? Yes, we can put all MIME-related functions into mail-utils.el, but it would be better to put them into a separate file (mime.el) or even a separate directory (mime) with separate files implementing specific RFCs, e.g. the file lisp/mail/mime/rfc2045.el contains functions defined by RFC 2045. Please choose and I will send a patch. -- Alexander Pohoyda PGP Key fingerprint: 7F C9 CC 5A 75 CD 89 72 15 54 5F 62 20 23 C6 44