[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140724201548.GM16795@example.net>
Date: Thu, 24 Jul 2014 22:15:48 +0200
From: u-igbb@...ey.se
To: musl@...ts.openwall.com
Subject: Re: Locale bikeshed time
On Thu, Jul 24, 2014 at 12:01:50PM -0400, Rich Felker wrote:
> I just meant that language-based locales should match the pattern:
>
> ^[[:lower:]]{2,3}(_[[:upper:]]{2})?([[:punct:]].*)?$
>
> assuming I didn't make any stupid mistakes in writing that regex. And
> non-language-based locales should not match this pattern.
I feel it would be somewhat more robust if we'd have a positive
definition for "the second class" of locale data, just in case we one
day discover that we want to differently handle, say, three classes (?)
A negative defintition gives also very little guidance for the actual
naming and in the worst case may lead to misunderstanding when multiple
parties are involved.
Why not make such a worst case less probable by a somewhat more strict
naming rule?
Possibly also defining "non-language-based" in a positive way?
This is just a thought. I have no actual proposal as I do not have a
good mental picture of which kinds of "non-language-based" definitions
exist or should exist and how they are being used or might/should be used.
Rune
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.
