From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: translation-table-for-input Date: Fri, 13 Feb 2009 12:38:54 +0200 Message-ID: References: Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1234521713 17915 80.91.229.12 (13 Feb 2009 10:41:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 13 Feb 2009 10:41:53 +0000 (UTC) Cc: handa@m17n.org, rms@gnu.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 13 11:43:08 2009 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 1LXvVj-0004MR-L8 for ged-emacs-devel@m.gmane.org; Fri, 13 Feb 2009 11:43:07 +0100 Original-Received: from localhost ([127.0.0.1]:48639 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LXvUP-0007e3-KS for ged-emacs-devel@m.gmane.org; Fri, 13 Feb 2009 05:41:45 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LXvSp-0007Dl-JC for emacs-devel@gnu.org; Fri, 13 Feb 2009 05:40:07 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LXvSj-0007CT-Qq for emacs-devel@gnu.org; Fri, 13 Feb 2009 05:40:06 -0500 Original-Received: from [199.232.76.173] (port=36868 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LXvSj-0007CN-HZ for emacs-devel@gnu.org; Fri, 13 Feb 2009 05:40:01 -0500 Original-Received: from mtaout5.012.net.il ([84.95.2.13]:37812) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LXvSh-0007Qx-7o; Fri, 13 Feb 2009 05:39:59 -0500 Original-Received: from conversion-daemon.i_mtaout5.012.net.il by i_mtaout5.012.net.il (HyperSendmail v2004.12) id <0KF000F002U37W00@i_mtaout5.012.net.il>; Fri, 13 Feb 2009 12:39:11 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([84.229.24.112]) by i_mtaout5.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KF000M6Z2XALFS0@i_mtaout5.012.net.il>; Fri, 13 Feb 2009 12:39:11 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by monty-python.gnu.org: Solaris 9.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:109036 Archived-At: > From: Stefan Monnier > Cc: rms@gnu.org, emacs-devel@gnu.org, handa@m17n.org > Date: Thu, 12 Feb 2009 16:58:54 -0500 > > > I ended up removing the make-obsolete-variable call for > > translation-table-for-input, and instead added a blurb to its doc > > string to discourage its use for unification purposes. > > Please don't. Too late, it's done. > If you really want to fix the warning then either use > with-no-warnings, or just remove the whole feature. > But don't just remove the call to make-obsolete-variable. Based on the discussion that followed my original question, I became convinced that this variable is not obsolete at all. Thus, what I did eventually had nothing to do with eliminating the warning per se. > > No, it's not obsolete. > > The "obsolete" thingy mostly means "slated for removal", AFAIC. So, > yes, it is "obsolete" because I plan to remove it altogether. Declaring something obsolete requires that we name which other feature to use in its stead. Do we have such an alternative in place? > > Its use for character code unification is obsolete, but otherwise > > having a possibility to translate the output of an input method is > > a valuable feature. > > I see no such evidence. My evidence is that there's no alternative to translating the output of an input method. > > I understand Handa-san objected to deleting it in the past. > > Yes, simply out of fear that someone somewhere might use it. Hence the > `make-obsolete-variable' so aso to warn people that if they use it, they > should come and see us I put the same information into the doc string, precisely for that reason.