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: po file charset via auto-coding-functions Date: Mon, 24 Oct 2005 10:53:58 +0900 Message-ID: References: <87zmp399ue.fsf@zip.com.au> <87ll0ma3ow.fsf@zip.com.au> <87zmp1f9np.fsf@zip.com.au> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1130118921 2299 80.91.229.2 (24 Oct 2005 01:55:21 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 24 Oct 2005 01:55:21 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 24 03:55:10 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1ETrXW-0007YE-J8 for ged-emacs-devel@m.gmane.org; Mon, 24 Oct 2005 03:54:19 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ETrXV-0002Ri-VC for ged-emacs-devel@m.gmane.org; Sun, 23 Oct 2005 21:54:18 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ETrXI-0002Q7-JC for emacs-devel@gnu.org; Sun, 23 Oct 2005 21:54:04 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ETrXG-0002NY-Vp for emacs-devel@gnu.org; Sun, 23 Oct 2005 21:54:04 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ETrXG-0002NQ-RI for emacs-devel@gnu.org; Sun, 23 Oct 2005 21:54:02 -0400 Original-Received: from [192.47.44.130] (helo=tsukuba.m17n.org) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1ETrXG-0003Dz-Ok for emacs-devel@gnu.org; Sun, 23 Oct 2005 21:54:03 -0400 Original-Received: from nfs.m17n.org (nfs.m17n.org [192.47.44.7]) by tsukuba.m17n.org (8.13.4/8.13.4/Debian-3) with ESMTP id j9O1s0rQ024518; Mon, 24 Oct 2005 10:54:00 +0900 Original-Received: from etlken (etlken.m17n.org [192.47.44.125]) by nfs.m17n.org (8.13.4/8.13.4/Debian-3) with ESMTP id j9O1s0YS026888; Mon, 24 Oct 2005 10:54:00 +0900 Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1ETrXC-00082K-00; Mon, 24 Oct 2005 10:53:58 +0900 Original-To: Kevin Ryde In-reply-to: <87zmp1f9np.fsf@zip.com.au> (message from Kevin Ryde on Sun, 23 Oct 2005 08:51:06 +1000) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.50 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) 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:44671 Archived-At: In article <87zmp1f9np.fsf@zip.com.au>, Kevin Ryde writes: > Kenichi Handa writes: >> >> And, functions in auto-coding-functions is called on any >> file, but currently, po-find-file-coding-system is called >> only on *.po file. I'm not sure which is better, but at >> least there's a difference. > I guess if the file contents are unambiguous, or near enough so, then > it may actually be a good thing to ignore the filename. In general, I agree. But, for that, a function to detect a coding system has to check if the contents is surely in an expected format in advance. For instance, in the case of po-find-file-coding-system, it has to check if the file is surely PO file. But, it seems that the current po.el doesn't do that but expects that it is called only on PO file. > Maybe the auto-coding-functions could be called with the filename too, > so they could restrict themselves if they felt the need. > find-auto-coding has that available for the calls, or document that > `filename' is bound, or whatever. Yes, if a function in auto-coding-functions can check a filename too, the above problem disappears (or at least Emacs can perform the same operation as now). But, I don't want to change an API at this moment, especially when we can fix the problem by the other method (as in my previous mail). --- Kenichi Handa handa@m17n.org