This is the mail archive of the libc-locales@sourceware.org mailing list for the GNU libc locales 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][BZ 18934] hu_HU: Fix multiple sorting bugs.


Hi,

Thanks a lot for the information about ICU.

I'd like to emphasize again that my patch does not really touch those
bits where glibc and ICU differ (the unspecified cases) (or actually,
for the second of the two pointed out by Luis, I think I made glibc
more consistent with itself - but not touched the basic intent around
tokenization of weird capitalizations etc.). If we care about
harmonizing glibc and ICU in these unspecified cases, this should be
another extremely-low-prio issue, and we'd need to begin with
verifying that the well specified cases indeed work correctly and the
same way in the two.

Instead of discussing possible extremely-low-prio issues around
unspecified cases that my patch doesn't change, could we please focus
on the things that my patch actually does? :)

thanks,
egmont



On Thu, Feb 2, 2017 at 2:27 PM, Carlos O'Donell <carlos@redhat.com> wrote:
> On 02/01/2017 07:04 PM, Egmont Koblinger wrote:
>> Hi Luis, others,
>>
>> TLDR:
>>
>> Nice inversigation from someone not speaking our language, thumbs up :)
>
> I agree. I enjoyed reading both of your detailed discussions.
>
>> (I'm not sure what ICU is and what's its relation to CLDR. Nevermind.)
>
> ICU is "International Components for Unicode"
> http://site.icu-project.org/
>
> ICU provides a very thorough API for Unicode and globalization.
>
> CLDR is "Unicode Common Locale Data Repository"
>
> CLDR provides the data that is used by ICU implementations.
>
> So in any given program you would link against the ICU library and
> the manipulations you make are driven by the data from CLDR.
>
> The goal with glibc locale data is to attempt to harmonize with CLDR
> such that applications using ICU APIs and glibc APIs get as close to
> the same results as possible.
>
> It does users a disservice if Java and C are arbitrarily different
> in this regard across the two most commonly used APIs for localization.
>
> --
> Cheers,
> Carlos.


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