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

[Eli Zaretskii]

> Date: Tue, 05 Jul 2011 14:12:01 -0700
> From: Bruce Korb <address@hidden>
> CC: 張叁 <address@hidden>, 
>  Bruno Haible <address@hidden>,
>  Eli Zaretskii <address@hidden>, address@hidden, address@hidden, 
>  "\"Eric\" toe lin" <address@hidden>
> 
> Meanwhile, I'm still waiting for a good answer to, "Why do it at all?"

Because not doing that would severely limit uuencode's domain of
applicability?  Why would users be coerced to use pax when all they
need is send a single file?  Sounds like a gratuitous limitation to
me.