(String Basics): Only unibyte strings that represent key sequences hold

8-bit raw bytes.

2 files changed, 7 insertions, 4 deletions

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index 952c2953a60..e36aecce040 100644
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,5 +1,8 @@
 2008-12-05  Eli Zaretskii  <eliz@gnu.org>
 
+        * strings.texi (String Basics): Only unibyte strings that
+        represent key sequences hold 8-bit raw bytes.
+
         * nonascii.texi (Coding System Basics): Rewrite @ignore'd
         paragraph to speak about `undecided'.
         (Character Properties): Don't explain the meaning of each
diff --git a/doc/lispref/strings.texi b/doc/lispref/strings.texi
index a2315cc767b..e987bdeef78 100644
--- a/doc/lispref/strings.texi
+++ b/doc/lispref/strings.texi
@@ -58,10 +58,10 @@ Emacs strings (and in buffers): unibyte and multibyte (@pxref{Text
 Representations}).  For most Lisp programming, you don't need to be
 concerned with these two representations.
 
-  Sometimes key sequences are represented as strings.  When a string is
-a key sequence, string elements in the range 128 to 255 represent meta
-characters (which are large integers) rather than character
-codes in the range 128 to 255.
+  Sometimes key sequences are represented as unibyte strings.  When a
+unibyte string is a key sequence, string elements in the range 128 to
+255 represent meta characters (which are large integers) rather than
+character codes in the range 128 to 255.
 
   Strings cannot hold characters that have the hyper, super or alt
 modifiers; they can hold @acronym{ASCII} control characters, but no other