This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
CLDR locales support in glibc
- From: Rostislav Devyatov <deviatov at gmail dot com>
- To: libc-help at sourceware dot org
- Date: Wed, 4 May 2016 21:42:21 +0300
- Subject: CLDR locales support in glibc
- Authentication-results: sourceware.org; auth=none
Dear developers,
I have a question about support of locales in glibc.
If I understand correctly (however, I'm in doubt, in particular,
that's why I'm asking my question here, and not in locales mailing
list), "locales" are first "defined" or "created" by Unicode
developers and distributed in a package (?) called CLDR. Then the
support for a given new locale in linux starts when it becomes
supported by glibc.
It also seems to me that for now, CLDR containes more locales than
glibc supports. In other words, here
http://unicode.org/Public/cldr/29/ in core.zip , in the common/main/
directory of the archive, there are more files than here
http://ftp.gnu.org/gnu/glibc/ in glibc-2.23.tar.gz , in the
localedata/locales/ directory of the archive. And my question is,
whether support for (some of) the remaining CLDR locales by glibc can
be expected?
I'm particularly interested in the locale called en_150, which is
announced here http://cldr.unicode.org/index/downloads/cldr-22 . If I
understand correctly, this locale indicates that the language is
English and the date/paper/temperature standards are the ones used in
continental Europe.
Is this mailing list good for this question? Or should I ask in
libc-locales mailing list? Or is my understanding of how locales are
created and supported completely wrong?
Best regards,
Rostislav Devyatov