public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug localedata/16777] New: Incorrect thousands separator in pl_PL locale
@ 2014-03-29 18:29 mgorny at gentoo dot org
  2014-03-31  7:10 ` [Bug localedata/16777] " myllynen at redhat dot com
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: mgorny at gentoo dot org @ 2014-03-29 18:29 UTC (permalink / raw)
  To: glibc-bugs

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

            Bug ID: 16777
           Summary: Incorrect thousands separator in pl_PL locale
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: localedata
          Assignee: unassigned at sourceware dot org
          Reporter: mgorny at gentoo dot org
                CC: libc-locales at sourceware dot org

Currently, glibc lists the following for pl_PL locale:

- no thousands separator in LC_NUMERIC section,

- '.' as thousands separator in LC_MONETARY section.

While actually, a non-breaking space is used as thousands separator in both
cases. However, I'm not sure if it is correct to use <U00A0> in locales or if
<U0020> should be used instead.

It should be also noted that the grouping is used only for numbers having more
than 4 digits, i.e. '4000' does not use grouping, '40 000' and '4 000 000' do
on 3-digit groups. I don't know if it is possible to express this in current
glibc localedata format.

References:

1. opinion given by a linguist:
   http://poradnia.pwn.pl/lista.php?id=9842

2. EU publication guidelines:
   http://publications.europa.eu/code/pl/pl-360500.htm

3. example law act, having numbers e.g. on page 111 (PDF):
   http://isip.sejm.gov.pl/Download?id=WDU19910800350&type=3

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug localedata/16777] Incorrect thousands separator in pl_PL locale
  2014-03-29 18:29 [Bug localedata/16777] New: Incorrect thousands separator in pl_PL locale mgorny at gentoo dot org
@ 2014-03-31  7:10 ` myllynen at redhat dot com
  2014-06-12 19:51 ` fweimer at redhat dot com
  2015-10-11  0:25 ` [Bug localedata/16777] pl_PL: incorrect thousands separator in locale vapier at gentoo dot org
  2 siblings, 0 replies; 4+ messages in thread
From: myllynen at redhat dot com @ 2014-03-31  7:10 UTC (permalink / raw)
  To: glibc-bugs

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 11202 bytes --]

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

Marko Myllynen <myllynen at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |myllynen at redhat dot com

--- Comment #1 from Marko Myllynen <myllynen at redhat dot com> ---
(In reply to Michał Górny from comment #0)
> Currently, glibc lists the following for pl_PL locale:
> 
> - no thousands separator in LC_NUMERIC section,
> 
> - '.' as thousands separator in LC_MONETARY section.
> 
> While actually, a non-breaking space is used as thousands separator in both
> cases. However, I'm not sure if it is correct to use <U00A0> in locales or
> if <U0020> should be used instead.

<00A0> should be used in this case, as do many other locales as well.

> It should be also noted that the grouping is used only for numbers having
> more than 4 digits, i.e. '4000' does not use grouping, '40 000' and '4 000
> 000' do on 3-digit groups. I don't know if it is possible to express this in
> current glibc localedata format.

Perhaps you want to see whether that's doable, please see the Locales wiki page
which has a link to a page describing LC_NUMERIC and grouping in detail. The
page contains also information on how to test and submit your locale changes.

Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-22037-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Mar 31 10:45:25 2014
Return-Path: <glibc-bugs-return-22037-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 19940 invoked by alias); 31 Mar 2014 10:45:24 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Delivered-To: mailing list glibc-bugs@sourceware.org
Received: (qmail 19860 invoked by uid 55); 31 Mar 2014 10:45:18 -0000
From: "keld at keldix dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/16777] Incorrect thousands separator in pl_PL locale
Date: Mon, 31 Mar 2014 10:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: localedata
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: keld at keldix dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-16777-131-aEIsTHZAUa@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16777-131@http.sourceware.org/bugzilla/>
References: <bug-16777-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-03/txt/msg00228.txt.bz2
Content-length: 2626

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

--- Comment #2 from keld at keldix dot com <keld at keldix dot com> ---
On Mon, Mar 31, 2014 at 07:10:18AM +0000, myllynen at redhat dot com wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=16777
> 
> Marko Myllynen <myllynen at redhat dot com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |myllynen at redhat dot com
> 
> --- Comment #1 from Marko Myllynen <myllynen at redhat dot com> ---
> (In reply to Micha?? Górny from comment #0)
> > Currently, glibc lists the following for pl_PL locale:
> > 
> > - no thousands separator in LC_NUMERIC section,
> > 
> > - '.' as thousands separator in LC_MONETARY section.
> > 
> > While actually, a non-breaking space is used as thousands separator in both
> > cases. However, I'm not sure if it is correct to use <U00A0> in locales or
> > if <U0020> should be used instead.
> 
> <00A0> should be used in this case, as do many other locales as well.
> 
> > It should be also noted that the grouping is used only for numbers having
> > more than 4 digits, i.e. '4000' does not use grouping, '40 000' and '4 000
> > 000' do on 3-digit groups. I don't know if it is possible to express this in
> > current glibc localedata format.
> 
> Perhaps you want to see whether that's doable, please see the Locales wiki page
> which has a link to a page describing LC_NUMERIC and grouping in detail. The
> page contains also information on how to test and submit your locale changes.

I do not think the "under 10000" is doable with current glibc functionality.

furthermore I think this is not desirable, for LC_MONETARY.

The no break space versus the COMMA/PERIOD thousands separator issue
is a classical problem between linguistic and computer use.
Linguists tends in many languages, European style, to advocate no break space,
but for computer use a period is most often used. I have yet to see a financial
application to use no break space. Bank applications and ledger applications do
not
use no break space.

Actually we shoud probably provide for both styles, and also do the "no
separator
for under 10000.". I would then advise that we use the current functionality
in the POSIX style, and compatible with the POSIX/C locale, and then have new
keywords
both in LC_MONETARY and LC_NUMERIC for the linguistic styles.

Best regards
Keld

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-22038-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Mar 31 12:52:52 2014
Return-Path: <glibc-bugs-return-22038-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 2478 invoked by alias); 31 Mar 2014 12:52:52 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Delivered-To: mailing list glibc-bugs@sourceware.org
Received: (qmail 2435 invoked by uid 55); 31 Mar 2014 12:52:47 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/16648] [microblaze] __ASSUME_ATFCTS incorrect (futimesat)
Date: Mon, 31 Mar 2014 12:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: 2.19
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-16648-131-WnrYIXrM3C@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16648-131@http.sourceware.org/bugzilla/>
References: <bug-16648-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-03/txt/msg00229.txt.bz2
Content-length: 3163

