(mm-content-transfer-encoding-defaults): Use qp-or-base64 for the

 application/* types.

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index 7f80eae..ddfd351 100644 (file)
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,3 +1,8 @@
+2004-07-02  Katsumi Yamaoka  <yamaoka@jpl.org>
+
+       * mm-encode.el (mm-content-transfer-encoding-defaults): Use
+       qp-or-base64 for the application/* types.
+
 2004-07-02  Jesper Harder  <harder@ifa.au.dk>
 
        * nnrss.el (nnrss-read-group-data): Fix off-by-one error.  From

diff --git a/lisp/mm-encode.el b/lisp/mm-encode.el
index 735ba6d..63c963b 100644 (file)
--- a/lisp/mm-encode.el
+++ b/lisp/mm-encode.el
@@ -36,14 +36,18 @@
   '(("text/x-patch" 8bit)
     ("text/.*" qp-or-base64)
     ("message/rfc822" 8bit)
-    ("application/emacs-lisp" 8bit)
-    ("application/x-emacs-lisp" 8bit)
-    ("application/x-patch" 8bit)
+    ("application/emacs-lisp" qp-or-base64)
+    ("application/x-emacs-lisp" qp-or-base64)
+    ("application/x-patch" qp-or-base64)
     (".*" base64))
   "Alist of regexps that match MIME types and their encodings.
 If the encoding is `qp-or-base64', then either quoted-printable
 or base64 will be used, depending on what is more efficient.
 
+`qp-or-base64' has another effect.  It will fold long lines so that
+MIME parts may not be broken by MTA.  So do `quoted-printable' and
+`base64'.
+
 Note: It affects body encoding only when a part is a raw forwarded
 message (which will be made by `gnus-summary-mail-forward' with the
 arg 2 for example) or is neither the text/* type nor the message/*