From: Eidur Eidsson <eidurkr@outlook.com>
To: "libc-locales@sourceware.org" <libc-locales@sourceware.org>
Subject: English locale for Europe – en_150
Date: Mon, 6 Jul 2020 23:38:26 +0000 [thread overview]
Message-ID: <DB8PR04MB6972403CB63E4ED6A38CBDA9AA690@DB8PR04MB6972.eurprd04.prod.outlook.com> (raw)
Hello to you all and thank you for your efforts
I have been wondering whether it would be feasible to include the locale "en_150" in glibc. This is a standard CLDR/ICU-defined locale (not a personal invention) that has been mentioned here before: https://sourceware.org/legacy-ml/libc-locales/2016-q2/msg00245.html .
I have prepared the following prototype by visually inspecting the ICU demonstration at https://icu4c-demos-7hxm2n5zgq-uc.a.run.app/icu-bin/locexp . Of course it would be better to automatically derive the locale from the library itself, but this shows what it could look like. The only immediate problem I can see is the use of "XXX" as a currency code. Perhaps "EUR" could be used instead (and "@euro" appended to the name) although this is strictly not an EU locale.
----------
comment_char %
escape_char /
% This file is part of the GNU C Library and contains locale data.
% The Free Software Foundation does not claim any copyright interest
% in the locale data contained in this file. The foregoing does not
% affect the license of the GNU C Library as a whole. It does not
% exempt you from the conditions of the license if your use would
% otherwise be governed by that license.
% This locale is based on English for region 150 within ICU (icu-project.org). It is characterized by a decimal point, 24-hour clock, little-endian dates, and ISO week-numbering.
LC_IDENTIFICATION
title "English locale for Europe"
source "Free Software Foundation, Inc."
address "https:////www.gnu.org//software//libc//"
contact ""
email "bug-glibc-locales@gnu.org"
tel ""
fax ""
language "English"
territory "Europe"
revision "0.1"
date "2020-07-06"
category "i18n:2012";LC_IDENTIFICATION
category "i18n:2012";LC_CTYPE
category "i18n:2012";LC_COLLATE
category "i18n:2012";LC_TIME
category "i18n:2012";LC_NUMERIC
category "i18n:2012";LC_MONETARY
category "i18n:2012";LC_MESSAGES
category "i18n:2012";LC_PAPER
category "i18n:2012";LC_NAME
category "i18n:2012";LC_ADDRESS
category "i18n:2012";LC_TELEPHONE
category "i18n:2012";LC_MEASUREMENT
END LC_IDENTIFICATION
LC_CTYPE
copy "i18n"
END LC_CTYPE
LC_COLLATE
copy "iso14651_t1"
END LC_COLLATE
LC_MONETARY
int_curr_symbol "XXX "%causes a warning%
currency_symbol "<U00A4>"
mon_decimal_point "."
mon_thousands_sep ","
mon_grouping 3;3
positive_sign ""
negative_sign "-"
int_frac_digits 2
frac_digits 2
p_cs_precedes 0
p_sep_by_space 1
n_cs_precedes 0
n_sep_by_space 1
p_sign_posn 1
n_sign_posn 1
END LC_MONETARY
LC_NUMERIC
decimal_point "."
thousands_sep ","
grouping 3;3
END LC_NUMERIC
LC_TIME
abday "Sun";"Mon";"Tue";"Wed";"Thu";"Fri";"Sat"
day "Sunday";/
"Monday";/
"Tuesday";/
"Wednesday";/
"Thursday";/
"Friday";/
"Saturday"
abmon "Jan";"Feb";/
"Mar";"Apr";/
"May";"Jun";/
"Jul";"Aug";/
"Sep";"Oct";/
"Nov";"Dec"
mon "January";/
"February";/
"March";/
"April";/
"May";/
"June";/
"July";/
"August";/
"September";/
"October";/
"November";/
"December"
d_t_fmt "%A, %e %B %Y %T"
date_fmt "%A, %e %B %Y %T %Z"
d_fmt "%d//%m//%Y"
t_fmt "%T"
am_pm "am";"pm"
t_fmt_ampm ""
first_weekday 2
week 7;19971201;1
END LC_TIME
LC_MESSAGES
yesexpr "^[+1yY]"
noexpr "^[-0nN]"
yesstr "yes"
nostr "no"
END LC_MESSAGES
LC_PAPER
copy "i18n"
END LC_PAPER
LC_TELEPHONE
copy "i18n"
END LC_TELEPHONE
LC_MEASUREMENT
copy "i18n"
END LC_MEASUREMENT
LC_NAME
copy "i18n"
END LC_NAME
LC_ADDRESS
copy "i18n"
END LC_ADDRESS
next reply other threads:[~2020-07-06 23:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 23:38 Eidur Eidsson [this message]
2020-07-07 0:28 ` Carlos O'Donell
2020-07-07 1:36 ` Eidur Eidsson
2020-07-07 17:28 ` English locale for Europe ? en_150 Keld Simonsen
2020-07-09 22:38 ` Eidur Eidsson
2020-07-12 15:57 ` Keld Simonsen
2020-07-13 19:19 ` Eidur Eidsson
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=DB8PR04MB6972403CB63E4ED6A38CBDA9AA690@DB8PR04MB6972.eurprd04.prod.outlook.com \
--to=eidurkr@outlook.com \
--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).