Uuencoding

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Format)
Line 8: Line 8:
 
== Format ==
 
== Format ==
 
The header line usually starts with "<code>begin</code>", followed by a Unix file permission code and a filename. The last line is "<code>end</code>".
 
The header line usually starts with "<code>begin</code>", followed by a Unix file permission code and a filename. The last line is "<code>end</code>".
 
A newer version of the format begins with "<code>begin-base64</code>", and ends with "<code>====</code>".
 
  
 
Each line of data begins with a character indicating the line length. Since lines have a standard length, all lines except the last one begin with "<code>M</code>".
 
Each line of data begins with a character indicating the line length. Since lines have a standard length, all lines except the last one begin with "<code>M</code>".
 +
 +
== Base64 variant ==
 +
 +
Some uuencode utilities support a variant format that uses standard [[Base64]] encoding, with a "<code>begin-base64</code>" header line, and a "<code>====</code>" footer line.
  
 
== Software ==
 
== Software ==

Revision as of 12:49, 20 November 2015

File Format
Name Uuencoding
Ontology
Extension(s) .uue, .uu

Uuencoding is a way to encode binary data as plain text, suitable for inclusion in an e-mail message or Usenet message.

Contents

Format

The header line usually starts with "begin", followed by a Unix file permission code and a filename. The last line is "end".

Each line of data begins with a character indicating the line length. Since lines have a standard length, all lines except the last one begin with "M".

Base64 variant

Some uuencode utilities support a variant format that uses standard Base64 encoding, with a "begin-base64" header line, and a "====" footer line.

Software

See also

Links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox