[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#30218: [PATCH] Fix statement about string equality (Bug#30218).
From: |
Philipp Stephani |
Subject: |
bug#30218: [PATCH] Fix statement about string equality (Bug#30218). |
Date: |
Tue, 23 Jan 2018 00:12:32 +0100 |
* doc/lispref/objects.texi (Equality Predicates): Fix statement about
equality between unibyte and multibyte strings.
---
doc/lispref/objects.texi | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/doc/lispref/objects.texi b/doc/lispref/objects.texi
index 7cbc61dc8e..82c8007376 100644
--- a/doc/lispref/objects.texi
+++ b/doc/lispref/objects.texi
@@ -2206,11 +2206,10 @@ Equality Predicates
Comparison of strings is case-sensitive, but does not take account of
text properties---it compares only the characters in the strings.
@xref{Text Properties}. Use @code{equal-including-properties} to also
-compare text properties. For technical reasons, a unibyte string and
-a multibyte string are @code{equal} if and only if they contain the
-same sequence of character codes and all these codes are either in the
-range 0 through 127 (@acronym{ASCII}) or 160 through 255
-(@code{eight-bit-graphic}). (@pxref{Text Representations}).
+compare text properties. A unibyte string and a multibyte string are
+@code{equal} if and only if they contain the same sequence of
+character codes and all these codes are in the range 0 through 127
+(@acronym{ASCII}). (@pxref{Text Representations}).
@example
@group
--
2.15.1