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, 18 May 2006 10:09:35 +0900 Message-ID: References: <17491.34779.959316.484740@parhasard.net> <87irohfrx1.fsf@gmx.de> <87iroarr9i.fsf-monnier+emacs@gnu.org> <87d5egrb4c.fsf-monnier+emacs@gnu.org> <87ves8p0us.fsf-monnier+emacs@gnu.org> <87ves8ngtb.fsf@gmx.de> <87u07qcnaa.fsf@gmx.de> <87y7x289lr.fsf@gmx.de> 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 1147914624 29824 80.91.229.2 (18 May 2006 01:10:24 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 18 May 2006 01:10:24 +0000 (UTC) Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, storm@cua.dk, alkibiades@gmx.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 18 03:10:22 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 1FgX1v-0004ef-Oi for ged-emacs-devel@m.gmane.org; Thu, 18 May 2006 03:10:20 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FgX1v-0005J3-3R for ged-emacs-devel@m.gmane.org; Wed, 17 May 2006 21:10:19 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FgX1j-0005Iy-7r for emacs-devel@gnu.org; Wed, 17 May 2006 21:10:07 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FgX1h-0005Im-K7 for emacs-devel@gnu.org; Wed, 17 May 2006 21:10:06 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FgX1h-0005Ij-FH for emacs-devel@gnu.org; Wed, 17 May 2006 21:10:05 -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 1FgX4f-0002Zq-5P; Wed, 17 May 2006 21:13:09 -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 k4I19bYg019105; Thu, 18 May 2006 10:09: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 k4I19ZPD009035; Thu, 18 May 2006 10:09:35 +0900 Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1FgX1D-0003ax-00; Thu, 18 May 2006 10:09:35 +0900 Original-To: rms@gnu.org In-reply-to: (message from Richard Stallman on Tue, 16 May 2006 23:45:33 -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:54675 Archived-At: In article , Richard Stallman writes: > I agree, in principle. IIRC, I was the first one here to suggest to > just document the issue and be done with it. But documenting it would > be a good idea. Something along the lines: "When using non-ASCII > characters in Emacs Lisp source files, beware that compilation > "freezes" some of your current settings for character unification > and/or fragmentation. > I want to fix this bug, not document it. I'm confused. You wrote: > Handa says that telling people "don't use utf-8" solves the problem. > If that is a good solution, I think the problem is solved. > Does everyone agree that that solution works? So, I thought you accepted such kind of solution; i.e. documenting the potential problem about decoding and the way to avoid the ambiguity if one has a problematic *.el file. There are two ways to avoid it. (1) use emacs-mule coding system (2) use one of iso-2022 based coding systems (they include iso-8859-X) with setting enable-character-translation to nil in "Local Variables:" section. (1) works now. (2) doens't work now but easy to make it work as I wrote in the previous mail. Do you want something more? --- Kenichi Handa handa@m17n.org