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: Tue, 09 May 2006 14:13:31 +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> <87irohfrx1.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 1147151702 21458 80.91.229.2 (9 May 2006 05:15:02 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 9 May 2006 05:15:02 +0000 (UTC) Cc: emacs-devel@gnu.org, alkibiades@gmx.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 09 07:14:59 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 1FdKYj-0006vM-Gu for ged-emacs-devel@m.gmane.org; Tue, 09 May 2006 07:14:57 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FdKYi-0005ET-PV for ged-emacs-devel@m.gmane.org; Tue, 09 May 2006 01:14:56 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FdKYV-0005Dr-4l for emacs-devel@gnu.org; Tue, 09 May 2006 01:14:43 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FdKYT-0005DX-1K for emacs-devel@gnu.org; Tue, 09 May 2006 01:14:42 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FdKYS-0005DU-TF for emacs-devel@gnu.org; Tue, 09 May 2006 01:14:40 -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 1FdKZL-0002DD-SD; Tue, 09 May 2006 01:15:37 -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 k495EKjt030512; Tue, 9 May 2006 14:14:20 +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 k495EKmN013974; Tue, 9 May 2006 14:14:20 +0900 Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1FdKXL-0005lp-00; Tue, 09 May 2006 14:13:31 +0900 Original-To: rms@gnu.org In-reply-to: (message from Richard Stallman on Mon, 08 May 2006 18:29:13 -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:54128 Archived-At: In article , Richard Stallman writes: > We seem to be talking about two variables here: > unify-8859-on-decoding-mode and utf-fragment-on-decoding. Their roles are as Eli wrote. > Are there any others involved? utf-translate-cjk-mode also plays a role on decoding utf-*. > I do not know what those variables mean. Do they affect the > choice of coding system? Or do they take effect by altering > the meaning of a given coding system? > If it is the former, the Lisp source file can defend against this > problem by specifying coding in the -*- line. We tell people to do this > in Lisp source files. > If it is the latter, there are two possible solutions: > 1. to make the compiler bind these variables to their default values. > 2. to tell people that all Lisp files for which this is relevant > should specify these variables explicitly. The latter. > If it is just those two variables, I think #1 is easy and preferable. > Are there any other variables for which this arises? Just setting those variables doesn't work; they should be customized. In addition, the default value of utf-translate-cjk-mode t, and to which CJK charsets Han characters of Unicode are decoded depends on these: (1) current-language-environment (2) utf-translate-cjk-unicode-range (which also should be customized to take effect), (3) utf-translate-cjk-charsets (4) the contents of the hash table ucs-unicode-to-mule-cjk (a user can freely reflect one's preference on how to decode Unicode character by modifying this hash table). --- Kenichi Handa handa@m17n.org