Date: Thu, 25 Jun 2009 09:24:07 +0100 From: Chris Rees <utisoft@googlemail.com> To: perryh@pluto.rain.com Cc: corky1951@comcast.net, freebsd-ports@freebsd.org, tabthorpe@freebsd.org Subject: Re: [RFC] New category proposal, i18n Message-ID: <b79ecaef0906250124w4254e1dcve32f916d2e077eec@mail.gmail.com> In-Reply-To: <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> <4a4312cd.yWDVqdLjAXRTY5Bn%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/6/25 <perryh@pluto.rain.com>: >> > 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"? =A0It's short, should still tab-complete > from "in", and it may be a bit less cryptic than nls, i18n, or l10n. I was thinking intl, but your suggestion's better. Chris --=20 A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in a mailing list?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b79ecaef0906250124w4254e1dcve32f916d2e077eec>