This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] localedata: CLDRv29: update LC_ADDRESS.lang_name translations
- From: Chris Leonard <cjlhomeaddress at gmail dot com>
- To: Chris Leonard <cjlhomeaddress at gmail dot com>, libc-alpha <libc-alpha at sourceware dot org>
- Date: Mon, 18 Apr 2016 13:48:40 -0400
- Subject: Re: [PATCH] localedata: CLDRv29: update LC_ADDRESS.lang_name translations
- Authentication-results: sourceware.org; auth=none
- References: <1460957575-4675-1-git-send-email-vapier at gentoo dot org> <CAHdAatY-_P+PTXZb2-ma1oAaPtc5+Nkon37Mov51g2OB56FDvQ at mail dot gmail dot com> <20160418144432 dot GJ5369 at vapier dot lan> <CAHdAatYy2-CiXHXAubY6vkP6+TNd6BDyXu2ZNrHH1ZxQPwr_tg at mail dot gmail dot com> <20160418165100 dot GS5369 at vapier dot lan>
On Mon, Apr 18, 2016 at 12:51 PM, Mike Frysinger <firstname.lastname@example.org> wrote:
> On 18 Apr 2016 12:27, Chris Leonard wrote:
>> On Mon, Apr 18, 2016 at 10:44 AM, Mike Frysinger wrote:
>> > On 18 Apr 2016 03:11, Chris Leonard wrote:
>> >> On Mon, Apr 18, 2016 at 1:32 AM, Mike Frysinger wrote:
>> >> > This updates a bunch of locales based on CLDR v29 data:
>> >> > id_ID: changing Bahasa Ind/onesia to Indonesia
>> >> This individual change just does not look right to me. "Bahasa" is
>> >> the Indonesian word for language. I have been working quite a bit
>> >> with an Indonesian localizer recently, so I can double check if
>> >> needed, but the "Bahasa Indonesia" entry in the "Bahasa Indonesia"
>> >> wikipedia would strongly suggest that "Indonesia" is insufficient to
>> >> describe the language of that country.
>> > CLDR says otherwise:
>> > id.xml: <territory type="ID">Indonesia</territory>
>> > file a ticket if you think it should include Bahasa ?
>> > http://unicode.org/cldr/trac/newticket
>> You cited territory type tag, not language name tag.
> so i did. same answer though for language tag ;).
> id.xml: <language type="id">Indonesia</language>
I honestly wasn't trying to win a nit-pick point, but I hadn't
downloaded CLDRv29 yet, just did.
I accept the overall goal of harmonization with CLDR and leveraging
them as an upstream to the greatest extent possible, but I have a
problem with not only knowingly propagating an error, but in taking
affirmative action to break something that is currently correct. I do
not know if a sin of commission is worse than a sin of omission, but
it seems to transcend laziness to achieve offensiveness.
By what right or mandate are we going to override the correct
representation of cultural information in the Gnu/Linux project
dedicated to allowing proper representation of cultural information?
I like the idea of leveraging CLDR, but following arbitrary
self-adopted rules is no excuse for not using one's mind or
disrespecting someone else's culture (especially in this context). I
believe we are failing in our responsibilities as stewards of this
information if we knowingly make it incorrect and then say, tough
shit, file a bug elsewhere, not our problem.
That is not to say that good stewardship does not also include trying
to improve our processes and seeking to share errors we discover with
the relevant upstream or downstream efforts, I am all for that and
will personally assist with such information gardening in any way I
can. I do think we owe it to our users to not knowingly break stuff,
like the name of their own language or country just because it is