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: Mon, 08 May 2006 16:50:24 +0900 Message-ID: References: <17491.34779.959316.484740@parhasard.net> <87odyfnqcj.fsf-monnier+emacs@gnu.org> <17498.27200.911709.330947@parhasard.net> <877j4z5had.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 1147074683 30202 80.91.229.2 (8 May 2006 07:51:23 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 8 May 2006 07:51:23 +0000 (UTC) Cc: emacs-devel@gnu.org, alkibiades@gmx.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 08 09:51:19 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 1Fd0WL-0000hy-QP for ged-emacs-devel@m.gmane.org; Mon, 08 May 2006 09:51:10 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fd0WL-0005e7-Cw for ged-emacs-devel@m.gmane.org; Mon, 08 May 2006 03:51:09 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fd0Vr-0005Zv-8H for emacs-devel@gnu.org; Mon, 08 May 2006 03:50:39 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fd0Vp-0005Yc-3k for emacs-devel@gnu.org; Mon, 08 May 2006 03:50:38 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fd0Vo-0005YT-RU for emacs-devel@gnu.org; Mon, 08 May 2006 03:50:36 -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 1Fd0WW-0004gQ-BZ; Mon, 08 May 2006 03:51:21 -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 k487oOVx020459; Mon, 8 May 2006 16:50:24 +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 k487oOpW018288; Mon, 8 May 2006 16:50:24 +0900 Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1Fd0Vc-0003yl-00; Mon, 08 May 2006 16:50:24 +0900 Original-To: rms@gnu.org In-reply-to: (message from Richard Stallman on Mon, 08 May 2006 03:36:54 -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:54066 Archived-At: In article , Richard Stallman writes: > (set-language-environment "Latin-1") > (byte-compile-file "~/test1.el") > (set-language-environment "Japanese") > (byte-compile-file "~/test2.el")) > Although the source files are exactly the same, the > resulting test1.elc contains a string of two Latin-1 > characters whereas the test2.elc contains a string of single > Japanese character. > Is the difference due solely to the choice of coding system for > decoding the file? Yes, in the above example. > That heuristic choice of coding system depends on > lots of things, but Lisp files can prevent variation by specifying > -*-coding-system:...;-*-. > When the file does that, does eliminate the problem? Yes, in the above example. > Anyway, is the specific problem I asked you to look at a matter of > choice of coding system? (I don't know the details, since I don't > know what that variable does--I just know it relates to Mule.) "A matter of choice of coding system" is just one of the problems. Even if a coding system is deterministically chosen, there are several options that controls the decoding of utf-*. And, binding all of them to the default values while byte-compiling leads to another problem as I wrote in the previsou mail. --- Kenichi Handa handa@m17n.org