From owner-freebsd-ports@FreeBSD.ORG Thu Jun 25 06:13:04 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0189F1065670; Thu, 25 Jun 2009 06:13:04 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (unknown [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id C9E6D8FC0C; Thu, 25 Jun 2009 06:13:03 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id n5P6D1Mh096275 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 24 Jun 2009 23:13:02 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id n5P6D1J6096274; Wed, 24 Jun 2009 23:13:01 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA03598; Wed, 24 Jun 09 23:03:29 PDT Date: Wed, 24 Jun 2009 23:01:49 -0700 From: perryh@pluto.rain.com To: tabthorpe@freebsd.org Message-Id: <4a4312cd.yWDVqdLjAXRTY5Bn%perryh@pluto.rain.com> References: <200906181114.43935.tabthorpe@freebsd.org> <200906231506.05001.tabthorpe@freebsd.org> <20090623203608.GB15815@comcast.net> <200906240956.10625.tabthorpe@freebsd.org> In-Reply-To: <200906240956.10625.tabthorpe@freebsd.org> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: corky1951@comcast.net, freebsd-ports@freebsd.org Subject: Re: [RFC] New category proposal, i18n X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jun 2009 06:13:04 -0000 > > If i18n is too cryptic or too alphanumeric, and > > internationalization is too long, why not go with "nls"? > > I personally think that nls is equally as cryptic as i18n or l10n. Anyone care for "intlzn"? It's short, should still tab-complete from "in", and it may be a bit less cryptic than nls, i18n, or l10n.