public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dsegan at gmx dot net" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug localedata/549] Fixed ISO-4217 spec for sr_CS locale
Date: Sun, 05 Dec 2004 12:18:00 -0000 [thread overview]
Message-ID: <20041205121815.32382.qmail@sourceware.org> (raw)
In-Reply-To: <20041115151519.549.urke@users.sourceforge.net>
------- Additional Comments From dsegan at gmx dot net 2004-12-05 12:18 -------
My guess is at the same time YU/YUG->CS/SCG change took place: currency code is
defined as starting with ISO 3166 alpha-2 code, as described on eg.
http://encyclopedia.thefreedictionary.com/Currency%20Code :
> The first two letters of the code are the two letters of ISO 3166-1 alpha-2
> (which are similar to those used for national top-level domains on the internet)
> and the third is usually the initial of the currency itself.
I couldn't find any trustworthier source (like page on iso.ch itself).
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=549
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2004-12-05 12:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 15:15 [Bug localedata/549] New: " urke@users.sourceforge.net
2004-11-15 15:17 ` [Bug localedata/549] " urke@users.sourceforge.net
2004-11-15 15:30 ` dsegan@gmx.net
2004-11-15 15:35 ` urke@users.sourceforge.net
2004-11-28 19:22 ` dsegan@gmx.net
2004-12-05 11:37 ` pere at hungry dot com
2004-12-05 12:18 ` dsegan at gmx dot net [this message]
2004-12-10 16:41 ` urke at users dot sourceforge dot net
2005-01-14 18:46 ` pere at hungry dot com
2005-03-21 22:16 ` dsegan at gmx dot net
2005-07-18 1:47 ` cvs-commit at gcc dot gnu dot org
2005-07-18 1:47 ` roland at gnu dot org
2005-07-19 3:31 ` roland at gnu dot org
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=20041205121815.32382.qmail@sourceware.org \
--to=sourceware-bugzilla@sources.redhat.com \
--cc=glibc-bugs@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).