From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Unicode Lisp reader escapes Date: Tue, 09 May 2006 23:20:53 -0400 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> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1147231337 15630 80.91.229.2 (10 May 2006 03:22:17 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 10 May 2006 03:22:17 +0000 (UTC) Cc: emacs-devel@gnu.org, alkibiades@gmx.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 10 05:22:14 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 1FdfHB-0003j9-Ag for ged-emacs-devel@m.gmane.org; Wed, 10 May 2006 05:22:13 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FdfHA-0000aF-S3 for ged-emacs-devel@m.gmane.org; Tue, 09 May 2006 23:22:12 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FdfFv-000067-RH for emacs-devel@gnu.org; Tue, 09 May 2006 23:20:55 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FdfFu-00005Z-U2 for emacs-devel@gnu.org; Tue, 09 May 2006 23:20:55 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FdfFu-00005R-Ml for emacs-devel@gnu.org; Tue, 09 May 2006 23:20:54 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FdfH7-0001YB-0p for emacs-devel@gnu.org; Tue, 09 May 2006 23:22:09 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1FdfFt-0006ux-Pm; Tue, 09 May 2006 23:20:53 -0400 Original-To: Kenichi Handa In-reply-to: (message from Kenichi Handa on Tue, 09 May 2006 14:13:31 +0900) 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:54163 Archived-At: 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 What effect does this have? (Aside from the choice of coding system, that is.) (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). Could you tell me some examples for how users are really expected to use this? Overall: With so many different variables that might affect the reading of these characters, it is just too inconvenient for every file to specify them all. So I think we need a new feature to make that easy to do. Here's one idea. Add a new "variable" `buffer-coding' which is analogous to `coding'. Whereas `coding' specifies the encoding in the file, `buffer-coding' specifies the in-buffer encoding to produce in the buffer. Its value could be a list or plist, which would specify the values of all these many variables. What do you think? If you think this is a good idea, could you try designing the details?