GNU bug report logs - #6576
documentation `string-to-char' is incorrect

Previous Next

Full log

View this message in rfc822 format

From: Andreas Schwab <schwab <at> linux-m68k.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: monkey <at> sandpframing.com, 6576 <at> debbugs.gnu.org
Subject: bug#6576: documentation `string-to-char' is incorrect
Date: Wed, 07 Jul 2010 14:16:28 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Andreas Schwab <schwab <at> linux-m68k.org>
>> Cc: MON KEY <monkey <at> sandpframing.com>,  6576 <at> debbugs.gnu.org
>> Date: Wed, 07 Jul 2010 10:40:00 +0200
>> 
>> Eli Zaretskii <eliz <at> gnu.org> writes:
>> 
>> >   "Return the Unicode codepoint of the first character of STRING.
>> 
>> This is not correct.  The value is just the internal encoding of the
>> character.
>
> Which is Unicode, AFAIK.

No, it is an extension of Unicode.  Eight-bit characters, for example,
are not part of Unicode.

>> >   Note: eight-bit characters are returned as single-byte values in the
>> >   range 160 to 255, inclusive."
>> 
>> That depends on the multibyteness of the string.
>
> Eight-bit characters are defined as such only in multibyte strings.

That makes it even more incorrect.  For multibyte strings you'll get the
internal encoding, which is not in the range 160 to 255.

Andreas.

-- 
Andreas Schwab, schwab <at> linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.