From: "digitalfreak at lingonborough dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/22473] New: Suggestion: Introduce en_EU locale
Date: Wed, 22 Nov 2017 06:03:00 -0000 [thread overview]
Message-ID: <bug-22473-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=22473
Bug ID: 22473
Summary: Suggestion: Introduce en_EU locale
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: digitalfreak at lingonborough dot com
CC: libc-locales at sourceware dot org
Target Milestone: ---
Following the previous discussion on the alpha mailing list [1] I suggest to
introduce en_EU locale. It should be useful for the people who live in
non-English speaking European countries but want to use the English user
interface having their local settings for other things like metric system,
paper size, etc. So far workaround solutions have been used like en_SE, en_DK,
en_NL, also used in other countries. The en_EU locale would mean a generic
European locale without favoring one or few countries. ISO currently marks EU
country code as exceptionally reserved for European Union [2] which is kinda
good but my initial idea was that EU may mean both European Union and whole
Europe (including also non-EU countries). The yesexpr and noexpr entries should
include the Y/N answers for as many languages as possible.
The idea is not to drop en_DK immediately although these locales can use "copy
en_EU" if it makes sense.
[1] https://sourceware.org/ml/libc-alpha/2017-08/msg00308.html
[2] https://www.iso.org/obp/ui/
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-11-22 6:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 6:03 digitalfreak at lingonborough dot com [this message]
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
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@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).