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@sources.redhat.com
Subject: [Bug localedata/14085] New: English language locale for the Netherlands
Date: Wed, 09 May 2012 16:33:00 -0000	[thread overview]
Message-ID: <bug-14085-716@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 14085
           Summary: English language locale for the Netherlands
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: localedata
        AssignedTo: unassigned@sourceware.org
        ReportedBy: pander@users.sourceforge.net
                CC: libc-locales@sources.redhat.com
    Classification: Unclassified


Internationally oriented users who are physically located in the Netherlands
use software mainly in the English language. Therefore they have their systems
usually configured to US English International. However, due to the geographic
location, it can be desirable for certain data to be represented according to
the local Dutch notation while the rest remains in English.

Therefore this locale called en_NL has been created. It is based on en_US and
has some parts from nl_NL. Please see comments starting with "%% use" how each
section has been composed. Note that this specific configuration is difficult
to obtain by using locale nl_NL and setting LANGUAGES to en.

The latest version is available at:
  https://github.com/PanderMusubi/locale-en-nl

Please include this locale in next release.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2012-05-09 16:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 16:33 pander at users dot sourceforge.net [this message]
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
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@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libc-locales@sources.redhat.com \
    /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).