From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/67679 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel,gmane.emacs.gnus.general Subject: Re: gnus should accept UTF8 even if UTF-8 is standard Date: Sat, 25 Oct 2008 11:32:34 +0900 Message-ID: References: <87iqruvs19.fsf@jidanni.org> <86od1mj3z2.fsf@lifelogs.com> <86od1lg3xq.fsf@lifelogs.com> <87d4i1iqpq.fsf@marauder.physik.uni-ulm.de> <86k5c9fzm9.fsf@lifelogs.com> <878wsph5xr.fsf@marauder.physik.uni-ulm.de> <87wsg345oo.fsf@marauder.physik.uni-ulm.de> <86wsg2546l.fsf@lifelogs.com> <86abct3o4s.fsf@lifelogs.com> 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 1224901979 31568 80.91.229.12 (25 Oct 2008 02:32:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 25 Oct 2008 02:32:59 +0000 (UTC) Cc: tzz@lifelogs.com, ding@gnus.org, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 25 04:34:00 2008 connect(): Connection refused 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 1KtYyR-0006PG-EP for ged-emacs-devel@m.gmane.org; Sat, 25 Oct 2008 04:33:55 +0200 Original-Received: from localhost ([127.0.0.1]:40052 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KtYxL-000838-GX for ged-emacs-devel@m.gmane.org; Fri, 24 Oct 2008 22:32:47 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KtYxI-000833-Ch for emacs-devel@gnu.org; Fri, 24 Oct 2008 22:32:44 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KtYxG-00082r-Pa for emacs-devel@gnu.org; Fri, 24 Oct 2008 22:32:43 -0400 Original-Received: from [199.232.76.173] (port=53568 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KtYxG-00082o-KU for emacs-devel@gnu.org; Fri, 24 Oct 2008 22:32:42 -0400 Original-Received: from mx1.aist.go.jp ([150.29.246.133]:39352) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KtYxE-0003GR-FK; Fri, 24 Oct 2008 22:32:40 -0400 Original-Received: from rqsmtp1.aist.go.jp (rqsmtp1.aist.go.jp [150.29.254.115]) by mx1.aist.go.jp with ESMTP id m9P2WaAH026298; Sat, 25 Oct 2008 11:32:36 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp3.aist.go.jp by rqsmtp1.aist.go.jp with ESMTP id m9P2WaU6024784; Sat, 25 Oct 2008 11:32:36 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp3.aist.go.jp with ESMTP id m9P2WY1b013742; Sat, 25 Oct 2008 11:32:34 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken.m17n.org with local (Exim 4.69) (envelope-from ) id 1KtYx8-0003A2-0t; Sat, 25 Oct 2008 11:32:34 +0900 In-reply-to: (rms@gnu.org) 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-operating-system: by monty-python.gnu.org: Solaris 9 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:104977 gmane.emacs.gnus.general:67679 Archived-At: In article , "Richard M. Stallman" writes: > I think completing utf8 to utf-8 is the best solution as you and Stephen > described, so it's worth some code. > It would look strange for completion to make such a change within a > word of the user's input. It may be ok, but let's not forget the > easy alternative: accept that input without having it visibly change > in the minibuffer. > For instance, completing-read could accept a list of alternatives > that are valid if entered, but should not affect completion. Such a behavior can be implemented without a list of alternatives but with a function to find a coding system with loose matching. The only difference with Stephen's proposal is to echo "utf-8" to users or not. By the way, with such a behavior, when one types "utf8 TAB TAB", what completion list should we show? With "utf-8 TAB TAB", these are shown now. utf-8 utf-8-auto utf-8-auto-dos utf-8-auto-mac utf-8-auto-unix utf-8-dos utf-8-emacs utf-8-emacs-dos utf-8-emacs-mac utf-8-emacs-unix utf-8-mac utf-8-unix utf-8-with-signature utf-8-with-signature-dos utf-8-with-signature-mac utf-8-with-signature-unix --- Kenichi Handa handa@ni.aist.go.jp