[Emacs-diffs] /srv/bzr/emacs/trunk r101514: rfc2047.el (rfc2047-encode-parameter): Doc fix.

[Katsumi Yamaoka]

------------------------------------------------------------
revno: 101514
committer: Katsumi Yamaoka <address@hidden>
branch nick: trunk
timestamp: Mon 2010-09-20 23:44:05 +0000
message:
  rfc2047.el (rfc2047-encode-parameter): Doc fix.
  emacs-mime.texi (rfc2047): Update description for rfc2047-encode-parameter.
modified:
  doc/misc/ChangeLog
  doc/misc/emacs-mime.texi
  lisp/gnus/ChangeLog
  lisp/gnus/rfc2047.el

=== modified file 'doc/misc/ChangeLog'
--- a/doc/misc/ChangeLog        2010-09-13 15:32:45 +0000
+++ b/doc/misc/ChangeLog        2010-09-20 23:44:05 +0000
@@ -1,3 +1,8 @@
+2010-09-20  Katsumi Yamaoka  <address@hidden>
+
+       * emacs-mime.texi (rfc2047): Update description for
+       rfc2047-encode-parameter.
+
 2010-09-13  Michael Albinus  <address@hidden>
 
        * tramp.texi (Inline methods): Remove "ssh1_old", "ssh2_old" and

=== modified file 'doc/misc/emacs-mime.texi'
--- a/doc/misc/emacs-mime.texi  2010-09-02 00:55:51 +0000
+++ b/doc/misc/emacs-mime.texi  2010-09-20 23:44:05 +0000
@@ -1469,21 +1469,9 @@
 
 @item rfc2047-encode-parameter
 @findex rfc2047-encode-parameter
-Encode a parameter in the RFC2047-like style.  This is a replacement for
-the @code{rfc2231-encode-string} function.  @xref{rfc2231}.
-
-When attaching files as @acronym{MIME} parts, we should use the RFC2231
-encoding to specify the file names containing address@hidden
-characters.  However, many mail softwares don't support it in practice
-and recipients won't be able to extract files with correct names.
-Instead, the RFC2047-like encoding is acceptable generally.  This
-function provides the very RFC2047-like encoding, resigning to such a
-regrettable trend.  To use it, put the following line in your
address@hidden/.gnus.el} file:
-
address@hidden
-(defalias 'mail-header-encode-parameter 'rfc2047-encode-parameter)
address@hidden lisp
+Encode a parameter in the RFC2047-like style.  This is a substitution
+for the @code{rfc2231-encode-string} function, that is the standard but
+many mailers don't support it.  @xref{rfc2231}.
 
 @end table
 

=== modified file 'lisp/gnus/ChangeLog'
--- a/lisp/gnus/ChangeLog       2010-09-20 23:08:33 +0000
+++ b/lisp/gnus/ChangeLog       2010-09-20 23:44:05 +0000
@@ -1,3 +1,7 @@
+2010-09-20  Katsumi Yamaoka  <address@hidden>
+
+       * rfc2047.el (rfc2047-encode-parameter): Doc fix.
+
 2010-09-20  Lars Magne Ingebrigtsen  <address@hidden>
 
        * nnimap.el (nnimap-request-group): Don't select the imap buffer before

=== modified file 'lisp/gnus/rfc2047.el'
--- a/lisp/gnus/rfc2047.el      2010-09-02 00:55:51 +0000
+++ b/lisp/gnus/rfc2047.el      2010-09-20 23:44:05 +0000
@@ -851,18 +851,8 @@
 
 (defun rfc2047-encode-parameter (param value)
   "Return and PARAM=VALUE string encoded in the RFC2047-like style.
-This is a replacement for the `rfc2231-encode-string' function.
-
-When attaching files as MIME parts, we should use the RFC2231 encoding
-to specify the file names containing non-ASCII characters.  However,
-many mail softwares don't support it in practice and recipients won't
-be able to extract files with correct names.  Instead, the RFC2047-like
-encoding is acceptable generally.  This function provides the very
-RFC2047-like encoding, resigning to such a regrettable trend.  To use
-it, put the following line in your ~/.gnus.el file:
-
-\(defalias 'mail-header-encode-parameter 'rfc2047-encode-parameter)
-"
+This is a substitution for the `rfc2231-encode-string' function, that
+is the standard but many mailers don't support it."
   (let ((rfc2047-encoding-type 'mime)
        (rfc2047-encode-max-chars nil))
     (rfc2045-encode-string param (rfc2047-encode-string value))))