unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Unicode character read representation
Date: Tue, 24 Feb 2009 20:14:14 +0900	[thread overview]
Message-ID: <E1LbvEs-0004v7-F1@etlken> (raw)
In-Reply-To: <87hc2n28a4.fsf@cyd.mit.edu> (message from Chong Yidong on Sat, 21 Feb 2009 09:07:15 -0500)

In article <87hc2n28a4.fsf@cyd.mit.edu>, Chong Yidong <cyd@stupidchicken.com> writes:

> From objects.texi in the Lisp manual:
>   `\U00NNNNNN' represents the character whose Unicode code point is
>   `U+NNNNNN', if such a character is supported by Emacs.  If the
>   corresponding character is not supported, Emacs signals an error.

> Are there any Unicode code points not supported by Emacs,

No.

> or is this sentence obsolete?

Not completely obsolete, but should be modified somehow.

At first, #x0..#x3FFFFF are all valid Emacs character codes.

Some of U+NNNNNN are valid Unicode code points for
"noncharacter" (e.g. U+FFFE, U+FFFF), some are invalid
Unicode code points (U+120000..U+3FFFFF), some are invalid
both as Unicode code points and Emacs character codes
(U+400000 and over).

Currently Emacs signals an error only for U+400000 and over,
and I'm not sure how strictly we should interprete
\U.. notation.

---
Kenichi Handa
handa@m17n.org




  parent reply	other threads:[~2009-02-24 11:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-21 14:07 Unicode character read representation Chong Yidong
2009-02-21 14:22 ` Harald Hanche-Olsen
2009-02-24 11:14 ` Kenichi Handa [this message]
2009-02-24 22:16   ` Stefan Monnier
2009-02-26  7:28     ` Kenichi Handa
2009-02-26 15:08       ` Stefan Monnier
2009-02-27  0:51         ` Kenichi Handa
2009-02-27  1:45           ` 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=E1LbvEs-0004v7-F1@etlken \
    --to=handa@m17n.org \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.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).