[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#6576: documentation `string-to-char' is incorrect
From: |
Eli Zaretskii |
Subject: |
bug#6576: documentation `string-to-char' is incorrect |
Date: |
Wed, 07 Jul 2010 17:23:40 +0300 |
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: monkey@sandpframing.com, 6576@debbugs.gnu.org
> Date: Wed, 07 Jul 2010 14:16:28 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Andreas Schwab <schwab@linux-m68k.org>
> >> Cc: MON KEY <monkey@sandpframing.com>, 6576@debbugs.gnu.org
> >> Date: Wed, 07 Jul 2010 10:40:00 +0200
> >>
> >> Eli Zaretskii <eliz@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.
And that's why there's this note:
> >> > 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.
Sounds like a bug, assuming it's true.