X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;f=README.en;h=784567497929452de00685acda6faeb56cf84adc;hb=62756c430ded8a1cd9abad3414534a81c127e19d;hp=ef841a82dbfd3382e2741819a58df3ff224bfc50;hpb=a4d20ad51f2f32d9c5aebd7fd1e90c036a8a6755;p=elisp%2Fsemi.git

diff --git a/README.en b/README.en
index ef841a8..7845674 100644
--- a/README.en
+++ b/README.en
@@ -34,13 +34,16 @@ What's SEMI?
 Required environment
 ====================
 
-  SEMI supports XEmacs 20.2 or later with mule, and Emacs 20.
+  SEMI supports XEmacs 21.1 or later, and GNU Emacs 20.4 or later.
 
-  SEMI does not support anything older than Emacs 19.28 or XEmacs
-  19.14.  SEMI also does not support Emacs 19.29 to 19.34, XEmacs
-  19.15 or XEmacs 20.2 without mule, but SEMI may work with them.
+  SEMI does not support anything older than GNU Emacs 19.28 or XEmacs
+  19.14.  In addition, SEMI does not word with byte-indexing Mule
+  implementations, such as Mule 1, Mule 2 and GNU Emacs 20.1/20.2.
 
-  SEMI requires APEL (9.22 or later) and FLIM (1.14.1 or later)
+  SEMI also does not support Emacs 19.29 to 19.34, XEmacs 19.15 or
+  XEmacs 20.2, but SEMI may work with them.
+
+  SEMI requires APEL (9.22 or later) and FLIM (1.14.2 or later)
   package.  Please install them before installing it.  APEL package is
   available at:
 
@@ -51,9 +54,6 @@ Required environment
 	http://www.kanji.zinbun.kyoto-u.ac.jp/~tomo/comp/emacsen/lisp/
 							flim/flim-1.14/
 
-  PGP/MIME and application/pgp require mailcrypt or tiny-pgp package.
-
-
 Installation
 ============
 
@@ -187,11 +187,17 @@ Mailing lists
 
   Via the EMACS-MIME ML, you can report SEMI bugs, obtain the latest
   release of SEMI, and discuss future enhancements to SEMI.  To join
-  the EMACS-MIME ML, send an empty e-mail to
+  the EMACS-MIME ML, send an e-mail to
 
 	emacs-mime-en-ctl@m17n.org	(English)
 	emacs-mime-ja-ctl@m17n.org	(Japanese)
 
+  containing
+
+	subscribe YOUR NAME
+
+  in its contents.
+
   Notice that you should not send mail to author(s), such as
   morioka@jaist.ac.jp, directly.  Because your problem may occur in
   other environments (if not, it might be your problem, not bug of