public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/14085] en_NL: new locale (English language for the Netherlands)
Date: Wed, 19 Jul 2017 13:38:00 -0000	[thread overview]
Message-ID: <bug-14085-716-GNNyNiWp4G@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14085-716@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=14085

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |carlos at redhat dot com
         Resolution|---                         |WONTFIX

--- Comment #12 from Carlos O'Donell <carlos at redhat dot com> ---
There is no consensus, and in fact there is opposition to the addition of en_*
locales for all countries that deal with English. Stated reasons include: size
of install, increased number of locales to pick from, complexity on the user
side for selecting those locales (Chris Leonard's "maximum parsimony" theory
;-)). Instead the generally accepted idea is that you should mix-and-match the
LC_* variables as needed, with the knowledge that this is not the most flexible
way to solve this problem. Individual distributions are free to include
whatever en_* locales they wish to build to suit their users. Likewise, users
can do the same thing.

Therefore until there is consensus formed around this issue I'm marking this
bug as RESOLVED/WONTFIX.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2017-07-19 13:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 16:33 [Bug localedata/14085] New: English language locale for the Netherlands pander at users dot sourceforge.net
2012-07-15 15:03 ` [Bug localedata/14085] " mistresssilvara at hotmail dot com
2014-06-25 12:09 ` fweimer at redhat dot com
2016-02-19 10:48 ` [Bug localedata/14085] en_NL: new locale (English language for the Netherlands) vapier at gentoo dot org
2016-04-22  4:22 ` vapier at gentoo dot org
2016-04-22 22:02 ` vapier at gentoo dot org
2016-04-23 10:29 ` programming at ertai dot nl
2016-04-25  9:31 ` pander at users dot sourceforge.net
2016-04-25 21:04 ` vapier at gentoo dot org
2016-04-26 10:47 ` pander at users dot sourceforge.net
2016-11-15 11:58 ` superherowolverine-sourcewareorg at yahoo dot com
2016-11-15 12:13 ` pander at users dot sourceforge.net
2017-07-19 12:19 ` maiku.fabian at gmail dot com
2017-07-19 12:37 ` pander at users dot sourceforge.net
2017-07-19 13:38 ` carlos at redhat dot com [this message]
2017-07-19 13:39 ` carlos at redhat dot com
2017-07-19 15:18 ` pander at users dot sourceforge.net
2019-05-07  9:41 ` superherowolverine-sourcewareorg at yahoo dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-14085-716-GNNyNiWp4G@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libc-locales@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).