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: [PATCH] Unicode Lisp reader escapes Date: Thu, 04 May 2006 10:26:35 +0900 Message-ID: References: <17491.34779.959316.484740@parhasard.net> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1146706019 10599 80.91.229.2 (4 May 2006 01:26:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 4 May 2006 01:26:59 +0000 (UTC) Cc: kehoea@parhasard.net, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 04 03:26:56 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FbScI-0002oH-LH for ged-emacs-devel@m.gmane.org; Thu, 04 May 2006 03:26:54 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FbScI-0003eA-3D for ged-emacs-devel@m.gmane.org; Wed, 03 May 2006 21:26:54 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FbSc5-0003dr-TE for emacs-devel@gnu.org; Wed, 03 May 2006 21:26:41 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FbSc5-0003dW-1i for emacs-devel@gnu.org; Wed, 03 May 2006 21:26:41 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FbSc4-0003dS-Uq for emacs-devel@gnu.org; Wed, 03 May 2006 21:26:40 -0400 Original-Received: from [192.47.44.130] (helo=tsukuba.m17n.org) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FbScY-0008EM-Kt; Wed, 03 May 2006 21:27:11 -0400 Original-Received: from nfs.m17n.org (nfs.m17n.org [192.47.44.7]) by tsukuba.m17n.org (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id k441QbWC021533; Thu, 4 May 2006 10:26:37 +0900 Original-Received: from etlken (etlken.m17n.org [192.47.44.125]) by nfs.m17n.org (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id k441QauW020029; Thu, 4 May 2006 10:26:37 +0900 Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1FbSbz-0003MC-00; Thu, 04 May 2006 10:26:35 +0900 Original-To: Eli Zaretskii In-reply-to: (message from Eli Zaretskii on Wed, 03 May 2006 11:47:27 +0300) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.50 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) 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:53879 Archived-At: In article , Eli Zaretskii writes: >> > do we really want read_escape to produce Unicode or >> > non-Unicode characters when it sees \uNNNN, depending on >> > the current user settings? >> >> I think, at least, CJK characters should be decoded into one >> of CJK charsets because there's no other charsets. > Right, but what about Cyrillic and Greek? The merits and demerits of > depending on utf-fragment-on-decoding are not clear when the Lisp > reader is involved. I don't see any strong reason for not following utf-fragment-on-decoding in read_escape leaving the question about the usefullness of this option. --- Kenichi Handa handa@m17n.org