public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "malabay at yandex dot ru" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug locale/26727] New: sys-libs/glibc : Wrong locale be_BY (LC_MONETARY should be BYN, is BYR)
Date: Mon, 12 Oct 2020 07:34:18 +0000 [thread overview]
Message-ID: <bug-26727-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26727
Bug ID: 26727
Summary: sys-libs/glibc : Wrong locale be_BY (LC_MONETARY
should be BYN, is BYR)
Product: glibc
Version: 2.31
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: locale
Assignee: unassigned at sourceware dot org
Reporter: malabay at yandex dot ru
Target Milestone: ---
The current code of the Belarussian currency is BYN according to ISO 4217
(https://www.currency-iso.org/en/home/tables/table-a1.html )
The current code in glibc has other value:
(https://sourceware.org/git/?p=glibc.git;a=blob;f=localedata/locales/be_BY;h=defb2d782f0efa150eb5ac52e30bfaf13b1c9cb7;hb=HEAD#l105)
LC_MONETARY
int_curr_symbol "BYR "
currency_symbol "<U0440><U0443><U0431>"
mon_decimal_point "."
mon_thousands_sep "<U202F>"
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
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-10-12 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 7:34 malabay at yandex dot ru [this message]
2020-10-12 7:34 ` [Bug locale/26727] " malabay at yandex dot ru
2020-10-12 9:46 ` fweimer at redhat dot com
2020-10-12 12:19 ` slyfox at inbox dot ru
2020-10-12 15:43 ` malabay at yandex dot ru
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-26727-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).