Re: uuencode: multi-byte chars in remote file names

[Bruce Korb]

Digging up an old thread:
  http://lists.gnu.org/archive/html/bug-gnu-utils/2011-07/msg00000.html

Yesterday's release of sharutils "officially" adds a new option
to uuencode:

> uuencode (GNU sharutils) - encode a file into email friendly text
> Usage:  uuencode [ -<flag> | --<name> ]... [<in-file>] <output-name>
> 
>    -m, --base64               convert using base64
>    -e, --encode-file-name     encode the output file name
> [...]

that will create an encoded output file name with an extension:

> $ echo hello | uuencode -e -m goodbye
> begin-base64-encoded 644 Z29vZGJ5ZQ==
> aGVsbG8K
> ====

The hyphen separated words appended to "begin" are, essentially,
decoding options.  uudecode is written to accept them in any order
(i.e. "begin-encoded-base64" is also acceptable).
These two variations of the "begin" line are not, obviously,
in the POSIX specified format for uuencode-ed files.