# HG changeset patch
# User Eli Zaretskii <eliz@gnu.org>
# Date 1227961162 0
# Node ID 0f0810c1d1d152075c99c78e061516195235ffa9
# Parent  ce90a3ecf576583e8a84e39718a243219aa6376b
(String Basics): Add an @xref to "Character Codes".

diff -r ce90a3ecf576 -r 0f0810c1d1d1 doc/lispref/strings.texi
--- a/doc/lispref/strings.texi	Sat Nov 29 12:18:44 2008 +0000
+++ b/doc/lispref/strings.texi	Sat Nov 29 12:19:22 2008 +0000
@@ -39,7 +39,8 @@
 
   Characters are represented in Emacs Lisp as integers;
 whether an integer is a character or not is determined only by how it is
-used.  Thus, strings really contain integers.
+used.  Thus, strings really contain integers.  @xref{Character Codes},
+for details about character representation in Emacs.
 
   The length of a string (like any array) is fixed, and cannot be
 altered once the string exists.  Strings in Lisp are @emph{not}
@@ -54,11 +55,8 @@
 
   There are two text representations for non-@acronym{ASCII} characters in
 Emacs strings (and in buffers): unibyte and multibyte (@pxref{Text
-Representations}).  An @acronym{ASCII} character always occupies one byte in a
-string; in fact, when a string is all @acronym{ASCII}, there is no real
-difference between the unibyte and multibyte representations.
-For most Lisp programming, you don't need to be concerned with these two
-representations.
+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