From: Kenichi Handa <handa@m17n.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org, cyd@stupidchicken.com,
1726@emacsbugs.donarmstrong.com
Subject: bug#1726: 23.0.60; end-of-sentence and non-breaking space
Date: Mon, 05 Jan 2009 16:11:23 +0900 [thread overview]
Message-ID: <E1LJjcR-0001uN-1l__9927.39808648384$1231140300$gmane$org@etlken.m17n.org> (raw)
In-Reply-To: <E1LJIXN-0008Vg-Pe@fencepost.gnu.org> (message from Richard M Stallman on Sat, 03 Jan 2009 21:16:21 -0500)
In article <E1LJIXN-0008Vg-Pe@fencepost.gnu.org>, Richard M Stallman <rms@gnu.org> writes:
> We need some way of inserting raw 8-bit bytes, because otherwise code
> that encodes and decodes text in Lisp will not work. For inserting
> characters, we have the \u alternative; but I don't think there's
> alternative for raw bytes except insert \xNN.
> Naybe that is a valid reason for the current behavior, but that
> doesn't alter the need for the manual to document the behavior.
> Meanwhile, the Chinese and Chinese-derived character codes
> do not follow Unicode. So you can't enter them with \u.
> What is the way to enter them?
Most of Chinese and Chinese-derived character codes are
unified into Unicode area. Only a few codes can't be
unified with Unicode, and thus decoded into the character
space over #x110000. But, in that sense, Chinese and
Chinese-derived character codes are not special. There
exist several non-Chinese character sets (e.g. tibetan)
containing characters that doesn't exist in Unicode, and
they are decoded into the character space over #x110000 too.
But, all of them can be accessed by "\U00XXXXXX".
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2009-01-05 7:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 3:47 23.0.60; end-of-sentence and non-breaking space Chong Yidong
2009-01-02 1:25 ` Richard M Stallman
2009-01-02 1:25 ` bug#1726: " Richard M Stallman
2009-01-02 1:25 ` bug#1727: " Richard M Stallman
2009-01-02 2:38 ` bug#1726: " Drew Adams
2009-01-02 2:38 ` Drew Adams
2009-01-02 2:38 ` Drew Adams
2009-01-02 4:11 ` Stefan Monnier
2009-01-02 17:13 ` bug#1726: " Richard M Stallman
2009-01-02 17:13 ` Richard M Stallman
2009-01-03 3:06 ` bug#1726: " Stefan Monnier
2009-01-03 3:06 ` Stefan Monnier
2009-01-03 9:54 ` Eli Zaretskii
2009-01-03 9:54 ` bug#1726: " Eli Zaretskii
2009-01-03 15:21 ` Richard M Stallman
2009-01-03 16:44 ` bug#1726: " Eli Zaretskii
2009-01-03 16:44 ` Eli Zaretskii
2009-01-04 2:16 ` bug#1726: " Richard M Stallman
2009-01-04 2:16 ` Richard M Stallman
2009-01-04 4:18 ` bug#1726: " Eli Zaretskii
2009-01-04 4:18 ` Eli Zaretskii
2009-01-04 21:42 ` Richard M Stallman
2009-01-04 21:42 ` bug#1726: " Richard M Stallman
2009-01-04 4:29 ` Jason Rumney
2009-01-04 4:29 ` Jason Rumney
2009-01-04 16:45 ` Eli Zaretskii
2009-01-04 16:45 ` Eli Zaretskii
2009-01-05 7:11 ` Kenichi Handa [this message]
2009-01-05 7:11 ` Kenichi Handa
2009-01-06 0:01 ` bug#1726: " Richard M Stallman
2009-01-06 4:08 ` Eli Zaretskii
2009-01-05 6:37 ` Kenichi Handa
2009-01-05 6:37 ` Kenichi Handa
2009-01-03 15:21 ` bug#1726: " Richard M Stallman
2009-01-02 4:11 ` Stefan Monnier
2009-01-02 4:11 ` bug#1727: " Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2009-01-01 3:47 bug#1726: " Chong Yidong
2008-12-29 10:23 Richard M Stallman
2011-09-11 18:43 ` Lars Magne Ingebrigtsen
2012-03-27 23:27 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='E1LJjcR-0001uN-1l__9927.39808648384$1231140300$gmane$org@etlken.m17n.org' \
--to=handa@m17n.org \
--cc=1726@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.