public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Pander <pander@users.sourceforge.net>
Cc: Mike Frysinger <vapier@gentoo.org>, libc-alpha@sourceware.org
Subject: Re: [PATCH] localedata: en_NL: new English in the Netherlands locale [BZ #14085]
Date: Sat, 23 Apr 2016 12:14:00 -0000	[thread overview]
Message-ID: <87r3dwjzec.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <0C28F4FA-7780-4DFD-90E8-054AFE1D7346@users.sourceforge.net> (pander@users.sourceforge.net's message of "Sat, 23 Apr 2016 00:27:04 +0200")

> I understand you are playing the devils advocate. Thanks for
> that. Suppose that for all territories English is added, that will, at
> a maximum, double the number of locales, only once.
>
> That is manageable. Computers nowadays can handle that amount with
> ease.

The current dominant criticism of glibc is related to installation
size (search for Docker and Alpine Linux if you aren't aware).  As
always, the situation is more complex than some of the reports
suggest, but adding a few dozen megabytes to the installation is
probably not such a good idea.

> At the moment, remixing LC sections is not supported by any of the
> main GNU/Linux installers or by command line configuration tools or by
> configuration tools for GNOME, KDE, etc.

Not quite true.  It was supported in KDE; it had a separate selector
for LC_MESSAGES at least.  The KDE people removed it at one point
because there was no need.  If they have not added it back yet, I
think this shows this feature is not actually needed, and neither are
English locale variants.

I don't want glibc to be the place where contested decisions by
desktop environments are worked around.  If the people actually
working on end user interfaces determine that mixed locale settings
are not needed, who are we to second-guess them?  They have many more
interactions with such users than we do.

> As long as no progress is made in usability in installers and
> configuration tools, I would see fit that en_NL is added. It can
> always be removed if more elegant alternatives become available.

If the locale has actual users, we can't remove it that easily.

  parent reply	other threads:[~2016-04-23 12:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22  4:17 Mike Frysinger
2016-04-22 15:19 ` Chris Leonard
2016-04-22 16:10 ` Florian Weimer
2016-04-22 19:07   ` mix/match lang/territory (was: [PATCH] localedata: en_NL: new English in the Netherlands locale [BZ #14085]) Mike Frysinger
2016-04-23 12:01     ` mix/match lang/territory Florian Weimer
2016-04-22 19:13   ` [PATCH] localedata: en_NL: new English in the Netherlands locale [BZ #14085] Chris Leonard
2016-04-23 12:05     ` Florian Weimer
2016-04-23 13:18       ` Chris Leonard
2016-04-23 14:57     ` Pander
2016-04-23 15:03       ` Florian Weimer
2016-04-23 19:51         ` Pander
2016-04-22 20:28   ` Pander
2016-04-22 21:23     ` Mike Frysinger
2016-04-23 12:01       ` Florian Weimer
2016-04-23 14:47         ` Pander
     [not found]       ` <0C28F4FA-7780-4DFD-90E8-054AFE1D7346@users.sourceforge.net>
2016-04-23 12:14         ` Florian Weimer [this message]
2016-04-23 14:41           ` Pander
2016-04-25 13:13     ` Marko Myllynen
2016-04-23 11:15 ` Florian Weimer

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=87r3dwjzec.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=libc-alpha@sourceware.org \
    --cc=pander@users.sourceforge.net \
    --cc=vapier@gentoo.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).