From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Unicode Lisp reader escapes Date: Wed, 03 May 2006 11:47:27 +0300 Message-ID: References: <17491.34779.959316.484740@parhasard.net> Reply-To: Eli Zaretskii NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1146646097 1104 80.91.229.2 (3 May 2006 08:48:17 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 3 May 2006 08:48:17 +0000 (UTC) Cc: kehoea@parhasard.net, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 03 10:48:11 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 1FbD1k-0005Mh-Qn for ged-emacs-devel@m.gmane.org; Wed, 03 May 2006 10:48:09 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FbD1k-0006gA-39 for ged-emacs-devel@m.gmane.org; Wed, 03 May 2006 04:48:08 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FbD15-0006Zh-10 for emacs-devel@gnu.org; Wed, 03 May 2006 04:47:27 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FbD13-0006Yq-4x for emacs-devel@gnu.org; Wed, 03 May 2006 04:47:26 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FbD12-0006Yi-Qt for emacs-devel@gnu.org; Wed, 03 May 2006 04:47:24 -0400 Original-Received: from [192.114.186.66] (helo=romy.inter.net.il) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FbD1N-0003T6-T9 for emacs-devel@gnu.org; Wed, 03 May 2006 04:47:46 -0400 Original-Received: from HOME-C4E4A596F7 (IGLD-80-230-248-70.inter.net.il [80.230.248.70]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id ECJ27685 (AUTH halo1); Wed, 3 May 2006 11:47:22 +0300 (IDT) Original-To: Kenichi Handa In-reply-to: (message from Kenichi Handa on Wed, 03 May 2006 11:59:52 +0900) 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:53840 Archived-At: > From: Kenichi Handa > CC: kehoea@parhasard.net, emacs-devel@gnu.org > Date: Wed, 03 May 2006 11:59:52 +0900 > > > Moreover, I think the fact that decode-char uses translation tables to > > support unify-8859-on-*coding-mode (and thus might produce characters > > other than mule-unicode-*) could even be a misfeature: > > Decode-char doesn't support unify-8859-on-*coding-mode but > supports utf-fragment-on-decoding and > utf-translate-cjk-mode. Sorry, I meant utf-fragment-on-decoding, which decodes Cyrillic and Greek into ISO 8859. (I always get confused and lost in the maze of those twisted *-on-decoding passages, all alike.) > > 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.