This is the mail archive of the libc-locales@sourceware.org mailing list for the GNU libc locales project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug localedata/20756] [PATCH] Use Unicode wise thousands separator


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

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2016-11-01
                 CC|                            |carlos at redhat dot com
     Ever confirmed|0                           |1

--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Stanislav Brabec from comment #0)
> Created attachment 9605 [details]
> Proposed changes
> 
> Many languages use small gap as thousands separator.
> 
> Thousands separator should not be a plain space, but a narrow space. And
> additionally, it is not allowed to wrap number in the middle when wrapping
> line.

Agreed.

> Locale data were created in a deep age of 8-bit encodings, so most of them
> use space (incorrect: it allows word wrapping in the middle of the number),
> or NBSP (better, but typographically incorrect: space between group is too
> wide).
> 
> Now unicode is widely supported, so we should leave legacy characters in
> favor of correct UNICODE character.
> 
> UNICODE has a dedicated character for this purpose:
> 
> NNBSP
> U+202F NARROW NO-BREAK SPACE: a narrow form of a no-break space, typically
> the width of a thin space or a mid space

I would support this change.

The NNBSP has been around since Unicode 3.0 so we support it across the board.

Can you please post this to libc-alpha following:
https://sourceware.org/glibc/wiki/Contribution%20checklist

Note that you don't need a copyright assignment for locale data changes as your
patch proposes.

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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]