public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "pander at users dot sourceforge.net" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/22473] Suggestion: Introduce en_EU locale
Date: Fri, 21 Dec 2018 10:51:00 -0000	[thread overview]
Message-ID: <bug-22473-716-MSGqHB34BI@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 #7 from Pander <pander at users dot sourceforge.net> ---
I understand that the footprint needs to be as minimal as possible, and I'm
thinking how we could solve that the best. For example
https://www.sourceware.org/bugzilla/show_bug.cgi?id=24006 would enable more
minimization when needed.

Also https://www.sourceware.org/bugzilla/show_bug.cgi?id=14641 would free up
some space.

en_NL is indeed not in glibc, as is en_DE and en_SE. Only en_DK is, because it
was introduced early on. To reduce size and accommodate more practical use, I
would sooner propose removing li_NL, nds_NL, nds_DE and alike. See also
https://www.sourceware.org/bugzilla/show_bug.cgi?id=23857 for reasons.

There are more and more users in EU countries using their system in English
(and prefer to have correct support for their locale datetime, currency, etc.)
than there are users that want to use their system in their very very local
language such as:
- Upper Sorbian (hsb_DE)
- Lower Sorbian (dsb_DE)-
- Low German/Saxon/Nedersaksisch (nds_DE and nds_NL)
- Frisian (fy_DE and fy_NL)
- Limburgs (li_NL and li_BE)
which don't even have a spell checker or wide localization of applications.
These locales have practically no users, whereas most developers in EU
countries work in the English language but are in need of proper support of
datetime, currenct, etc.

Perhaps even join fr_BE and wa_BE, to free up even more space.

Locale en_EU is gonna give a lot of confusion, remarks and struggles over which
exact formats should be used, as they differ substantially among EU countries,
even/especially the larger countries.

In my opinion, better to trade the before mentioned locales for en_DE, en_SE,
en_NE, etc.

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

  parent reply	other threads:[~2018-12-21 10:51 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
2018-12-21 10:51 ` pander at users dot sourceforge.net [this message]
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-MSGqHB34BI@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).