This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH 3/5] localedata: CLDRv28: update LC_ADDRESS.country_name translations
- From: Florian Weimer <fw at deneb dot enyo dot de>
- To: Keld Simonsen <keld at keldix dot com>
- Cc: Carlos O'Donell <carlos at redhat dot com>, Roland McGrath <roland at hack dot frob dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, Mike Frysinger <vapier at gentoo dot org>, Marko Myllynen <myllynen at redhat dot com>, libc-alpha at sourceware dot org
- Date: Mon, 22 Feb 2016 12:34:30 +0100
- Subject: Re: [PATCH 3/5] localedata: CLDRv28: update LC_ADDRESS.country_name translations
- Authentication-results: sourceware.org; auth=none
- References: <56BA53A8 dot 2070704 at redhat dot com> <20160209214819 dot GR7732 at vapier dot lan> <56BB8DD6 dot 9020808 at redhat dot com> <20160210201256 dot GA7732 at vapier dot lan> <56BC0DC4 dot 3070404 at redhat dot com> <56BC534B dot 5040306 at redhat dot com> <56BCA2E9 dot 6010407 at redhat dot com> <56BCC81E dot 4070804 at redhat dot com> <56C11AC8 dot 10809 at redhat dot com> <8760xhyp6n dot fsf at mid dot deneb dot enyo dot de> <20160222111834 dot GA28040 at www5 dot open-std dot org>
* Keld Simonsen:
> On Mon, Feb 22, 2016 at 12:12:00PM +0100, Florian Weimer wrote:
>> * Carlos O'Donell:
>> > I suggest we continue the work and I will ask FSF legal to comment
>> > on the issue of needing an attribution for the use of the Unicode
>> > data files. I am still of the opinion that the original statement
>> > from the FSF is enough guidance, to continue the work Mike is doing,
>> > but it doesn't hurt to get clarification.
>> Please also point them out that ISO currently seems to re-sell glibc
>> locale data under a restrictive license. This is probably not what
>> the FSF wanted to enabled when it disclaimed copyright on glibc locale
> How does ISO resell these data, and where?
A while back, you wrote this:
Subject: Re: Should glibc provide a builtin C.UTF-8 locale?
Date: Tue, 27 Oct 2015 14:10:38 +0100 (16 weeks, 5 days, 22 hours ago)
| Yes, ISO TR 30112 i18n and glibc i18n are essentially the same, as
| ISO 30112 builds on a bit old copy of glibc i18n locale.
| In turn the glibc i18n locale was built on ISO TR 14652 i18n
| locale, so this is a fruitful relation. ISO 30112 is the followup
| spec on ISO 14652, and ISO 30112 has catched up with some glibc development.