summaryrefslogtreecommitdiff
path: root/lisp/gnus/mm-encode.el
diff options
context:
space:
mode:
Diffstat (limited to 'lisp/gnus/mm-encode.el')
-rw-r--r--lisp/gnus/mm-encode.el11
1 files changed, 2 insertions, 9 deletions
diff --git a/lisp/gnus/mm-encode.el b/lisp/gnus/mm-encode.el
index c6ca4c40d04..296a24351bb 100644
--- a/lisp/gnus/mm-encode.el
+++ b/lisp/gnus/mm-encode.el
@@ -42,15 +42,8 @@
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/*
-type. Even though in those cases, you can use the `encoding' MML tag
-to specify encoding of non-ASCII MIME parts."
+This list is only consulted when encoding MIME parts in the
+bodies -- not for the regular non-MIME-ish messages."
:type '(repeat (list (regexp :tag "MIME type")
(choice :tag "encoding"
(const 7bit)