Subject: misc/17796: uuencode man page algorithm description blatantly wrong
To: None <gnats-bugs@gnats.netbsd.org>
From: None <meinlschmidt@informatik.uni-erlangen.de>
List: netbsd-bugs
Date: 08/01/2002 03:52:07
>Number:         17796
>Category:       misc
>Synopsis:       uuencode man page algorithm description blatantly wrong
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    misc-bug-people
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Aug 01 03:53:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Stefan Meinlschmidt
>Release:        NetBSD 1.6
>Organization:
Universitšt Erlangen
>Environment:
>Description:
In the man-page UUENCODE(5), NetBSD 1.6, April 9, 1997 as obtained via 
http://www.tac.eu.org/cgi-bin/man-cgi?uuencode+5 ,
is stated, that the bits are processed low to high order. This disagrees with the Open Group man-page on this issue as obtained via
http://www.opengroup.org/onlinepubs/007904975/utilities/uuencode.html ,
disagrees with the result from running the uuencode that ships with Linux (sorry) and disagrees with network byte order.

Apologies if this was fixed fife years ago, but there's lots of old stuff creeping up the Google reaults :-(

>How-To-Repeat:

>Fix:
Change ``lowest order bit of the first character'' to ``highest order bit of the first character'' and ``highest order bit of the third character'' to ``lowest order bit of the third character''
>Release-Note:
>Audit-Trail:
>Unformatted: