This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] localedata: en_NL: new English in the Netherlands locale [BZ #14085]
- From: Pander <pander at users dot sourceforge dot net>
- To: Florian Weimer <fw at deneb dot enyo dot de>
- Cc: libc-alpha at sourceware dot org
- Date: Sat, 23 Apr 2016 16:46:54 +0200
- Subject: Re: [PATCH] localedata: en_NL: new English in the Netherlands locale [BZ #14085]
- Authentication-results: sourceware.org; auth=none
- References: <1461298610-19221-1-git-send-email-vapier at gentoo dot org> <87a8klk4jp dot fsf at mid dot deneb dot enyo dot de> <D44674DF-E470-43C5-B667-22EBDE618CCC at users dot sourceforge dot net> <20160422212338 dot GG5369 at vapier dot lan> <87ziskjzyt dot fsf at mid dot deneb dot enyo dot de>
On 23 April 2016 14:01:46 CEST, Florian Weimer <email@example.com> wrote:
>* Mike Frysinger:
>> Florian's point is that for most categories, you can (mostly) get
>> export LANG=nl_NL.UTF8
>> export LC_MESSAGES=en_US.UTF8
>> export LC_NAME=en_US.UTF8
>> i would contend that for the average user, they'll be using a DE that
>> a GUI where there is a settings panel for them to easily select how
>> want the time/date/currency/etc... to be displayed.
>Right, and some versions of KDE have such separated locale selectors.
>>> Adding this locale will not result in an explosion of additional
>>> locales, as no other languages than English are linga franca. There
>>> is also Danmark English one, I believe. If you could measure the
>>> eventual usage, this locale will be very in much in demand and usage
>>> in the Netherlands.
>> with ~250 territories defined today, we're talking about ~250 for
>> alone. that is kind of an explosion considering we have ~330 locales
>> in glibc, and only ~20 of them are for English.
>My worry is that for locales such as en_NL, there is no reference what
>the ârightâ settings should be. (See my other message.)
For me, as a Dutch person and having a lot of experience with standards, I know this is the optimal and 'right' settings for en_NL. Do you know independent Dutch developers that can review it? I have been offering this via GitHub for many years with no requests for changes.