public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "digitalfreak at lingonborough dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/22473] Suggestion: Introduce en_EU locale
Date: Fri, 21 Dec 2018 10:25:00 -0000	[thread overview]
Message-ID: <bug-22473-716-CBsDNBvStw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22473-716@http.sourceware.org/bugzilla/>

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

--- Comment #6 from Rafal Luzynski <digitalfreak at lingonborough dot com> ---
There is no en_NL locale in glibc.  I believe you are talking about a different
project, maybe about some non-upstream patches for glibc.  Of course, localedef
tool exists in order to allow the users build and use their own locales, even
without the root permissions.  So you may have and use whatever locale you
want.  However, I'm trying here to avoid inflation of locales.  The problem is
that each new locale, even if it source code is short and easy to implement,
makes about 2 MB binaries.  This multiplied by about 200 or 300 locales we
currently provide may make a problem.  Distros are already complaining about it
because the locale binaries take too much space both in installation media and
in the users' computers.

Of course, en_EU will not work for everyone.  Even if it works for 8 or 12
countries I'd be satisfied.

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

  parent reply	other threads:[~2018-12-21 10:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22  6:03 [Bug localedata/22473] New: " digitalfreak at lingonborough dot com
2017-11-22 15:39 ` [Bug localedata/22473] " piotrdrag at gmail dot com
2017-11-22 18:53 ` schwab@linux-m68k.org
2017-11-22 19:18 ` egmont at gmail dot com
2017-11-23 14:50 ` fweimer at redhat dot com
2017-11-24 19:20 ` jwilk at jwilk dot net
2017-11-28 23:14 ` digitalfreak at lingonborough dot com
2017-11-29  7:42   ` Keld Simonsen
2017-11-29  7:43 ` keld at keldix dot com
2018-12-20  8:18 ` pander at users dot sourceforge.net
2018-12-21 10:25 ` digitalfreak at lingonborough dot com [this message]
2018-12-21 10:51 ` pander at users dot sourceforge.net
2019-09-16  8:47 ` robert.pollak at posteo dot net
2021-11-08 23:40 ` sergio.callegari at gmail 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-22473-716-CBsDNBvStw@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).