This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] localedata: en_NL: new English in the Netherlands locale [BZ #14085]
- From: Florian Weimer <fw at deneb dot enyo dot de>
- To: Chris Leonard <cjlhomeaddress at gmail dot com>
- Cc: Mike Frysinger <vapier at gentoo dot org>, libc-alpha <libc-alpha at sourceware dot org>, Pander Musubi <pander at users dot sourceforge dot net>
- Date: Sat, 23 Apr 2016 14:05:23 +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> <CAHdAatZf+6OQrRjBSmOUHw34-TYH0zvNAqA9G3K-1DQE_XmMnw at mail dot gmail dot com>
* Chris Leonard:
> Isn't ease of use ever a consideration here?
Sure.
> Are all decisions, even those not code-driven, but user-driven always
> decided on a "maximum parsimony" basis?
>
> Can you describe the method a novice user of Linux would employ to mix
> and match separate LC_* environment variables?
Some desktop environments already have a per-category locale selector.
I doubt we can ever do without this because for this mixed locale
environments, there won't always be a clear preference, and we can't
tell users that they have to live with it because that's what their
local standards body has decided.
If desktop environments refuse to add the user interface for this, or
can't arrange for the installation or generation of the required
locales, this isn't really our fault. If we aggressively increase the
number of locales, it is likely that only a subset of them make it to
the user due to installation size concerns.