[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140723210120.GD11570@brightrain.aerifal.cx>
Date: Wed, 23 Jul 2014 17:01:20 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Locale bikeshed time
On Wed, Jul 23, 2014 at 09:25:03PM +0200, u-igbb@...ey.se wrote:
> On Wed, Jul 23, 2014 at 12:39:07PM -0400, Rich Felker wrote:
> > My leaning would be to use complete
> > files for language-based locales, and file-per-category for individual
> > category locales that are not associated with any particular language
> > (and where, thereby, there's no assumption that they should provide
> > any behavior to other categories).
>
> This feels appropriate - if the definitions indeed fall into distinctive
> classes like "full" / "single-category" and also if the naming reflects
> the distinction (keeping objects with different properties in the same
> name space is otherwise harmful, among others harmful for ease of
> understanding by the prospective users and administrators).
IMO language-based locales should be ll, lll, ll_TT, or lll_TT form
where ll or lll is lowercase ISO language code and TT is uppercase
territory code. Non-language-based locale files should avoid these
patterns.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
