public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebor at roguewave dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/34733] numpunct::grouping() doesn't match libc value for Bulgarian (bg_BG) locale
Date: Sun, 13 Jan 2008 00:14:00 -0000 [thread overview]
Message-ID: <20080112224545.6476.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34733-1186@http.gcc.gnu.org/bugzilla/>
------- Comment #14 from sebor at roguewave dot com 2008-01-12 22:45 -------
bg_BG is the only known example on Linux.
The original bug report we got was for a fr_FR locale on Tru64. I haven't
gone through other locales on Tru64 or any other platforms except for Linux
to see how pervasive such locales might be. I'll keep you posted once I have
more data.
I agree that if the locale is buggy and the bug is rare there's not much
point in spending time on this issue.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34733
next prev parent reply other threads:[~2008-01-12 22:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 2:10 [Bug libstdc++/34733] New: " sebor at roguewave dot com
2008-01-11 2:32 ` [Bug libstdc++/34733] " pcarlini at suse dot de
2008-01-11 3:09 ` sebor at roguewave dot com
2008-01-11 3:18 ` pcarlini at suse dot de
2008-01-11 3:37 ` pcarlini at suse dot de
2008-01-11 3:59 ` sebor at roguewave dot com
2008-01-11 4:00 ` pcarlini at suse dot de
2008-01-11 4:22 ` sebor at roguewave dot com
2008-01-11 4:45 ` pcarlini at suse dot de
2008-01-11 6:06 ` sebor at roguewave dot com
2008-01-11 11:20 ` pcarlini at suse dot de
2008-01-11 18:06 ` sebor at roguewave dot com
2008-01-11 18:10 ` sebor at roguewave dot com
2008-01-12 18:09 ` pcarlini at suse dot de
2008-01-12 18:13 ` pcarlini at suse dot de
2008-01-13 0:14 ` sebor at roguewave dot com [this message]
2008-01-13 1:25 ` pcarlini at suse dot de
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=20080112224545.6476.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).