From: Eli Zaretskii Date: Sat, 27 Jan 2024 08:11:32 +0000 (+0200) Subject: Fix description of when "\xNNN" is considered a unibyte character X-Git-Tag: archive/raspbian/1%29.4+1-4+rpi1~1^2~2^2~18^2~87 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=53481cc954641256602830a6d74def86440ac4a9;p=emacs.git Fix description of when "\xNNN" is considered a unibyte character * doc/lispref/objects.texi (Non-ASCII in Strings): More accurate description of when a hexadecimal escape sequence yields a unibyte character. (Bug#68751) --- diff --git a/doc/lispref/objects.texi b/doc/lispref/objects.texi index 13c5f06b0bd..7b2a4af303f 100644 --- a/doc/lispref/objects.texi +++ b/doc/lispref/objects.texi @@ -1180,13 +1180,14 @@ character), Emacs automatically assumes that it is multibyte. You can also use hexadecimal escape sequences (@samp{\x@var{n}}) and octal escape sequences (@samp{\@var{n}}) in string constants. -@strong{But beware:} If a string constant contains hexadecimal or -octal escape sequences, and these escape sequences all specify unibyte -characters (i.e., less than 256), and there are no other literal -non-@acronym{ASCII} characters or Unicode-style escape sequences in -the string, then Emacs automatically assumes that it is a unibyte -string. That is to say, it assumes that all non-@acronym{ASCII} -characters occurring in the string are 8-bit raw bytes. +@strong{But beware:} If a string constant contains octal escape +sequences or one- or two-digit hexadecimal escape sequences, and these +escape sequences all specify unibyte characters (i.e., codepoints less +than 256), and there are no other literal non-@acronym{ASCII} +characters or Unicode-style escape sequences in the string, then Emacs +automatically assumes that it is a unibyte string. That is to say, it +assumes that all non-@acronym{ASCII} characters occurring in the +string are 8-bit raw bytes. In hexadecimal and octal escape sequences, the escaped character code may contain a variable number of digits, so the first subsequent