Jarkko Hietaniemi <[EMAIL PROTECTED]> writes:
>>Let's not 'fix' it (not carve it on a stone), but offer a few
>> well-thought-out options. For instance, Perl may offer (not that these
>> are particularly well-thought-out) 'just treat this as a sequence of
>> octets', 'locale', and 'unicode'. 'l
Jungshik Shin <[EMAIL PROTECTED]> writes:
>
> Then, he should switch to en_GB.UTF-8.
I probably will.
>Besides, he implied that
>he still uses ISO-8859-1 for files whose names can be covered by
>ISO-8859-1, which is why I wrote about mixing up two encodings
>in a single file system _under_ his
Jarkko Hietaniemi <[EMAIL PROTECTED]> writes:
>>> What I wish is that the whole current locale system would curl up and
>>> die.
>>
>> As you'd agree, it's only 'encoding' part that has to die.
>
>Oh no, there are plenty of parts in it that I wish would die :-)
>(though the coupling of encoding i
Jungshik Shin <[EMAIL PROTECTED]> writes:
>> That will work if there's en_GB.UTF-8 available for him in his
>> particular Unixes and assuming using UTF-8 locales won't break other
>> things.
Just so we get this clear. A year or so back I - as a Unicode advocate - tried
to switch to en_GB.utf8. Wi
On Sun, 28 Dec 2003, Nick Ing-Simmons wrote:
> Jungshik Shin <[EMAIL PROTECTED]> writes:
> >
> > Then, he should switch to en_GB.UTF-8.
>
> I probably will.
Good !
> >Besides, he implied that
> >he still uses ISO-8859-1 for files whose names can be covered by
> >ISO-8859-1, which is why I wro
