public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nilgun at belgeler dot org" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug localedata/187] wrong grouping and decimal point in tr_TR LC_NUMERIC
Date: Sat, 14 Aug 2004 07:44:00 -0000 [thread overview]
Message-ID: <20040814074423.21017.qmail@sourceware.org> (raw)
In-Reply-To: <20040529151215.187.deniz@arayan.com>
------- Additional Comments From nilgun at belgeler dot org 2004-08-14 07:44 -------
(In reply to comment #2)
> I've asked the original locale author Keld Simonsen to comment
> on this change request. I aldo tried to reach an earlier
> contributor, "Nilg~n Belma Bug~ner", but his email address bounced.
>
The grammar rules published by the Turkish Language Institution (TDK)
make no distinciton between monetary and numerical representations.
However the monetary representation has gained public recognition
because of the stress placed on this matter by the Turkish
Ministry of Finance. Nevertheless this representation is not as
well defined as in the documentation of th GNU C libraries
(probably because the related rule set was prepared during the pre-IT era).
On the other hand, due to the international nature of the scientific
publications, the numerical representation has not been as widely
accepted as the monetary representation. The fix I have sent you uses
the publically accepted form of the rules that were left unspecified
by the Turkish Language Institution.
It is possible not to make any grouping using the strfmon function.
Therefore the same tersary grouping can be used in the numerical
representation as in the monetary representation. The substitution of
period with comma is possible by assigning "C" to the LC_NUMERIC variable.
Consequently the current number representations adopted by the Turkish
Language Institution can be used both in the numerical and in the monetary
representations, provided that their grammar rules stay the same
(if not changed in the grammar rules currently being revised).
In order to end the current debate, the patch sent in can be assumed
valid a priori.
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=187
------- 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-08-14 7:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 15:12 [Bug localedata/187] New: " deniz at arayan dot com
2004-05-29 15:13 ` [Bug localedata/187] " deniz at arayan dot com
2004-07-17 8:46 ` pere at hungry dot com
2004-08-09 7:47 ` drepper at redhat dot com
2004-08-10 6:08 ` deniz at arayan dot com
2004-08-10 6:23 ` deniz at arayan dot com
2004-08-10 7:11 ` pere at hungry dot com
2004-08-10 7:25 ` deniz at arayan dot com
2004-08-14 7:44 ` nilgun at belgeler dot org [this message]
2004-10-31 13:22 ` pere at hungry dot com
2004-10-31 14:06 ` pere at hungry dot com
2004-10-31 14:11 ` [Bug localedata/187] [PATCH] tr_TR:LC_NUMERIC should use comma decimal point and 3 digit grouping pere at hungry dot com
2004-10-31 20:48 ` cvs-commit at gcc dot gnu dot org
2004-10-31 22:14 ` pere at hungry 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=20040814074423.21017.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).