[Emacs-diffs] emacs/doc/lispref strings.texi

[Eli Zaretskii]

CVSROOT:        /cvsroot/emacs
Module name:    emacs
Changes by:     Eli Zaretskii <eliz>    08/11/29 12:19:22

Modified files:
        doc/lispref    : strings.texi 

Log message:
        (String Basics): Add an @xref to "Character Codes".

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/emacs/doc/lispref/strings.texi?cvsroot=emacs&r1=1.7&r2=1.8

Patches:
Index: strings.texi
===================================================================
RCS file: /cvsroot/emacs/emacs/doc/lispref/strings.texi,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- strings.texi        25 Nov 2008 03:52:05 -0000      1.7
+++ strings.texi        29 Nov 2008 12:19:22 -0000      1.8
@@ -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 address@hidden 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