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: Feature request: multibyte user-full-name Date: Mon, 20 Mar 2006 13:47:36 +0900 Message-ID: References: <87mzft813o.fsf-monnier+emacs@gnu.org> 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 1142830087 17578 80.91.229.2 (20 Mar 2006 04:48:07 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 20 Mar 2006 04:48:07 +0000 (UTC) Cc: emacs-devel@gnu.org, shinra@j10n.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 20 05:48:05 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FLCJG-0000RF-B6 for ged-emacs-devel@m.gmane.org; Mon, 20 Mar 2006 05:48:02 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FLCJF-0007ej-9l for ged-emacs-devel@m.gmane.org; Sun, 19 Mar 2006 23:48:01 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FLCIy-0007c6-RI for emacs-devel@gnu.org; Sun, 19 Mar 2006 23:47:44 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FLCIx-0007aB-Cj for emacs-devel@gnu.org; Sun, 19 Mar 2006 23:47:44 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FLCIx-0007Zw-5D for emacs-devel@gnu.org; Sun, 19 Mar 2006 23:47:43 -0500 Original-Received: from [192.47.44.130] (helo=tsukuba.m17n.org) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FLCOQ-0000jX-Fq for emacs-devel@gnu.org; Sun, 19 Mar 2006 23:53:22 -0500 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 k2K4ldtK011278; Mon, 20 Mar 2006 13:47:39 +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 k2K4lbLB023732; Mon, 20 Mar 2006 13:47:38 +0900 Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1FLCIq-0002JT-00; Mon, 20 Mar 2006 13:47:36 +0900 Original-To: Stefan Monnier In-reply-to: <87mzft813o.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 14 Mar 2006 11:07:47 -0500) 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:51867 Archived-At: Stefan Monnier writes: >>> Anyway, as far as a system allows users to switch locale, I >>> think, pw_gecos must adopt locale-independent encoding, thus >>> the possible encoding is one of UTF-*. And, considering >>> backward compatibility, it should be UTF-8. Then, how about >>> we always decode it by utf-8 (only if it contains a byte >>> with MSB set) while falling back to locale-coding-system >>> (invalid utf-8 sequence is found), and see if that works on >>> any systems? > That sounds like a reasonable plan. AIDA Shinra writes: > Now I support Handa's proposal. It will work in most real sites. Sorry, but I've just noticed that utf-8 decoding doesn't work in init_editfns () (which sets Vuser_full_name) because, at this time, emacs/lisp/international is not yet in Vload_path and thus loading of subst-ksc, etc fails if the name contains CJK chars. :-( It may be possible to delay setting of user-full-name until Vload_path is setup, but I'm not sure it's worth making that kind of nontrivial change at this stage. On the other hand, the same strategy can be implemented in emacs-unicode-2 without such a problem. So, I'm going to do that in that branch. --- Kenichi Handa handa@m17n.org