[PATCH 3/5] localedata: CLDRv28: update LC_ADDRESS.country_name translations

[Florian Weimer]

* 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
>> data.

> How does ISO resell these data, and where?

A while back, you wrote this:

From: keld@keldix.com
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)
Message-ID: <20151027131038.GB23833@www5.open-std.org>

| 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.

<https://sourceware.org/ml/libc-alpha/2015-10/msg00958.html>