Update.

[elisp/semi.git] / mime-ui-en.sgml

diff --git a/mime-ui-en.sgml b/mime-ui-en.sgml
index 49f60ca..2a08a63 100644 (file)
--- a/mime-ui-en.sgml
+++ b/mime-ui-en.sgml
@@ -411,8 +411,7 @@ Encrypt to specified region. <cf node="PGP">
 <kt>C-c C-x C-q
 <kd>
 avoid to encode tags in specified region.  In other words, tags is
-interpreted as such string.  (In current version, it may be
-incomplete.  Maybe PGP-signature does not work for this enclosure.)
+interpreted as such string.
 </kl>
 
 
@@ -623,20 +622,16 @@ The value should be a symbol.  Allowed versions are <code>gpg</code>,
 <defvar name="pgp-function-alist">
 <p>
 Alist of service names vs. corresponding functions and its filenames.
-Each element looks like
-<code>(SERVICE FUNCTION FILE [PGP5_FUNCTION PGP5_FILE [GPG_FUNCTION GPG_FILE]])</code>.
+Each element looks like <code>(SERVICE FUNCTION FILE)</code>.
 <p>
-SERVICE is a symbol of PGP2, PGP5 or GnuPG processing.  It allows
-`verify', `decrypt', `fetch-key', `snarf-keys', `mime-sign',
-`traditional-sign', `encrypt' or `insert-key'.
+SERVICE is a symbol of PGP processing.  It allows `verify', `decrypt',
+`fetch-key', `snarf-keys', `mime-sign', `traditional-sign', `encrypt'
+or `insert-key'.
 <p>
 Function is a symbol of function to do specified SERVICE.
 <p>
 FILE is string of filename which has definition of corresponding
 FUNCTION.
-<p>
-PGP5_FUNCTION, PGP5_FILE, GPG_FUNCTION and GPG_FILE are similar to
-FUNCTION and FILE, but they will be used for PGP 5.0i or GnuPG.
 </defvar>
 
 <defun name="pgp-function">
@@ -645,6 +640,13 @@ FUNCTION and FILE, but they will be used for PGP 5.0i or GnuPG.
 Return function to do service <var>method</var>.
 </defun>
 
+<defun name="mime-mc-setversion">
+           <args> version
+<p>
+Select `pgp-version' and `mc-default-scheme' if possible.
+<var>version</var> should be a string or a symbol.
+<defun/>
+
 
 <h2> Mouse button
 <node> Buttons