public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/23792] New: fr_FR.UTF8 thousands separator is not C++ conforming
Date: Thu, 18 Oct 2018 12:54:00 -0000	[thread overview]
Message-ID: <bug-23792-716@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=23792

            Bug ID: 23792
           Summary: fr_FR.UTF8 thousands separator is not C++ conforming
           Product: glibc
           Version: 2.27
            Status: NEW
          Severity: normal
          Priority: P2
         Component: localedata
          Assignee: unassigned at sourceware dot org
          Reporter: rguenth at gcc dot gnu.org
                CC: libc-locales at sourceware dot org
  Target Milestone: ---

Appearantly C++ says it has to be a single character.  Testcase:

#include <iostream>
#include <locale>

using namespace std;

int
main()
{
  locale::global(locale(""));
  cout.imbue(locale());
  cout << 1000 << endl;
}

> LANG=fr_FR.UTF8 ./a.out 
1�000
> LANG=fr_FR.UTF8 ./a.out | hexdump -c
0000000   1 342   0   0   0  \n                                        
0000006

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2018-10-18 12:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 12:54 rguenth at gcc dot gnu.org [this message]
2018-10-18 12:54 ` [Bug localedata/23792] " rguenth at gcc dot gnu.org
2018-10-18 12:55 ` rguenth at gcc dot gnu.org
2018-10-18 20:01 ` jwakely.gcc at gmail dot com
2018-10-18 20:31 ` fweimer at redhat dot com
2018-10-19 11:52 ` jwakely.gcc at gmail dot com
2018-10-19 18:46 ` carlos at redhat dot com
2024-01-03 16:31 ` maiku.fabian at gmail dot com
2024-01-03 17:18 ` maiku.fabian at gmail 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=bug-23792-716@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --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).