public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/31205] Inconsistent (mon_)grouping formats
Date: Tue, 02 Jan 2024 16:11:34 +0000	[thread overview]
Message-ID: <bug-31205-716-zAwEfapYUs@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31205-716@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Mike FABIAN <maiku.fabian at gmail dot com> ---
So in the el_GR locale, one could use

grouping -1


instead of 

grouping 0:0


But it does not seem to matter, both do the same:


mfabian@hathi:/local/mfabian/src/glibc/localedata/locales (master $%)
$ grep -E "grouping.*(0;0|-1)" *
C:mon_grouping        -1
C:grouping        -1
POSIX:mon_grouping        -1
POSIX:grouping        -1
aa_DJ:grouping               0;0
ar_SA:mon_grouping      -1
ar_SA:grouping  -1
bs_BA:grouping                  0;0
el_CY:grouping                  0;0
el_GR:grouping                  0;0
eo:grouping      0;0
es_CU:grouping             0;0
gl_ES:grouping             0;0
i18n:mon_grouping        -1
i18n:grouping        -1
mg_MG:grouping                  0;0
pap_AW:grouping                  0;0
pap_CW:grouping                  0;0
pt_PT:grouping                  0;0
rw_RW:grouping                  -1
sl_SI:grouping                  0;0
sr_RS:grouping                  0;0
ti_ER:grouping              0;0
wo_SN:grouping                  0;0
mfabian@hathi:/local/mfabian/src/glibc/localedata/locales (master $%)
$ LC_ALL=rw_RW.UTF-8 /usr/bin/printf "%'f\n" 12345678.9
12345678,900000
mfabian@hathi:/local/mfabian/src/glibc/localedata/locales (master $%)
$ LC_ALL=el_GR.UTF-8 /usr/bin/printf "%'f\n" 12345678.9
12345678,900000
mfabian@hathi:/local/mfabian/src/glibc/localedata/locales (master $%)
$

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

  parent reply	other threads:[~2024-01-02 16:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02 13:28 [Bug localedata/31205] New: " oscar.gustafsson at gmail dot com
2024-01-02 13:29 ` [Bug localedata/31205] " oscar.gustafsson at gmail dot com
2024-01-02 16:04 ` maiku.fabian at gmail dot com
2024-01-02 16:11 ` maiku.fabian at gmail dot com [this message]
2024-01-02 16:14 ` maiku.fabian at gmail dot com
2024-01-02 16:37 ` oscar.gustafsson at gmail dot com
2024-01-18 15:11 ` maiku.fabian at gmail dot com
2024-01-18 15:12 ` maiku.fabian at gmail dot com
2024-01-18 16:11 ` maiku.fabian at gmail dot com
2024-01-19 14:21 ` maiku.fabian at gmail dot com
2024-01-22 14:22 ` maiku.fabian at gmail dot com
2024-01-25 10:41 ` cvs-commit at gcc dot gnu.org
2024-01-25 10:50 ` 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-31205-716-zAwEfapYUs@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).