(Documentation Tips): Recommend against `iff'.

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index 65df7d26b1560561f9965cc6c1d9ee83cffb7908..29e9027e54e990c0f812fd8b86016fee6f3c3b4c 100644 (file)
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -4,6 +4,9 @@
 
        * Replace `iff' in doc-strings and comments.
 
+       * help-mode.el (help-make-xrefs): Search for symbol constituents,
+       rather than just `-'.
+
 2007-08-08  Martin Rudalics  <rudalics@gmx.at>
 
        * dired.el (dired-pop-to-buffer):

diff --git a/lispref/tips.texi b/lispref/tips.texi
index de590c4cf9d28606bbce71af983fb44563a5faea..f3070f4659b17f63815068af8d99211db284cfc4 100644 (file)
--- a/lispref/tips.texi
+++ b/lispref/tips.texi
@@ -844,6 +844,12 @@ Avoid using the word ``cause'' (or its equivalents) unnecessarily.
 Instead of, ``Cause Emacs to display text in boldface,'' write just
 ``Display text in boldface.''
 
+@item
+Avoid using ``iff'' (a mathematics term meaning ``if and only if''),
+since many people are unfamiliar with it and mistake it for a typo.  In
+most cases, the meaning is clear with just ``if''.  Otherwise, try to
+find an alternate phrasing that conveys the meaning.
+
 @item
 When a command is meaningful only in a certain mode or situation,
 do mention that in the documentation string.  For example,