From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: 23.0.60; end-of-sentence and non-breaking space Date: Mon, 05 Jan 2009 16:11:23 +0900 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: ger.gmane.org 1231139516 3628 80.91.229.12 (5 Jan 2009 07:11:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 5 Jan 2009 07:11:56 +0000 (UTC) Cc: eliz@gnu.org, emacs-devel@gnu.org, cyd@stupidchicken.com, monnier@iro.umontreal.ca, 1726@emacsbugs.donarmstrong.com To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 05 08:13:06 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LJje2-0005cn-0o for ged-emacs-devel@m.gmane.org; Mon, 05 Jan 2009 08:13:02 +0100 Original-Received: from localhost ([127.0.0.1]:45574 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LJjcm-0004Mh-Fk for ged-emacs-devel@m.gmane.org; Mon, 05 Jan 2009 02:11:44 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LJjch-0004Mc-9Y for emacs-devel@gnu.org; Mon, 05 Jan 2009 02:11:39 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LJjcf-0004MQ-9I for emacs-devel@gnu.org; Mon, 05 Jan 2009 02:11:38 -0500 Original-Received: from [199.232.76.173] (port=38067 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LJjcf-0004MN-1k for emacs-devel@gnu.org; Mon, 05 Jan 2009 02:11:37 -0500 Original-Received: from mx1.aist.go.jp ([150.29.246.133]:64493) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LJjcb-0001jy-Ei; Mon, 05 Jan 2009 02:11:33 -0500 Original-Received: from rqsmtp2.aist.go.jp (rqsmtp2.aist.go.jp [150.29.254.123]) by mx1.aist.go.jp with ESMTP id n057BOuk008787; Mon, 5 Jan 2009 16:11:24 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp4.aist.go.jp by rqsmtp2.aist.go.jp with ESMTP id n057BNe0011687; Mon, 5 Jan 2009 16:11:23 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp4.aist.go.jp with ESMTP id n057BNLT027920; Mon, 5 Jan 2009 16:11:23 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken.m17n.org with local (Exim 4.69) (envelope-from ) id 1LJjcR-0001uN-1l; Mon, 05 Jan 2009 16:11:23 +0900 In-reply-to: (message from Richard M Stallman on Sat, 03 Jan 2009 21:16:21 -0500) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/23.0.60 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) X-detected-operating-system: by monty-python.gnu.org: Solaris 9 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:107598 Archived-At: In article , Richard M Stallman 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