From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Karl Fogel Newsgroups: gmane.emacs.devel Subject: Re: saveplace: don't ask for coding system Date: Mon, 03 Dec 2007 02:59:33 -0800 Message-ID: <87fxykjb6y.fsf@red-bean.com> References: <198E2B70-D060-41D8-8BC2-A9614C2729CC@inf.ed.ac.uk> <06675819-C4A8-4D78-AD59-0A2AF296AC7E@inf.ed.ac.uk> <87ve7gn5zc.fsf@red-bean.com> <0CD94276-1D9F-42BB-A6F7-A90ED9E06817@inf.ed.ac.uk> <87bq98n0ka.fsf@red-bean.com> Reply-To: Karl Fogel NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1196679595 4942 80.91.229.12 (3 Dec 2007 10:59:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 3 Dec 2007 10:59:55 +0000 (UTC) Cc: lekktu@gmail.com, dreitter@inf.ed.ac.uk, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 03 12:00:04 2007 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 1Iz91w-0006pS-FG for ged-emacs-devel@m.gmane.org; Mon, 03 Dec 2007 12:00:04 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Iz91f-000323-V8 for ged-emacs-devel@m.gmane.org; Mon, 03 Dec 2007 05:59:48 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Iz91b-0002z7-Io for emacs-devel@gnu.org; Mon, 03 Dec 2007 05:59:43 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Iz91W-0002sF-Kc for emacs-devel@gnu.org; Mon, 03 Dec 2007 05:59:43 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Iz91W-0002s3-Gr for emacs-devel@gnu.org; Mon, 03 Dec 2007 05:59:38 -0500 Original-Received: from sanpietro.red-bean.com ([66.146.193.61]) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Iz91U-0005vn-Cz; Mon, 03 Dec 2007 05:59:36 -0500 Original-Received: from localhost ([127.0.0.1]:57661) by sanpietro.red-bean.com with esmtp (Exim 4.68) (envelope-from ) id 1Iz91S-0007LP-Fs; Mon, 03 Dec 2007 04:59:34 -0600 In-Reply-To: (Eli Zaretskii's message of "Mon\, 03 Dec 2007 06\:18\:04 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1.50 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) 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:84563 Archived-At: Eli Zaretskii writes: >> Sure, I can port the coding-system change over to the EMACS_22_BASE >> branch > > But please, do not use utf-8 on the EMACS_22_BASE branch: it doesn't > support several character sets that EMACS_22_BASE still uses. (I > don't know why you disregarded discussions of this for the changes on > the trunk, but since the trunk will not be released before the unicode > merge, maybe that's okay.) I didn't disregard the discussions, I simply thought they expressed no clear preference for another coding system over utf-8. If there is a better solution, we should use that, and I'd be happy to make the change. In the thread, you objected to utf-8 because Emacs-mule supports some characters that utf-8 doesn't (I hadn't known that, but I'll take your word for it). However, Juanma pointed out that utf-8 was used for the ido-history file, and that the reason this was okay was that the data is just filenames (as with saveplace); he pointed to a thread on this. In *that* thread, there was no clear conclusion, but the last mail I see is from Kenichi Handa (whose judgement I usually trust!) saying, I think, that utf-8 ought to be fine for filenames, including on the EMACS_22_BASE branch. It would be more helpful if, instead of saying what encoding *not* to use, you (or someone) would say what encoding *to* use, and why :-). Thanks, -Karl