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 21:26:23 +0300 Message-ID: References: <17491.34779.959316.484740@parhasard.net> <87odyfnqcj.fsf-monnier+emacs@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1146680832 31731 80.91.229.2 (3 May 2006 18:27:12 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 3 May 2006 18:27:12 +0000 (UTC) Cc: kehoea@parhasard.net, emacs-devel@gnu.org, handa@m17n.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 03 20:27:08 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 1FbM3b-0006mc-5x for ged-emacs-devel@m.gmane.org; Wed, 03 May 2006 20:26:39 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FbM3a-0001NU-QP for ged-emacs-devel@m.gmane.org; Wed, 03 May 2006 14:26:38 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FbM3P-0001NP-M3 for emacs-devel@gnu.org; Wed, 03 May 2006 14:26:27 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FbM3N-0001N8-6l for emacs-devel@gnu.org; Wed, 03 May 2006 14:26:26 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FbM3N-0001N5-0Z for emacs-devel@gnu.org; Wed, 03 May 2006 14:26:25 -0400 Original-Received: from [192.114.186.20] (helo=nitzan.inter.net.il) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FbM3n-0000Wx-Js for emacs-devel@gnu.org; Wed, 03 May 2006 14:26:51 -0400 Original-Received: from HOME-C4E4A596F7 (IGLD-80-230-69-209.inter.net.il [80.230.69.209]) by nitzan.inter.net.il (MOS 3.7.3-GA) with ESMTP id DGO67487 (AUTH halo1); Wed, 3 May 2006 21:26:18 +0300 (IDT) 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) 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:53863 Archived-At: > Cc: Kenichi Handa , kehoea@parhasard.net, > emacs-devel@gnu.org > From: Stefan Monnier > Date: Wed, 03 May 2006 10:21:15 -0400 > > > 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. IIRC, we don't support such a consistency when we load Lisp files, because we don't want loading and byte-compiling to depend on user settings. Of course, the same effect can also be achieved by binding utf-fragment-on-decoding etc. to appropriate values.