From owner-freebsd-i18n Sun Jun 3 0:35:39 2001 Delivered-To: freebsd-i18n@freebsd.org Received: from mail.mk.bsdclub.org (adsl2049.ea.rim.or.jp [202.247.148.49]) by hub.freebsd.org (Postfix) with ESMTP id 6373937B422; Sun, 3 Jun 2001 00:35:32 -0700 (PDT) (envelope-from motoyuki@mk.bsdclub.org) Received: from sakura.mk.bsdclub.org (sakura.mk.bsdclub.org [3ffe:505:2022:0:2a0:c9ff:fe20:9aff]) by mail.mk.bsdclub.org (8.11.3+3.4W/3.7W/smtpfeed 1.12) with ESMTP/inet6 id f537ZUW12765; Sun, 3 Jun 2001 16:35:30 +0900 (JST) Received: from sakura.mk.bsdclub.org (localhost.mk.bsdclub.org [127.0.0.1]) by sakura.mk.bsdclub.org (8.11.3/3.7W) with ESMTP/inet id f537ZU500581; Sun, 3 Jun 2001 16:35:30 +0900 (JST) Message-Id: <200106030735.f537ZU500581@sakura.mk.bsdclub.org> To: "Andrey A. Chernov" Cc: Motoyuki Konno , CHOI Junho , i18n@FreeBSD.ORG, audit@FreeBSD.ORG Subject: Re: 2CFR: locale names renaming From: Motoyuki Konno X-Mailer: mh-e on Mule 2.3 / Emacs 19.34.1 References: <20010602040851.A34526@nagual.pp.ru> <86ofs7thvy.fsf@gradius.wdb.co.kr> <20010602143139.A43237@nagual.pp.ru> <200106021345.f52DjJ218044@sakura.mk.bsdclub.org> <20010603002153.A48861@nagual.pp.ru> <200106030035.f530Zu247879@sakura.mk.bsdclub.org> <20010603092746.A53677@nagual.pp.ru> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Sun, 03 Jun 2001 16:35:30 +0900 Sender: owner-freebsd-i18n@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Andrey A. Chernov" wrote: > > If so, why both ru_SU.* and ru_RU.* co-exist in 4-stable? > > They should not. ru_SU should be deleted. I don't have -stable machine > available and can't devote time for its development, so don't know > exact state of -stable changes made by other people. I want to say is: Russian FreeBSD users had a very long time to change their locale name setting (from ru_SU.* to ru_RU.*). Both locale name (ru_SU.* and ru_RU.*) co-exist in FreeBSD 4.*-RELEASE. Japanese (and Korean and Chinese) FreeBSD users also want enough time to change locale name setting. Immediate transition (for example, from ja_JP.EUC to ja_JP.eucJP) is not fair. > > 5-current (5-stable after 5.0-RELEASE) branch : both old and new locale > > It is already impossible, -current and -stable locales are incompatible. Probably, you misunderstand my mail. "old and new local" I said is "locale name". It is possible to support both old (ja_JP.EUC, ko_KO.EUC, ...) and new (ja_JP.eucJP, ko_KO.eucKO, ...) locale name. I propose the following plan: -------- old locale name : ja_JP.EUC, ko_KO.EUC, zh_CN.EUC, zh_TW.Big5 new locale name : ja_JP.eucJP, ko_KO.eucKO, zh_CN.eucCN, zh_TW.BIG5 Plan for 5-current (5-stable after 5.0-RELEASE) branch: support both old locale name and new locale name Plan for future 6-current branch: delete old locale name. only support new locale name. -------- -- ------------------------------------------------------------------------ Motoyuki Konno motoyuki@bsdclub.org (Home) motoyuki@FreeBSD.ORG (FreeBSD Project) http://www.freebsd.org/~motoyuki/ (WWW) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-i18n" in the body of the message