From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Stefan Newsgroups: gmane.emacs.devel Subject: Re: Rebinding international characters Date: 17 Aug 2004 15:53:56 -0400 Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Message-ID: References: <658l7dju.fsf@wanadoo.es> <200407270250.LAA07100@etlken.m17n.org> <200407280152.KAA09883@etlken.m17n.org> <200407300642.PAA15666@etlken.m17n.org> <200408021244.VAA22947@etlken.m17n.org> <200408030020.JAA24083@etlken.m17n.org> <200408031209.VAA25650@etlken.m17n.org> <2914-Tue03Aug2004220812+0300-eliz@gnu.org> <200408050046.JAA29472@etlken.m17n.org> <3c32jrng.fsf@wanadoo.es> <200408050447.NAA29917@etlken.m17n.org> <20 NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1092772474 21729 80.91.224.253 (17 Aug 2004 19:54:34 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 17 Aug 2004 19:54:34 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 17 21:54:22 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BxA2H-000133-00 for ; Tue, 17 Aug 2004 21:54:22 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BxA6S-0007w6-0t for ged-emacs-devel@m.gmane.org; Tue, 17 Aug 2004 15:58:40 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BxA6L-0007vo-Fz for emacs-devel@gnu.org; Tue, 17 Aug 2004 15:58:33 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BxA6J-0007uh-Qt for emacs-devel@gnu.org; Tue, 17 Aug 2004 15:58:33 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BxA6J-0007ud-Nb for emacs-devel@gnu.org; Tue, 17 Aug 2004 15:58:31 -0400 Original-Received: from [206.47.199.163] (helo=simmts5-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BxA1v-0005kI-GO; Tue, 17 Aug 2004 15:53:59 -0400 Original-Received: from empanada.home ([67.70.164.68]) by simmts5-srv.bellnexxia.net (InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP id <20040817195231.GKIY1635.simmts5-srv.bellnexxia.net@empanada.home>; Tue, 17 Aug 2004 15:52:31 -0400 Original-Received: by empanada.home (Postfix, from userid 502) id 6FF282A559A; Tue, 17 Aug 2004 15:53:57 -0400 (EDT) Original-To: Kenichi Handa In-Reply-To: <200408170714.QAA29316@etlken.m17n.org> Original-Lines: 25 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 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: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:26288 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:26288 > I think (C-1), (F-1), (F-2), (G-2), (H-1), (H-2) are not > good. (C-1) should be 2289, (F-1) (H-1) should be 241, > (F-2) (G-2) (H-2) should be [241]. I think that the --unicode mode is a dead-end (it made sense when it was introduced, but in my mind it's always been a temporary workaround for cases which the multibyte mode doesn't support correctly yet; nowadays multibyte mode behaves sufficiently well that --unibyte mode should be strongly discouraged). Thus I think that neither F-1, G-1, F-2, G-2, or H-2 are wrong (maybe they're not right either, but we shouldn't waste any time on them). I agree that C-1 should be fixed, but that implies doing the translation at a lower level than we currently do. It gets us back to the previous discussion of the relationship betwen function-key-map and key-translation-map and that we should have a key-translation-map-like step before function-key-map. Also we should be careful that applications like xterm-mouse-mode which want to read keyboard input events as binary (even if the rest of the events are normally treated as latin-1 or utf-8) can still do that properly. It shouldn't be a source of problems, but it's still worth remembering. Stefan