Re: Multibyte and unibyte file names

[Paul Eggert <eggert@cs.ucla.edu>]

>> >  > what you suggest is a large project that won't
>> >  > happen without a motivated individual.  Given the overall "cannot
>> >  > happen on POSIX, so it's SEP"
>> > 
>> > It can easily happen on POSIX systems, especially with removable media
>> > or double-booting hosts.
> If you look back at this thread, you will see that this is what I
> tried to say, but was consistently told that Posix systems have no
> such problems "in practice".

I don't think Stephen and I were talking about the same thing.
Stephen's reference to mojibake was talking about having various
files scattered around the system, with file names using different
encodings, and that can easily happen on POSIX systems.  But as I
understand it, we're not trying to solve that problem -- Emacs
will see mojibake in that situation, and users will just have to
deal with it.

Regardless of whether the mojibake problem is present,
Emacs is OK on a POSIX system without worrying about
this issue, since file names are safe even if they're
encoded in Shift-JIS or Big5.  Moreover, a file name is
safe even if it has some parts encoded in Shift-JIS
and other parts encoded in Big5, so that it looks like
gibberish on the screen.  That is because none of these
encoding usurp '/' or '.'.