Re: [patch] ko_KR locale

[Jungshik Shin <jshin at mailaps dot org>]

Jungshik Shin wrote:

Hi,

I sent the following message around Christmas. I'm wondering if you've 
had a chance to take a look 
(http://sources.redhat.com/ml/libc-alpha/2003-12/msg00205.html).

> Ulrich Drepper wrote:
>
>
> > Jungshik Shin wrote:
>
>
> > > localedef didn't complain, but the collation result was all messed up
> > > with the locale generated from it. So, I gave up using '..' to
> > > represent the range and  listed all characters in the patch.
>
>
> > That's no good solution.  The locale description gets unmaintainable
> > in
> > this form.  localedef should handle the case correctly.  Provide a
> > test
> > case and we can look into fixing it.
>
>
>   Yes, I agree that we have to fix the root cause instead of working
> around. Attached is a bzip2'd tar file with the following files:
>
>   1. ko_KR.v2  : the locale definition file with the range notation
>   2. ko_KR.test:  11,172 Hangul syllables and 8,999 Chinese characters
>                  with Korean reading specified in Unihan-3.2.0.txt
>                  are listed.
>
> With the locale generated by the definition file I sent you earlier,
> 'sort sorted' reproduced 'sorted' file. However, with the locale
> generated from ko_KR.v2 (I'm attaching here), 'sort sorted' generates
> a totally different output.

In the above paragraph, 'sort sorted' should be 'sort ko_KR.test'. The 
file 'ko_KR.test' is already sorted. However, with the locale generated 
from a locale source with the range notation, 'sort ko_KR.test' does not 
reproduces the original while under the locale generated from a locale 
source without the range notation, 'sort ko_KR.test' reproduces the 
original file.

Jungshik