# HG changeset patch # User Richard M. Stallman # Date 766624541 0 # Node ID 782646fc75055896c1ae9641a61da5e3b0c17f82 # Parent c5a85ac1d2920ac0f515848fc1eb555ce1fc8ee5 *** empty log message *** diff -r c5a85ac1d292 -r 782646fc7505 lispref/strings.texi --- a/lispref/strings.texi Sun Apr 17 23:02:52 1994 +0000 +++ b/lispref/strings.texi Sun Apr 17 23:15:41 1994 +0000 @@ -743,12 +743,13 @@ @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.