Date: Fri, 26 Jun 2009 09:18:09 +0100 From: Chris Rees <utisoft@googlemail.com> To: "Carlos A. M. dos Santos" <unixmania@gmail.com> Cc: corky1951@comcast.net, perryh@pluto.rain.com, freebsd-ports@freebsd.org, tabthorpe@freebsd.org Subject: Re: [RFC] New category proposal, i18n Message-ID: <b79ecaef0906260118m31525ae2y8e84b40df3ddcc48@mail.gmail.com> In-Reply-To: <e71790db0906251751g23bead87ped37a90c4a067024@mail.gmail.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> <b79ecaef0906250124w4254e1dcve32f916d2e077eec@mail.gmail.com> <e71790db0906251751g23bead87ped37a90c4a067024@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/6/26 Carlos A. M. dos Santos <unixmania@gmail.com>: > On Thu, Jun 25, 2009 at 5:24 AM, Chris Rees<utisoft@googlemail.com> wrote= : >> 2009/6/25 =A0<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. > > Guys, you have been discussing the category *name* for eight days now > without reaching a consensus. This is becoming somewhat boring. Please > do not reinvent the wheel. Whether you like it or not, i18n is a well > established and widely accepted acronym. > Very sorry, we'll shut up and have it YOUR way. 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?b79ecaef0906260118m31525ae2y8e84b40df3ddcc48>