This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH 4/5] localedata: CLDRv28: update LC_ADDRESS.lang_name translations
- From: Marko Myllynen <myllynen at redhat dot com>
- To: libc-alpha at sourceware dot org
- Date: Fri, 19 Feb 2016 17:03:55 +0200
- Subject: Re: [PATCH 4/5] localedata: CLDRv28: update LC_ADDRESS.lang_name translations
- Authentication-results: sourceware.org; auth=none
- References: <1454998387-26905-1-git-send-email-vapier at gentoo dot org> <1454998387-26905-4-git-send-email-vapier at gentoo dot org> <20160213002824 dot GA19416 at altlinux dot org> <20160213004931 dot GV7732 at vapier dot lan> <56C7206B dot 7040603 at redhat dot com>
- Reply-to: Marko Myllynen <myllynen at redhat dot com>
On 2016-02-19 16:02, Carlos O'Donell wrote:
> On 02/12/2016 07:49 PM, Mike Frysinger wrote:
>> i noted in an earlier message that i need to respin and throw away the
>> comments because they are out of sync. this gets back to a previous
>> conversation we had about using UTF-8 encoding in all the localedata
>> files instead of ASCII. these <Uxxxx> encodings are a pita.
> I think we should just use UTF-8.
> What was the consensus the last time we talked about this?
When was the last time this was discussed? I remember that I sent a
patch to unify the current situation where most localedata is using code
points but few fields here and there are using strings. The patch was
rejected in the hope we would one day move to using human-readable
strings but no discussion followed when that might be.
Perhaps the time is now?