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:33:55 +0900 Message-ID: References: <17491.34779.959316.484740@parhasard.net> <87odyfnqcj.fsf-monnier+emacs@gnu.org> 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 1146706463 11578 80.91.229.2 (4 May 2006 01:34:23 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 4 May 2006 01:34:23 +0000 (UTC) Cc: kehoea@parhasard.net, eliz@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 04 03:34:21 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 1FbSjU-0003br-Kd for ged-emacs-devel@m.gmane.org; Thu, 04 May 2006 03:34:20 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FbSjT-0006BQ-Qw for ged-emacs-devel@m.gmane.org; Wed, 03 May 2006 21:34:19 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FbSjE-0006Ah-Ja for emacs-devel@gnu.org; Wed, 03 May 2006 21:34:04 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FbSjC-0006AJ-U1 for emacs-devel@gnu.org; Wed, 03 May 2006 21:34:04 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FbSjC-0006AG-Ox for emacs-devel@gnu.org; Wed, 03 May 2006 21:34:02 -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 1FbSjg-0000In-Qw; Wed, 03 May 2006 21:34:33 -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 k441XwgG021798; Thu, 4 May 2006 10:33:58 +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 k441Xv7h020207; Thu, 4 May 2006 10:33:58 +0900 Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1FbSj5-0003RO-00; Thu, 04 May 2006 10:33:55 +0900 Original-To: Stefan Monnier In-reply-to: <87odyfnqcj.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 03 May 2006 10:21:15 -0400) 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:53880 Archived-At: In article <87odyfnqcj.fsf-monnier+emacs@gnu.org>, Stefan Monnier writes: >>> 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 think we should treat them as much as possible consistently with the rest > of the treatment of unicode chars. If we start down the path of "OK, we can > do it like this for those chars but not these, oh and as for those ones over > there, we'll do it yet some other way", I think we're headed for headaches > with no real benefit. I agree. --- Kenichi Handa handa@m17n.org