[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ls is broken, what's next cd?
From: |
Pádraig Brady |
Subject: |
Re: ls is broken, what's next cd? |
Date: |
Sat, 17 Feb 2018 13:27:43 -0800 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
On 16/02/18 02:49, Harald Dunkel wrote:
> Hi Ben,
>
> On 02/15/18 08:16, Bernhard Voelker wrote:
>>
>> I'm not sure what's happening there, but it seems that your terminal
>> doesn't know how to display the 2-byte representation "c3 a4"; neither
>> gnome-terminal nor xterm have problems to display it here:
>>
>> $ /bin/ls -log /tmp/Q*
>> -rw-r--r-- 1 0 Feb 15 07:59 '/tmp/Qualitätssicherung final'
>>
>
> I am using xterm. The /tmp file system uses iso8859-? in this case.
> The env says
>
> LANG=C
> LC_ALL=C
>
> Doesn't this mean, that German Umlaute should be escaped, since
> they are outside of scope of the C locale? Regardless whether
> the file system uses iso8859 or UTF8?
Yes that's one of the advantages of the new quoting.
In the presence of mixed encodings (between ls, file system, terminal),
one can always get a safe and usable file name by setting the C locale:
$ ls
Qualitätssicherung
$ LC_ALL=C ls
'Qualit'$'\303\244''tssicherung'
- Re: ls is broken, what's next cd?, (continued)
- Re: ls is broken, what's next cd?, Bernhard Voelker, 2018/02/07
- Re: ls is broken, what's next cd?, Kamil Dudka, 2018/02/06
- Re: ls is broken, what's next cd?, Eric Blake, 2018/02/06
- Re: ls is broken, what's next cd?, Kamil Dudka, 2018/02/06
- Re: ls is broken, what's next cd?, Bernhard Voelker, 2018/02/06
- Re: ls is broken, what's next cd?, Harald Dunkel, 2018/02/07
- Re: ls is broken, what's next cd?, Bernhard Voelker, 2018/02/07
- Re: ls is broken, what's next cd?, Harald Dunkel, 2018/02/13
- Re: ls is broken, what's next cd?, Bernhard Voelker, 2018/02/15
- Re: ls is broken, what's next cd?, Harald Dunkel, 2018/02/16
- Re: ls is broken, what's next cd?,
Pádraig Brady <=