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: Fri, 02 Jun 2006 15:49:32 +0900 Message-ID: References: <17491.34779.959316.484740@parhasard.net> <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> <87d5e5gwbi.fsf@jurta.org> 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 1149231026 29008 80.91.229.2 (2 Jun 2006 06:50:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 2 Jun 2006 06:50:26 +0000 (UTC) Cc: juri@jurta.org, storm@cua.dk, emacs-devel@gnu.org, monnier@iro.umontreal.ca, alkibiades@gmx.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 02 08:50:24 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 1Fm3UD-0005uY-8q for ged-emacs-devel@m.gmane.org; Fri, 02 Jun 2006 08:50:21 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fm3UC-0001zw-QY for ged-emacs-devel@m.gmane.org; Fri, 02 Jun 2006 02:50:20 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fm3Tw-0001zM-8p for emacs-devel@gnu.org; Fri, 02 Jun 2006 02:50:04 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fm3Tt-0001xw-Ai for emacs-devel@gnu.org; Fri, 02 Jun 2006 02:50:03 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fm3Tt-0001xs-6F for emacs-devel@gnu.org; Fri, 02 Jun 2006 02:50:01 -0400 Original-Received: from [150.29.246.133] (helo=mx1.aist.go.jp) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Fm3aF-0002iu-6E; Fri, 02 Jun 2006 02:56:35 -0400 Original-Received: from smtp1.aist.go.jp ([150.29.246.12]) by mx1.aist.go.jp with ESMTP id k526naBd001647; Fri, 2 Jun 2006 15:49:36 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp1.aist.go.jp with ESMTP id k526nYVx013669; Fri, 2 Jun 2006 15:49:34 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1Fm3TQ-0006Iu-00; Fri, 02 Jun 2006 15:49:32 +0900 Original-To: rms@gnu.org In-reply-to: (message from Richard Stallman on Tue, 23 May 2006 22:18:22 -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:55601 Archived-At: In article , Richard Stallman writes: >> ;; xxx.el -- Do XXX. -*- coding: latin-1!; -*- > Such a notation is not self-evident. What about > ;; xxx.el -- Do XXX. -*- coding: latin-1; translation: no -*- > It would be useful to support the latter as well, > but I think we want something terse for this. I've just installed these changes. (1) Accept something like "latin-1!" as value of coding: in header and local variables section. (2) Accept "char-trans: VAL" in header and local variables section. I think "translation: VAL" is too ambiguous. (3) Accept "enable-character-translation: VAL" in local variables section. In which NEWS section, that information should go? Previously we simply had "* Changes in Emacs XX.YY", but now we have these sections: * Installation Changes in Emacs 22.1 * Startup Changes in Emacs 22.1 * Incompatible Editing Changes in Emacs 22.1 * Editing Changes in Emacs 22.1 * New Modes and Packages in Emacs 22.1 * Changes in Specialized Modes and Packages in Emacs 22.1 * Changes in Emacs 22.1 on non-free operating systems * Incompatible Lisp Changes in Emacs 22.1 * Lisp Changes in Emacs 22.1 * New Packages for Lisp Programming in Emacs 22.1 It seems that this change is "Editing Changes", but I'm not sure we can declare it incompatible or not. Perviously, if a file has "coding: latin-1!", it is treated as an invalid coding specification. In that sense, this change is incompatible, but... --- Kenichi Handa handa@m17n.org