public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "myllynen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug localedata/12961] New: *_sign_posn settings in locales ignored
Date: Tue, 05 Jul 2011 20:17:00 -0000	[thread overview]
Message-ID: <bug-12961-131@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=12961

           Summary: *_sign_posn settings in locales ignored
           Product: glibc
           Version: 2.14
            Status: NEW
          Severity: minor
          Priority: P2
         Component: localedata
        AssignedTo: libc-locales@sources.redhat.com
        ReportedBy: myllynen@redhat.com


http://www.open-std.org/jtc1/sc22/wg14/www/docs/n714.htm describes how
p_sign_posn and n_sign_posn should affect on monetary related output. However,
it would seem that any setting of p_sign_posn or n_sign_posn in locale data
doesn't change output at all with glibc.

This is the test program I used:

#include <locale.h>
#include <monetary.h>
#include <stdio.h>
#include <stdlib.h>

int main(int argc, char **argv)
{
  char buf[256];
  setlocale(LC_MONETARY, "");
  strfmon(buf, sizeof(buf), "[%=*+16#8.2n] [%=*+16#8.2i]", 123456.789,
-123456.789);
  printf("%s\n", buf);
  exit(EXIT_SUCCESS);
}

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2011-07-05 20:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05 20:17 myllynen at redhat dot com [this message]
2011-07-20 10:23 ` [Bug localedata/12961] " schwab@linux-m68k.org
2014-06-27 12:58 ` fweimer at redhat 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-12961-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --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).