[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1020654: C.UTF-8: surprising differences in character classes



Hi Aurelien,

>Starting with glibc 2.35, we do not patch the glibc to add C.UTF-8
>support, instead we use the upstream code which comes with the following
>NEWS entry [1]:
[…]

Thanks for the extra info.

>> They are as mandated by POSIX for the C locale. I believe I said
>> in my original 2013 proposal for a C.UTF-8 locale that it should
>> be as close to C as possible while using UTF-8 as encoding.
>
>Those are mandated for the POSIX C locale, but POSIX does not say
>anything (yet) about the C.UTF-8 locale.

Right. But, as I wrote above, my intent was to have C.UTF-8 to mirror
C as closely as possible.

>The choice made by upstream has been discussed during many years [2],
>if you disagree with it, please come back to upstream.

*sigh* but I understand your PoV.

bye,
//mirabilos
-- 
22:20⎜<asarch> The crazy that persists in his craziness becomes a master
22:21⎜<asarch> And the distance between the craziness and geniality is
only measured by the success 18:35⎜<asarch> "Psychotics are consistently
inconsistent. The essence of sanity is to be inconsistently inconsistent


Reply to: