summaryrefslogtreecommitdiff
path: root/lispref/strings.texi
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>1994-04-17 23:15:41 +0000
committerRichard M. Stallman <rms@gnu.org>1994-04-17 23:15:41 +0000
commit2778c642f8e637cf50ad3ff303be6c082a3e91d4 (patch)
tree0f1d0220bc54408790d0bc0bf7b2a97ebf482187 /lispref/strings.texi
parent5a0fd72f90459141bb100754a58b0543f720908c (diff)
downloademacs-2778c642f8e637cf50ad3ff303be6c082a3e91d4.tar.gz
*** empty log message ***
Diffstat (limited to 'lispref/strings.texi')
-rw-r--r--lispref/strings.texi13
1 files changed, 7 insertions, 6 deletions
diff --git a/lispref/strings.texi b/lispref/strings.texi
index efca7aeea62..1a25085aee7 100644
--- a/lispref/strings.texi
+++ b/lispref/strings.texi
@@ -743,12 +743,13 @@ equivalence class (of characters with the same canonical equivalent).
@samp{A} into @samp{a}, and likewise for each set of equivalent
characters.)
- When you construct a case table, you can provide @code{nil} for both
-@var{canonicalize} and @var{equivalences}. When you specify the case
-table for use, Emacs fills in these strings, computing them from
-@var{upcase} and @var{downcase}. In a case table that is actually in
-use, those components are non-@code{nil}. Do not try to make just one
-of these components @code{nil}; that is not meaningful.
+ When you construct a case table, you can provide @code{nil} for
+@var{canonicalize}; then Emacs fills in this string from @var{upcase}
+and @var{downcase}. You can also provide @code{nil} for
+@var{equivalences}; then Emacs fills in this string from
+@var{canonicalize}. In a case table that is actually in use, those
+components are non-@code{nil}. Do not try to specify @var{equivalences}
+without also specifying @var{canonicalize}.
Each buffer has a case table. Emacs also has a @dfn{standard case
table} which is copied into each buffer when you create the buffer.