public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "digitalfreak at lingonborough dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/10797] it_IT locale numeric does not have a separator for thousends
Date: Mon, 10 Sep 2018 21:23:00 -0000	[thread overview]
Message-ID: <bug-10797-716-NR1zxb8JtF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-10797-716@http.sourceware.org/bugzilla/>

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

Rafal Luzynski <digitalfreak at lingonborough dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |ASSIGNED
                 CC|                            |digitalfreak@lingonborough.
                   |                            |com

--- Comment #6 from Rafal Luzynski <digitalfreak at lingonborough dot com> ---
1. All links provided in comment 5 consistently confirm that a dot is used as a
grouping (thousands) separator in it_IT, also a comma is used as a decimal
(fraction) separator.  Also CLDR which we usually treat as an authoritative
source confirms the same.  Currently it_IT provides the same except (as the
original reporter noticed) that it does not provide any grouping separator for
LC_NUMERIC.  Therefore I'm going to add a dot as a grouping separator in
LC_NUMERIC in it_IT even if this differs from the original request.  Note that
the same values are currently in LC_MONETARY in it_IT.

2. But CLDR also confirms that a similar mark as the original reporter suggests
is used in it_CH (Italian language as used in Switzerland).  Currently an ASCII
apostrophe is used in glibc but CLDR says it should be a <U2019> character
(Right Single Quotation Mark, "’").  It is correctly transliterated to an ASCII
apostrophe while building non-Unicode locales.  Therefore I'm going to use the
<U2019> character as a grouping separator in LC_NUMERIC in it_CH.

3. But all LC_NUMERIC and LC_MONETARY sections in all Swiss locales (including
LC_MONETARY in it_CH) contain just “copy "de_CH"”.  So maybe LC_NUMERIC should
also contain “copy "de_CH"”?  True, de_CH uses an ASCII apostrophe as a
grouping separator while CLDR says it should be <U2019>.  Also, CLDR says that
a decimal separator for both it_CH and de_CH should be a dot.  In glibc it is
correctly set in all Swiss locales except it_CH.  Shortly: all Swiss locales
should use an apostrophe (or better the Right Single Quotation Mark) as a
grouping (thousands) separator and a dot as a decimal (fraction) separator. 
Therefore instead of what I said in point 2. I am going to use “copy "de_CH"”
in LC_NUMERIC section of it_CH and I'm going to update de_CH to use <U2019> as
a thousands separator in both LC_NUMERIC and LC_MONETARY.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2018-09-10 21:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10797-716@http.sourceware.org/bugzilla/>
2014-02-13  0:58 ` paulschreiber at gmail dot com
2014-07-01  5:56 ` fweimer at redhat dot com
2018-09-10 21:23 ` digitalfreak at lingonborough dot com [this message]
2018-09-10 21:58 ` cvs-commit at gcc dot gnu.org
2018-09-10 22:01 ` digitalfreak at lingonborough dot com
2018-10-08 22:47 ` [Bug localedata/10797] it_IT locale numeric does not have a separator for thousands digitalfreak at lingonborough dot com
2019-01-31 17:19 ` cvs-commit at gcc dot gnu.org
2009-10-17  8:02 [Bug localedata/10797] New: it_IT locale numeric does not have a separator for thousends nicolo dot chieffo at gmail dot com
2009-10-29 17:20 ` [Bug localedata/10797] " drepper at redhat dot com
2009-10-29 17:32 ` nicolo dot chieffo at gmail dot com
2009-10-30  9:37 ` nicolo dot chieffo at gmail dot com
2010-04-09  3:23 ` drepper 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-10797-716-NR1zxb8JtF@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).