public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "superherowolverine-sourcewareorg at yahoo dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/14085] en_NL: new locale (English language for the Netherlands)
Date: Tue, 07 May 2019 09:41:00 -0000	[thread overview]
Message-ID: <bug-14085-716-Ac3624YjUV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14085-716@http.sourceware.org/bugzilla/>

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

--- Comment #15 from Robertino <superherowolverine-sourcewareorg at yahoo dot com> ---
https://sourceware.org/bugzilla/show_bug.cgi?id=12624#c3 :
QUOTE
Accepting any such special-interest locale would open a flood.  There is no
reason to have such a locale in glibc.  The localedef utility is standardized
for a reason: locales can be compiled by anyone.

Just create a RPM or whatever which upon installation installs the files and
compiles the locale with localedef.
UNQUOTE

Adding "en_non-en" locales is not flooding.
Let's see what flooding is.

Somehow some people seem to forget that the EU (as we know it now) is a reality
since 1993. There are 24 official languages of the European Union. And 19 EU
member states. There is an internal single market in the EU where by law all
member states have agreed to act as one. Also, EU policies further the free
movement of **people**, goods, services and capital within this internal
market. Yes also people.
Has/Is anyone In The Netherlands working for a company that has Linux desktop
computers in their network and employs English speaking permies or English
speaking freelancers using those Linux computers?
And where more often than not one of the job requirements for native Dutch
speakers is : good (or better) written and spoken English. Because of the mix
of nationalities within the company. We are the USE (United States of Europe)
after all.
Has/Is anyone working for one of the many Japanese companies in The
Netherlands, where speaking and writing English is mandatory?

Has/Is anyone working for a company where Windows sysadmins keep Linux desktops
and laptops off their network and out the door because of locale issues?
Although staff would prefer to use Linux on the dersktop.

Some of the companies in The Netherlands that I worked as a freelance
contractor that had and still have many English speaking freelancers/permies :
ING Bank, ABN AMRO Bank, RABO Bank, MUFG Bank (nee Bank of Tokyo Mitsubishi
UFJ), Canon Europe BV, Kyocera Mita Europe, Cygnific BV (Air France-KLM's
worldwide support), XS4ALL BV (best ISP ever). They all refuse Linux desktops
for this locale issue.

ING Bank encountered major issues after they decided to build their new call
center software on Linux (server and desktop). As you guess the issues were
about locales on the desktop. Yes, they had to roll their own locales. I'm
still grateful that I did not work on that mope and grope project. That was in
late 2008.

You expect us to keep rinsing and repeating the ING effort almost 11 years
later? Almost 26 years after the beginning of the EU ?
Thanks for adding the Euro-sign though. It shaved 2 seconds off the work to
create a new locale. Hail Windows and Hail MacOS for putting in a genuinine
effort to conquer the desktop. Doh! Oops!

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

      parent reply	other threads:[~2019-05-07  9:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 16:33 [Bug localedata/14085] New: English language locale for the Netherlands pander at users dot sourceforge.net
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 [this message]

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-Ac3624YjUV@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).