This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH 1/3] localedata: use same comment_char/escape_char in these files
- From: Chris Leonard <cjlhomeaddress at gmail dot com>
- To: Chris Leonard <cjlhomeaddress at gmail dot com>, Marko Myllynen <myllynen at redhat dot com>, libc-alpha <libc-alpha at sourceware dot org>, "Carlos O'Donell" <carlos at redhat dot com>, Florian Weimer <fweimer at redhat dot com>
- Date: Mon, 11 Apr 2016 16:45:29 -0400
- Subject: Re: [PATCH 1/3] localedata: use same comment_char/escape_char in these files
- Authentication-results: sourceware.org; auth=none
- References: <1455954855-26431-1-git-send-email-vapier at gentoo dot org> <20160225201222 dot GK19841 at vapier dot lan> <20160309222439 dot GZ6588 at vapier dot lan> <56E29E8F dot 50209 at redhat dot com> <CAHdAatZoQ-G0Y-m1O0+vjysCT++Nek_kKdfMc5FQoH3MPZL9PA at mail dot gmail dot com> <56E40938 dot 3010708 at redhat dot com> <CAHdAataOaNnE1Sst9F3e-nFjtPxyNUUATx-+DsQUgQFzBye2EA at mail dot gmail dot com> <CAHdAata8SwOO4a1QFdG3m1L6238j3eX8zscYqkPtVW6dWiLz=A at mail dot gmail dot com> <20160411185850 dot GL6588 at vapier dot lan>
On Mon, Apr 11, 2016 at 2:58 PM, Mike Frysinger <email@example.com> wrote:
> seeing as you can represent the concerns of these communities better
> than probably any of us, it would be great if you could look into the
> cldr process. from my glances around there, it doesn't look *too*
> hard to break in and start posting contributions, especially when you
> have no one else representing those languages.
One of the joys of working with the Sugar Labs / OLPC community is
that we find ourselves on the bleeding edge of new language-in-Linux
introduction. The substantial OLPC deployments in Peru have driven
indigenous language work (Aymara, Quechua, Awajun, and others to
come). The same can be said of our work with deployments in Mexico
and their languages as well as some others.
I am generally sympathetic with the notion of trying to drive both
glibc and CLDR locale development forward together. and I have long
wanted to leverage the excellent work of the "100 locales for Africa"
project (in CLDR) into glibc locales as well. The CLDR
information/translation requirements are somewhat greater, including
as it does portions of the Debian iso-code project strings (languages,
countries, scripts, etc.). However it is easy enough to simply
locally host versions of those PO files from the Translation Project
on the Sugar Labs Pootle instance to allow their accumulation to
critical mass for CLDR development in the same manner that I had
created a "glibc-helper.pot" file to collect the core translations of
a glibc locale.
If I can get Pootle language setup information (plural numbers, plural
equation) for the languages that exist in glibc, but not CLDR, I'll
host some CLDR-relevant PO files and start looking to recruit
interested localizers, but it must be understood that it is not
particularly easy to find localizers for these languages, they have a
very small footprint on the Internet.
I'll look into it some more and report back to the list.