Bug 5599 - bg_BG: missing thousands_sep
Summary: bg_BG: missing thousands_sep
Status: RESOLVED WONTFIX
Alias: None
Product: glibc
Classification: Unclassified
Component: localedata (show other bugs)
Version: 2.4
: P2 normal
Target Milestone: ---
Assignee: GNU C Library Locale Maintainers
URL:
Keywords:
Depends on: 11484
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-11 00:38 UTC by Martin Sebor
Modified: 2017-08-28 16:36 UTC (History)
5 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:
fweimer: security-


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Sebor 2008-01-11 00:38:21 UTC
The LC_NUMERIC section of the glibc Bulgarian locale definition is the only
locale that specifies the empty string for thousands_sep. I don't think that's
correct. I believe the Bulgarian numeric format is in the form ### ### ###,
i.e., thousands_sep should be set to space. I don't have an authoritative
reference to back this up other than the value observed on non-glibc platforms
and a link to the Unicode cldr file for the Bulgarian locale:
http://unicode.org/cldr/data/common/main/bg.xml
Comment 1 Ulrich Drepper 2008-03-09 05:51:17 UTC
Nothing will be changed unless official references are provided.  CLDR of course
doesn't count.
Comment 2 Paolo Carlini 2010-01-08 18:28:00 UTC
I'm not sure to understand this PR: I just went through the
/usr/share/i18n/locales directory of a current Linux installation (glibc
2.10.1), and I can see literally *tens* of locales with thousands_sep an empty
string!! What I'm missing?
Comment 3 Wei-Lun Chao 2013-09-13 06:13:42 UTC
That is
thousands_sep             ""
should be
thousands_sep             "<U00A0>"
?
Comment 4 Roumen Petrov 2013-09-14 09:23:35 UTC
No we (Bulgarian) don't use space as separator !
Comment 5 Joseph Myers 2017-08-28 16:36:17 UTC
Restoring changes lost in system crash and restore from backup.

https://sourceware.org/ml/glibc-bugs/2017-08/msg00368.html