This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] localedata: add more translit entries
- From: Chris Leonard <cjlhomeaddress at gmail dot com>
- To: Marko Myllynen <myllynen at redhat dot com>
- Cc: libc-alpha <libc-alpha at sourceware dot org>, Mike Fabian <mfabian at redhat dot com>
- Date: Tue, 26 Apr 2016 08:37:13 -0400
- Subject: Re: [PATCH] localedata: add more translit entries
- Authentication-results: sourceware.org; auth=none
- References: <1461426795-14966-1-git-send-email-raj dot khem at gmail dot com> <1461447298-13571-1-git-send-email-vapier at gentoo dot org> <571E1896 dot 8060309 at redhat dot com> <20160426044059 dot GV5369 at vapier dot lan> <571F0505 dot 1040400 at redhat dot com>
+1
cjl
On Tue, Apr 26, 2016 at 2:04 AM, Marko Myllynen <myllynen@redhat.com> wrote:
> Hi,
>
> On 2016-04-26 07:40, Mike Frysinger wrote:
>> On 25 Apr 2016 16:16, Marko Myllynen wrote:
>>> On 2016-04-24 00:34, Mike Frysinger wrote:
>>>> Some of the newer symbols we're using are missing translit entries which
>>>> causes troubles when generating the locales with older encodings.
>>>>
>>>> tr_TR: â -> "TL"
>>>> uz_UZ: Ê -> "'"
>>>> common:
>>>> Ö -> "AMD"
>>>> â -> "ILS"
>>>> â -> "PHP"
>>>> â -> "KZT"
>>>> â -> "GEL"
>>>
>>> The new common parts look good but I wonder when should we include
>>> translit_neutral in locale files and when to add individual rules into
>>> them instead (which are already defined in translit_neutral)?
>>
>> the vast majority of locales leverage translit_neutral (by way of copying
>> i18n). the exceptions are:
>> az_AZ
>> crh_UA
>> km_KH
>> ku_TR
>> tr_CY
>> tr_TR
>> tt_RU@iqtelif
>>
>> all except km_KH eventually copy tr_TR. seems like it should be possible
>> to rebase these two on top of translit_neutral (or at least i18n), but i
>> have no idea why they didn't in the first place. considering how hacky
>> km_KH has been (looks like it was copied from lo_LA and then hacked to
>> bits to get a little km_KH), i wouldn't be surprised if it wasn't meant
>> to be by itself.
>
> Ok, thanks for checking, I think this can be investigated later in more
> detail and now your patch is the right thing to do.
>
> Cheers,
>
> --
> Marko Myllynen