Re: Why does dired go through extra efforts to avoid unibyte names

[Stefan Monnier <monnier@iro.umontreal.ca>]

> Eight-bit-* characters are not in general modified by encoding them,
> so you could encode them any number of times and still get the same
> bytes as result.

Agreed.  But even if it were not the case, I don't see why that would
explain the presence of this code.

>> > As for the reason for using string-to-multibyte: maybe it's because we
>> > use concat further down in the function, which will determine whether
>> > the result will be unibyte or multibyte according to its own ideas of
>> > what's TRT?
>> But `concat` will do a string-to-multibyte for us, if needed
> Not if the other concatenated parts are ASCII (which tend to be
> unibyte strings).

But that's still perfectly fine as well since it will then result in
a unibyte string which will get "encoded" correctly.


        Stefan