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: Sun, 07 May 2006 21:38:17 +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 1147005549 24393 80.91.229.2 (7 May 2006 12:39:09 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 7 May 2006 12:39:09 +0000 (UTC) Cc: emacs-devel@gnu.org, alkibiades@gmx.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 07 14:39:02 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 1FciX6-00044P-Nd for ged-emacs-devel@m.gmane.org; Sun, 07 May 2006 14:38:45 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FciX6-0006ks-7C for ged-emacs-devel@m.gmane.org; Sun, 07 May 2006 08:38:44 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FciWr-0006kZ-DU for emacs-devel@gnu.org; Sun, 07 May 2006 08:38:29 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FciWq-0006kE-9f for emacs-devel@gnu.org; Sun, 07 May 2006 08:38:29 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FciWq-0006k8-4u for emacs-devel@gnu.org; Sun, 07 May 2006 08:38:28 -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 1FciXQ-0006Ky-6V; Sun, 07 May 2006 08:39:05 -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 k47CcIih014896; Sun, 7 May 2006 21:38:18 +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 k47CcIST025858; Sun, 7 May 2006 21:38:18 +0900 Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1FciWf-0007hz-00; Sun, 07 May 2006 21:38:17 +0900 Original-To: rms@gnu.org In-reply-to: (message from Richard Stallman on Sun, 07 May 2006 01:00: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:54030 Archived-At: In article , Richard Stallman writes: >> Are you talking about how the compiler would write the .elc file? >> Or are you talking about how the .elc file would be interpreted? > It's the former. Meanwhile I have tested it. After some more thought I > think that the case of an UTF-8 encoded source files containing > characters from the Greek or Cyrillic repertoires is in fact entirely > analogous to what would happen with \u. > In other words: that particular bug is already there. > Handa-san, could you please investigate the bug? > Oliver, could you email Handa-san a description of the > bug, in the form which already exists? Can you find a test case > which fails in the present development sources? When you byte-compile a x.el file, x.el file is at first decoded. How x.el file is decoded depends on many thing, and thus, of course, the resulting x.elc files become different. If you say that is a bug, I think there's no way to fix it. The very simple testcase is this: (progn (let ((str "(setq x \"\300\300\")\n") (coding-system-for-write 'no-conversion)) (write-region str nil "~/test1.el") (write-region str nil "~/test2.el")) (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. I hope I misunderstand what you claim here. --- Kenichi Handa handa@m17n.org