This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


On 02/09/2016 03:00 AM, Mike Frysinger wrote:
> On 09 Feb 2016 09:25, Marko Myllynen wrote:
>> On 2016-02-09 09:20, Mike Frysinger wrote:
>>> i need to respin this patch due to some of the comments falling out of
>>> date.  should i send another patch to just delete these things ?  e.g.
>>> files inconstantly do things like:
>>> % wa
>>> lang_ab      "<U0077><U0061>"
>>>
>>> i think we should just scrub these and rely on a simple filter script
>>> to view the content.
>>
>> This series is a great initiative, thanks for doing this! I wonder how
>> have you generated the patches, would it be possible to script any of
>> this so that in case CLDR changes in the future we could automatically
>> update glibc locales accordingly then?
> 
> yes, i've written a python file that downloads the CLDR db, loads the
> locale files, and then merges them and checks for differences.  i'm in
> the process of trying to extract as much as possible from the CLDR db.
> you can find my in-progress work attached, but i'm not posting it for
> review yet ;).
> 
> i just run it like:
> $ ./cldr.py locales/*

So basically I think that reviewing your patches is only mildy useful
busy work. What's *really* cool is getting your scripts to a point where
they can be used like the Unicode scripts are used, a single directory
and a Makefile that can be run to update the files in question. I think
we're going to have to checkin the CLDR db data to ensure we can reproduce
the results?

Cheers,
Carlos.
 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]