Bug#522776: Subject: Re: Bug#522776: debian-policy: mandate existence of a standardised UTF-8 locale
Albert Cahalan dixit:
>Giacomo A. Catenazzi writes:
>> I think nobody should use "C" or "C.UTF-8" as user encoding.
I’d use it.
>Debian doesn't ship a proper locale. I want sorting according
>to the raw Unicode values.
Also called ASCIIbetically ☺ But C exists, C.UTF-8 doesn’t.
>>> * All ISO8859 locales are moved to a new locales-legacy-encodings
>>> package.
>>
>> This encoding is used also on CD/, floppy, remote filesystems,
>> USB pens, on a lot of internet pages, etc.
>
>Nope.
>
>It's actually UTF-16 in VFAT, Joliet, CIFS, and so on.
And cp437 (or, worse, cp850) in FAT SFNs.
>> So scripts should use LANG=C on most cases.
>
>That leaves iswprint() and towupper() broken. (not that it must)
No, LANG is *also* wrong. Scripts relying on certain behaviour
use LC_ALL=C (and, on GNU OSes, also must “unset LANGUAGE”), but
some things just require UTF-8, so the current approach is to
unset everything beginning with LC_*, setting LANG=C (or unsetting
it) and LC_ALL=en_US.UTF-8 or en_GB.UTF-8 or whatever and hoping
that that locale is installed… not acceptable!
bye,
//mirabilos
--
16:47⎜«mika:#grml» .oO(mira ist einfach gut....) 23:22⎜«mikap:#grml»
mirabilos: und dein bootloader ist geil :) 23:29⎜«mikap:#grml» und ich
finds saugeil dass ich ein bsd zum booten mit grml hab, das muss ich dann
gleich mal auf usb-stick installieren -- Michael Prokop über MirOS bsd4grml
Reply to: