From owner-freebsd-stable Sat Jan 5 9: 5:18 2002 Delivered-To: freebsd-stable@freebsd.org Received: from castle.jp.FreeBSD.org (castle.jp.FreeBSD.org [210.226.20.15]) by hub.freebsd.org (Postfix) with ESMTP id 8F2C637B405; Sat, 5 Jan 2002 09:05:11 -0800 (PST) Received: from localhost (localhost [::1]) by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet6 id g05H59m39277; Sun, 6 Jan 2002 02:05:09 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: stable@freebsd.org, re@freebsd.org In-Reply-To: <20020105183137.A79023@ark.cris.net> References: <20020105183137.A79023@ark.cris.net> X-User-Agent: Mew/1.94.2 XEmacs/21.5 (alfalfa) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 40 From: Makoto Matsushita To: phantom@freebsd.org Subject: Re: HEADSUP: several locale renames were MFCed Date: Sun, 06 Jan 2002 02:05:07 +0900 Message-Id: <20020106020507J.matusita@jp.FreeBSD.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG phantom> I've just MFCed following several locale renames Sigh. Japanese locale name, ja_JP.eucJP, and tcsh problem is *not yet* solved. Release engineers, why you allow to do that? I cannot believe that this change is MFCed; ache, the man who changed the locale name in 5-current, what do you think about this MFC? Tcsh have a feature that it does set 'dspmbyte' variable if and only if locale name is "ja_JP.EUC" (string match is performed) or other Chinese, Japanese, and Korean locales. Now the locale name was changed; we've miss the feature. Of course, 5-current tcsh is broken also. A patch to fix this problem was already submitted to the tcsh author IIRC, but it works only for 5-current. Maybe new patch will be submitted to the author ASAP, but... Phantom, would you please: 1a) check if tcsh repository was modified to fix this problem, 1b) make a request to the tcsh author to incorporate that fix if not yet, 2) import a fixed tcsh source to FreeBSD repository, 3) and send a HEADSUP to current@FreeBSD.org and stable@FreeBSD.org about all tcsh-and-locale problems are gone away. phantom> In case if you'll experience any problems in locale specific phantom> areas please notice me immidiately. Immidiately enough? :-) phantom> PS: for most of old locale names compatibility shims are phantom> present, except DIS_* -> ISO*-15. So, be adviced and switch phantom> to ISO8859-15 if you've used DIS_* before. All shims does nothing to this problem, since tcsh compares current LANG variable string and 'ja_JP.EUC' string, yes, just a string match. -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message