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 to add euro symbol to French-{postfix, alt-postfix, prefix} input methods Date: Sat, 01 Mar 2008 20:22:00 +0900 Message-ID: References: <1203936672.22517.5.camel@Argo.Styx> <87k5ktuf7d.fsf@stupidchicken.com> <87mypo5x1e.fsf@stupidchicken.com> <1204070698.4334.39.camel@Argo.Styx> <878x14lw94.fsf@stupidchicken.com> <87ejawam2n.fsf@catnip.gol.com> <8563w6vipk.fsf@lola.goethe.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: ger.gmane.org 1204370570 19300 80.91.229.12 (1 Mar 2008 11:22:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 1 Mar 2008 11:22:50 +0000 (UTC) Cc: rms@gnu.org, cyd@stupidchicken.com, emacs-devel@gnu.org, nick.steeves@uleth.ca, eliz@gnu.org, miles@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Mar 01 12:23:16 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JVPo4-0001TJ-MG for ged-emacs-devel@m.gmane.org; Sat, 01 Mar 2008 12:23:08 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JVPnX-00067v-Mp for ged-emacs-devel@m.gmane.org; Sat, 01 Mar 2008 06:22:35 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JVPnT-00067F-2A for emacs-devel@gnu.org; Sat, 01 Mar 2008 06:22:31 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JVPnR-00066P-TO for emacs-devel@gnu.org; Sat, 01 Mar 2008 06:22:30 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JVPnR-000662-MR for emacs-devel@gnu.org; Sat, 01 Mar 2008 06:22:29 -0500 Original-Received: from mx1.aist.go.jp ([150.29.246.133]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JVPnD-0003QM-L4; Sat, 01 Mar 2008 06:22:16 -0500 Original-Received: from rqsmtp1.aist.go.jp (rqsmtp1.aist.go.jp [150.29.254.115]) by mx1.aist.go.jp with ESMTP id m21BM3Kk023868; Sat, 1 Mar 2008 20:22:03 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp3.aist.go.jp by rqsmtp1.aist.go.jp with ESMTP id m21BM31g018565; Sat, 1 Mar 2008 20:22:03 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp3.aist.go.jp with ESMTP id m21BM0g8017424; Sat, 1 Mar 2008 20:22:00 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken.m17n.org with local (Exim 4.69) (envelope-from ) id 1JVPmy-0006q3-2O; Sat, 01 Mar 2008 20:22:00 +0900 In-reply-to: <8563w6vipk.fsf@lola.goethe.zz> (message from David Kastrup on Sat, 01 Mar 2008 11:31:35 +0100) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/23.0.60 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) X-detected-kernel: by monty-python.gnu.org: Solaris 8 (1) 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:90979 Archived-At: In article <8563w6vipk.fsf@lola.goethe.zz>, David Kastrup writes: > Eli Zaretskii writes: > > What bothers me is that the same input method suddenly switches the > > encoding I need to use from under my feet, just because I used one > > particular character supported by that input method. > Huh? That's not related to the input method at all. The input method > switches nothing. It is the presence of the character (and in the > unicode-2 branch, we don't even have to unify those characters anymore) > in the buffer that requires some specific coding. > > And on top of that, if I already used some of the characters not in > > Latin-9, my only practical choice is UTF-8. Somehow, this sounds > > wrong to me, but it looks like I'm the only one bothered by that, so > > maybe this problem exists only in my eyes. > It is not related to input methods. In fact, I find it somewhat silly > to have different latin-x input methods at all. Why don't we replace > them all with a single latin-x input method, or with language specific > ones? It seems somewhat pointless to have input methods that > meticulously avoid producing a certain character when this character can > be produced by any number of other means. I can think of one reason to have them. While one is using latin-x-* input methods, he can think that he never type a character not included in latin-x. In other word, if he wants to type a character not supproted by latin-x-* input methods, he must expect that his file can't be saved by latin-x. --- Kenichi Handa handa@ni.aist.go.jp