From: Eli Zaretskii <eliz@gnu.org>
To: schwab@linux-m68k.org, monkey@sandpframing.com
Cc: 6576@debbugs.gnu.org
Subject: bug#6576: documentation `string-to-char' is incorrect
Date: Wed, 07 Jul 2010 18:46:44 +0300 [thread overview]
Message-ID: <83wrt770rf.fsf@gnu.org> (raw)
In-Reply-To: <83y6dn74lv.fsf@gnu.org>
> Date: Wed, 07 Jul 2010 17:23:40 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: monkey@sandpframing.com, 6576@debbugs.gnu.org
>
> > >> > 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.
Actually, there's no way we could return the eight-bit characters in
the 160 to 255 range, since that range is already taken by Unicode
codepoints of Latin characters. So how about
"Return the codepoint of the first character of STRING.
Value is the Unicode codepoint, if it is below #x110000 (in hex).
Codepoints beyond that are Emacs extensions of Unicode. In
particular, eight-bit characters are returned as codepoints in
the range #x3FFF80 through #x3FFFFF, inclusive."
next prev parent reply other threads:[~2010-07-07 15:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 21:34 bug#6576: documentation `string-to-char' is incorrect MON KEY
2010-07-07 7:12 ` Eli Zaretskii
2010-07-07 8:40 ` Andreas Schwab
2010-07-07 10:31 ` Eli Zaretskii
2010-07-07 12:16 ` Andreas Schwab
2010-07-07 14:23 ` Eli Zaretskii
2010-07-07 15:46 ` Eli Zaretskii [this message]
2011-07-13 23:50 ` Lars Magne Ingebrigtsen
2011-07-14 2:13 ` Chong Yidong
2011-07-14 13:02 ` Lars Magne Ingebrigtsen
2011-07-14 3:06 ` Eli Zaretskii
2011-07-14 13:00 ` Lars Magne Ingebrigtsen
2011-07-14 13:34 ` Eli Zaretskii
2011-07-14 14:06 ` Lars Magne Ingebrigtsen
2011-07-14 15:59 ` Eli Zaretskii
2011-07-14 16:12 ` Lars Magne Ingebrigtsen
2011-07-14 19:37 ` Eli Zaretskii
2011-07-14 19:39 ` Lars Magne Ingebrigtsen
2011-07-15 19:06 ` MON KEY
2011-07-21 18:38 ` Chong Yidong
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wrt770rf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=6576@debbugs.gnu.org \
--cc=monkey@sandpframing.com \
--cc=schwab@linux-m68k.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).