all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: 30218@debbugs.gnu.org
Cc: Philipp Stephani <phst@google.com>
Subject: bug#30218: [PATCH] Fix statement about string equality (Bug#30218).
Date: Tue, 23 Jan 2018 00:12:32 +0100	[thread overview]
Message-ID: <20180122231232.66965-1-phst@google.com> (raw)
In-Reply-To: <m2zi55fqzb.fsf@gmail.com>

* 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






  reply	other threads:[~2018-01-22 23:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22 22:50 bug#30218: 27.0.50; Possibly incorrect statement in manual about string equality Philipp
2018-01-22 23:12 ` Philipp Stephani [this message]
2018-02-04 18:44   ` bug#30218: [PATCH] Fix statement about string equality (Bug#30218) Philipp Stephani
2018-01-26 10:39 ` bug#30218: 27.0.50; Possibly incorrect statement in manual about string equality Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180122231232.66965-1-phst@google.com \
    --to=p.stephani2@gmail.com \
    --cc=30218@debbugs.gnu.org \
    --cc=phst@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.