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: Sun, 14 May 2006 19:29:13 -0400 Message-ID: References: <17491.34779.959316.484740@parhasard.net> <17498.27200.911709.330947@parhasard.net> <877j4z5had.fsf@gmx.de> <87irohfrx1.fsf@gmx.de> <87iroarr9i.fsf-monnier+emacs@gnu.org> <87d5egrb4c.fsf-monnier+emacs@gnu.org> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1147665412 20615 80.91.229.2 (15 May 2006 03:56:52 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 15 May 2006 03:56:52 +0000 (UTC) Cc: emacs-devel@gnu.org, handa@m17n.org, alkibiades@gmx.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 15 05:56:50 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 1FfUCO-0000PU-SI for ged-emacs-devel@m.gmane.org; Mon, 15 May 2006 05:56:49 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FfUCO-0007kK-I8 for ged-emacs-devel@m.gmane.org; Sun, 14 May 2006 23:56:48 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FfUCC-0007kF-81 for emacs-devel@gnu.org; Sun, 14 May 2006 23:56:36 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FfUCB-0007k3-JE for emacs-devel@gnu.org; Sun, 14 May 2006 23:56:35 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FfUCB-0007k0-Ba for emacs-devel@gnu.org; Sun, 14 May 2006 23:56:35 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FfQ3s-0008FU-7t for emacs-devel@gnu.org; Sun, 14 May 2006 19:31:44 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1FfQ1R-0002A2-VQ; Sun, 14 May 2006 19:29:14 -0400 Original-To: Stefan Monnier In-reply-to: <87d5egrb4c.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 14 May 2006 09:32:19 -0400) 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:54478 Archived-At: > Handa says that telling people "don't use utf-8" solves the problem. Additionally to "don't use unify-8859-on-decoding" which causes similar problems (which we already bumped into a few years ago when we included unify-8859-on-decoding) with iso8859 chars and coding systems like iso-2022. There is a way for a Lisp file to specify a coding system which isn't utf-8. Is there a way for a Lisp file to specify that unify-8859-on-decoding should not be used when reading it? If not, maybe we should make one. Here's one idea: if the -*- line specifies `coding' and specifies the mode `emacs-lisp' then force unify-8859-on-decoding to nil for that file. That idea has the advantage that most of the Lisp files where this issue might arise won't need any change in order to be assured of DTRT.