https://sourceware.org/bugzilla/show_bug.cgi?id\x16648

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  d7a68734f7bbc76586017461cff19af0d9cb4df8 (commit)
      from  c760f5c210d85247ef0c6e10f7ef44fa27d9bd1d (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h×a68734f7bbc76586017461cff19af0d9cb4df8

commit d7a68734f7bbc76586017461cff19af0d9cb4df8
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Mon Mar 31 12:51:45 2014 +0000

    Fix futimesat for older MicroBlaze kernels (bug 16648).

    Continuing the fixes for __ASSUME_* issues in preparation for moving
    to a 2.6.32 minimum kernel version, this *untested* patch fixes bug
    16648, the definition of __ASSUME_ATFCTS meaning that the futimesat
    syscall is assumed for all MicroBlaze kernels despite not being
    present until 2.6.33.

    __ASSUME_ATFCTS controls conditionals relating to a lot of different
    syscalls in Linux-specific code (fstatat64 faccessat fchmodat fchownat
    futimesat newfstatat linkat mkdirat openat readlinkat renameat
    symlinkat unlinkat mknodat), where whether newfstatat fstatat64
    futimesat are used depends on the architecture, as well as controlling
    whether openat64_not_cancel_3 is expected to work in
    sysdeps/posix/getcwd.c.  The assumptions are all OK as of 2.6.32
    except for this MicroBlaze case, and it's generally desirable to get
    rid of as many of the __ASSUME_ATFCTS conditionals as possible, to
    simplify the code (the fallbacks include potential unbounded dynamic
    stack allocations).  Thus, rather than the simplest approach of
    undefining __ASSUME_ATFCTS for older kernels on MicroBlaze, this patch
    takes the approach of using the linux-generic implementation of
    futimesat for MicroBlaze kernels before 2.6.33 (all such kernels have
    the utimensat syscall).

        [BZ #16648]
        * sysdeps/unix/sysv/linux/microblaze/kernel-features.h
        [__LINUX_KERNEL_VERSION >= 0x020621] (__ASSUME_FUTIMESAT): Define.
        * sysdeps/unix/sysv/linux/microblaze/futimesat.c: New file.

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog                                          |    7 ++++++
 NEWS                                               |    6 ++--
 .../sysv/linux/microblaze/futimesat.c}             |   21 +++++++++----------
 .../unix/sysv/linux/microblaze/kernel-features.h   |    5 ++++
 4 files changed, 25 insertions(+), 14 deletions(-)
 copy sysdeps/{powerpc/powerpc64/multiarch/strcspn.c =>
unix/sysv/linux/microblaze/futimesat.c} (64%)

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug localedata/16777] Incorrect thousands separator in pl_PL locale
  2014-03-29 18:29 [Bug localedata/16777] New: Incorrect thousands separator in pl_PL locale mgorny at gentoo dot org
  2014-03-31  7:10 ` [Bug localedata/16777] " myllynen at redhat dot com
@ 2014-06-12 19:51 ` fweimer at redhat dot com
  2015-10-11  0:25 ` [Bug localedata/16777] pl_PL: incorrect thousands separator in locale vapier at gentoo dot org
  2 siblings, 0 replies; 4+ messages in thread
From: fweimer at redhat dot com @ 2014-06-12 19:51 UTC (permalink / raw)
  To: glibc-bugs

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

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |security-

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug localedata/16777] pl_PL: incorrect thousands separator in locale
  2014-03-29 18:29 [Bug localedata/16777] New: Incorrect thousands separator in pl_PL locale mgorny at gentoo dot org
  2014-03-31  7:10 ` [Bug localedata/16777] " myllynen at redhat dot com
  2014-06-12 19:51 ` fweimer at redhat dot com
@ 2015-10-11  0:25 ` vapier at gentoo dot org
  2 siblings, 0 replies; 4+ messages in thread
From: vapier at gentoo dot org @ 2015-10-11  0:25 UTC (permalink / raw)
  To: glibc-bugs

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

Mike Frysinger <vapier at gentoo dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Incorrect thousands         |pl_PL: incorrect thousands
                   |separator in pl_PL locale   |separator in locale

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2015-10-11  0:25 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-03-29 18:29 [Bug localedata/16777] New: Incorrect thousands separator in pl_PL locale mgorny at gentoo dot org
2014-03-31  7:10 ` [Bug localedata/16777] " myllynen at redhat dot com
2014-06-12 19:51 ` fweimer at redhat dot com
2015-10-11  0:25 ` [Bug localedata/16777] pl_PL: incorrect thousands separator in locale vapier at gentoo dot org

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).