>        The uuencode(5) manual page says that the encoding of the final
>        zero length line is an ASCI space.  This is incorrect; a single
>        character ` is used.

While this may be true for the NetBSD version of uuencode, it's
definitely not true for all uuencodes.  For instance, the ULTRIX
version _does_ use a space.

(1) If there is a relevant standard (RFC, most likely) that specifies
    the uuencode format, then our uuencode should conform to it, and

(2) the manual page should document _both_ behaviours, noting which is
    more correct.  (obviously, both work...)


It's worth noting that:

(1) the ULTIRIX and the NetBSD uuencode format manual pages currently
    _agree_ that it should be a space, and,

(2) by the manual page, using the formula given for converting values
    to printable characters, using space is correct.  (Note that space
    _is_ defined to be a printable character.)


Looking at the SCCS logs on vangogh, i see that the change was brought
in back in 1985 (!!), and was part of "bug fixes and changes from Rick
Adams."  Sounds like the format was changed, the docs weren't updated,
and the old format is still decoded because some systems still use it.


chris