Re: uuencode: multi-bytes char in remote file name contains bytes >0x80

[Eli Zaretskii]

> From: Bruno Haible <address@hidden>
> Date: Mon, 4 Jul 2011 22:58:43 +0200
> Cc: address@hidden,
>  address@hidden,
>  address@hidden,
>  address@hidden
> 
> > Doesn't the same problem exist with the file's data itself?
> 
> No, there is normally no problem with the contents of the files, because users
> have learned to use file formats that are independent of locale.

Text files are always in some encoding, so I doubt that this was
really true.

> But when uudecode has created files with garbled names on the receiver's disk,
> there is no program which will magically fix it.

Obviously, Emacs can.

> > IMO, it's not uuencode's problem to solve.  The correspondents need to
> > solve it "by some other means" (TM), for file data as for its name.
> 
> No, communication that matches users' reasonable expectations does not
> work like this.

What, email is no longer an option?