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

[Bruce Korb]

On 07/05/11 13:13, Eric Blake wrote:
> On 07/05/2011 12:12 PM, Bruce Korb wrote:
> > On 07/05/11 10:13, Eric Blake wrote:
> > > begin 444 hex-encode-EN:6865782d656e636f64652d44453a42414446
> > >
> > > that is, presence of : in the desired output name implies that the file
> > > name must be encoded, just the same as any 8-bit byte also makes that
> > > implication.
> >
> > Yep, but part of the whole point of uuencode is that the output is 7-bit
> > ASCII,
>
> "hex-encode-EN:6865782d656e636f64652d44453a42414446" _is_ 7-bit ASCII

I think we are in vehement agreement (agreeing, but not quite understanding
what each other has meant to say).

So, an option could be omitted by doing a strspn() with the set of
POSIX file name characters, but I don't think that is a good idea.
I suspect there are some folks expecting sloppiness in allowing
non-portable characters in the file name.  Therefore, it should be an
explicit request (option) to do it.

Meanwhile, I'm still waiting for a good answer to, "Why do it at all?"
since the file(s) could get rolled into a "pax"ball. :)