From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Linux  
WikiProject icon This article is within the scope of WikiProject Linux, a collaborative effort to improve the coverage of Linux on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
 ???  This article has not yet received a rating on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.

Error in image[edit]

There is an error in the image in the "Sample uuencode" section. The "Binary representation" for the letter "a" shows nine binary digits rather than eight. The first zero should not be there. Ivar Y 16:40, 23 May 2005 (UTC)


This utility is found in the GNU Sharutils package

GNU uuencode 1.0 distribution has been merged into GNU shar utilities 4.1 distribution.

This is not a complete or precise description of uuencode[edit]

This is not a complete or precise description of uuencode, it requires simplification and clarification as well as extending

It misses the explanation of line start character being the pre-coded line length e.g. 'M' for a 45 byte input length

It misses the addition of '=' characters to pad the output if the input is not a multiple of 24 bits, so '\x00\x00' codes to "AAA="

see The Open Group Base Specifications Issue 6

Trivia section may have an error[edit]

The link to COMT in the trivia section is probably incorrect. In this context COMT is not likely to be an enzyme or gene.

Problem solved. There was no reason for that to be in the article anyway, so now it's toast. RossPatterson 23:22, 7 December 2006 (UTC)

The citation for the "begin<SPACE><SPACE>"-Bug is this: There really was a time when some Linux-geeks annoyed Outlook Express users in some newsgroups (like dasr (Sysadmin recovery)) by including a "begin quote from ..". This does not occur with Mime-messages


A note about the added bloat of UUencoded data would be useful. —Preceding unsigned comment added by (talk) 20:35, 9 October 2008 (UTC)

The trivia section states that the bloat is 33%. However, a typical line of UUEcoding begins with an "M" (ASCII code 45, indicating 45 bytes encoded on this line) followed by 60 characters and ending with CR/LF - ie 63 characters to encode 45 data bytes. 63/45 is 1.4, or 40% bloat, not 33%. —Preceding unsigned comment added by (talk) 00:38, 9 December 2010 (UTC)

ASCII characters greater than 95?[edit]

Exaggerated statement "ASCII characters greater than 95 may also be used; however, only the six least-significant bits are relevant." needs citation! —Preceding unsigned comment added by (talk) 07:22, 12 May 2010 (UTC)

Grave accent in trailer[edit]

Implementations of uuencoding that I've seen do not seem to have a grave accent on the next-to-last line, they use a space character (0x20) instead. This is the case in GNU sharutils (see as well as at least an other utility I've run into (libdes, which implements its own uuencode/decode routines). Is this a variant of the format, or is the grave accent currently shown in the article wrong? Mlindstr (talk) 19:57, 9 May 2013 (UTC)

Discrepancy in "XXcoding" section[edit]

The section on relation to other coding methods says that XXcode "uses only alphanumeric characters and the plus and minus symbols", whereas the actual table showing the characters used shows A to Z, a to z, 0 to 9, +, and /. I presume / should be -, but haven't edited it in case it is the text that should have said "plus and stroke (solidus) symbols" (i. e. I don't know which is wrong).G6JPG (talk) 11:55, 13 December 2014 (UTC)

If you read the second paragraph carefully, it says that the table with the slash symbol is for Base 64, not xxencoding. But maybe there is a way to make this more obvious? Vadmium (talk, contribs) 00:16, 14 December 2014 (UTC).