{"id":4728,"date":"2022-12-20T18:36:49","date_gmt":"2022-12-20T21:36:49","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/uuencode-man5\/"},"modified":"2022-12-20T18:36:49","modified_gmt":"2022-12-20T21:36:49","slug":"uuencode-man5","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/uuencode-man5\/","title":{"rendered":"UUENCODE (man5)"},"content":{"rendered":"<h1 align=\"center\">UUENCODE<\/h1>\n<p> <a href=\"#NAME\">NAME<\/a><br \/> <a href=\"#DESCRIPTION\">DESCRIPTION<\/a><br \/> <a href=\"#EXAMPLES\">EXAMPLES<\/a><br \/> <a href=\"#CONFORMING TO\">CONFORMING TO<\/a><br \/> <a href=\"#SEE ALSO\">SEE ALSO<\/a><br \/> <a href=\"#HISTORY\">HISTORY<\/a> <\/p>\n<hr>\n<h2>NAME <a name=\"NAME\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">uuencode \u2212 format of an encoded uuencode file<\/p>\n<h2>DESCRIPTION <a name=\"DESCRIPTION\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">Files output by uuencode(1) consist of a header line, followed by a number of body lines, and a trailer line. The uudecode(1) command will ignore any lines preceding the header or following the trailer. Lines preceding a header must not, of course, look like a header.<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\">The header line is distinguished by having the first 5 characters be <i>begin<\/i> followed by a space, or else a hyphen and either <i>base64<\/i> or <i>encoded<\/i> or both (also separated with a hyphen). The <i>base64<\/i> option says the file has been encoded using base64. The <i>encoded<\/i> option says the output file <i>name<\/i> has been base64 encoded. It is never encoded with traditional uuencoding. This is a GNU extension. These are followed by a mode (in octal), and a string which names the remote file. The mode is separated from the <i>begin<\/i> clause and the file name by a single space character.<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>Traditional uuencoding<\/b> <br \/> The traditional <i>uuencoded<\/i> file body consists of a number of lines, each at most 62 characters long (including the trailing newline). These consist of a character count letter, followed by the encoded characters, followed by a newline. The character count is a single printing character, and represents an integer, the number of bytes the rest of the line represents. Such integers are always in the range from 0 to 63 and can be determined by subtracting the character space (octal 40) from the character.<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\">Groups of 3 bytes are stored in 4 characters, 6 bits per character. All are offset by a space to make the characters printing. The last line may be shorter than the normal 45 bytes. If the size is not a multiple of 3, this fact can be determined by the value of the count on the last line. Extra garbage will be included to make the character count a multiple of 4. The body is terminated by a line with a count of zero. This line consists of one ASCII space.<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\">The trailer line consists of <i>end<\/i> on a line by itself.<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>base64 encoding<\/b> <i><br \/> base64<\/i> encoded files follow the specified format for the body, but also include a <i>begin-base64<\/i> header and a trailer line of four <i>=<\/i> characters.<\/p>\n<h2>EXAMPLES <a name=\"EXAMPLES\"><\/a> <\/h2>\n<p style=\"margin-left:18%; margin-top: 1em\">begin-base64-encoded 644 VE9ETw==<\/p>\n<p style=\"margin-left:11%;\">This introduces a base64 encoded file named, <i>TODO<\/i> with that name encoded using base64 encoding.<\/p>\n<p style=\"margin-left:18%; margin-top: 1em\">begin-encoded 644 5$]$3P\u2018\u2018<\/p>\n<p style=\"margin-left:11%;\">This introduces an encoded file named, <i>TODO<\/i> with that name encoded using uuencoding. The encoding is a lot less friendly. Please prefer base64 encoding.<\/p>\n<h2>CONFORMING TO <a name=\"CONFORMING TO\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">IEEE Std 1003.1, plus extensions<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\">The <i>\u2212encoded<\/i> suffix to the <i>begin<\/i> header line is a GNU extension. Recipients must have the GNU <i>uudecode<\/i> program to decode them.<\/p>\n<h2>SEE ALSO <a name=\"SEE ALSO\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">uuencode(1), uudecode(1), base64(1GNU)<\/p>\n<h2>HISTORY <a name=\"HISTORY\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">The <i>uuencode<\/i> file format appeared in BSD 4.0 .<\/p>\n<hr>\n","protected":false},"excerpt":{"rendered":"<p>  uuencode \u2212 format of an encoded uuencode file <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[959],"tags":[961,1291,1649],"class_list":["post-4728","post","type-post","status-publish","format-standard","hentry","category-5-formatos-de-ficheros","tag-961","tag-man5","tag-uuencode"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4728","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=4728"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4728\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=4728"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=4728"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=4728"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}