1uuencode(1)                      User Commands                     uuencode(1)
2
3
4

NAME

6       uuencode - encode a file into email friendly text
7

SYNOPSIS

9       uuencode  [-flag  [value]]...  [--opt-name[[=|  ]value]]... [ in-file ]
10       output-name
11

DESCRIPTION

13       uuencode is used to create an ASCII representation of a file  that  can
14       be  sent  over  channels that may otherwise corrupt the data.  Specifi‐
15       cally, email cannot handle binary data and will  often  even  insert  a
16       character  when  the  six character sequence "0rom " is seen.  uuencode
17       will read in-file if provided and otherwise read data from standard  in
18       and write the encoded form to standard out.  The output will begin with
19       a header line for use by uudecode giving  it  the  resulting  suggested
20       file  output-name  and access mode.  If the output-name is specifically
21       /dev/stdout, then uudecode will emit the decoded file to standard  out.
22       Note:  uuencode  uses  buffered  input  and assumes that it is not hand
23       typed from a tty.  The consequence is that at a tty, you  may  need  to
24       hit Ctl-D several times to terminate input.
25

OPTIONS

27       -m, --base64
28              convert using base 64.
29
30              By  default,  uuencode will encode using the traditional conver‐
31              sion.  It is slower and less compact than base 64.  The  encoded
32              form  of  the file is expanded by 37% for UU encoding and by 35%
33              for base64 encoding (3 bytes become 4 plus control information).
34
35       -e, --encode-file-name
36              encode the output file name.
37
38              Since output file names may contain characters that are not han‐
39              dled  well  by  various transmission modes, you may specify that
40              the output-name be hex encoded as well.
41
42       -h, --help
43              Display usage information and exit.
44
45       -!, --more-help
46              Pass the extended usage information through a pager.
47
48       -R [rcfile], --save-opts[=rcfile]
49              Save the option state to rcfile.  The default is the  last  con‐
50              figuration file listed in the OPTION PRESETS section, below.
51
52       -r rcfile, --load-opts=rcfile, --no-load-opts
53              Load  options  from  rcfile.  The no-load-opts form will disable
54              the loading of earlier RC/INI files.  --no-load-opts is  handled
55              early, out of order.
56
57       -v [{v|c|n}], --version[={v|c|n}]
58              Output  version of program and exit.  The default mode is `v', a
59              simple version.  The `c' mode will print  copyright  information
60              and `n' will print the full copyright notice.
61

OPTION PRESETS

63       Any option that is not marked as not presettable may be preset by load‐
64       ing values from configuration  ("RC"  or  ".INI")  file(s).   The  file
65       "$HOME/.sharrc" will be used, if present.
66

STANDARDS

68       This implementation is compliant with P1003.2b/D11.
69

FILES

71       See OPTION PRESETS for configuration files.
72

EXIT STATUS

74       One of the following exit values will be returned:
75
76       0 (EXIT_SUCCESS)
77              Successful program execution.
78
79       1 (EXIT_FAILURE)
80              The operation failed or the command syntax was not valid.
81
82       66 (EX_NOINPUT)
83              A specified configuration file could not be loaded.
84
85       70 (EX_SOFTWARE)
86              libopts  had an internal operational error.  Please report it to
87              autogen-users@lists.sourceforge.net.  Thank you.
88

SEE ALSO

90       uudecode(1)
91

HISTORY

93       The uuencode command first appeared in BSD 4.0.
94

AUTHORS

96       Free Software Foundation, Inc.
97
99       Copyright (C) 1994-2013  Free  Software  Foundation,  Inc.  all  rights
100       reserved.   This program is released under the terms of the GNU General
101       Public License, version 3 or later.
102

BUGS

104       Please put sharutils in the subject line for emailed bug  reports.   It
105       helps to spot the message.
106
107       The output file name must not begin with the 11 character sequence:
108           hex-encode:
109       unless you specify the -h (encode-file-name) option.
110
111       Please send bug reports to: bug-gnu-utils@gnu.org
112

NOTES

114       This  manual  page  was AutoGen-erated from the uuencode option defini‐
115       tions.
116
117
118
119GNU sharutils (4.13.3)            06 Jan 2013                      uuencode(1)
Impressum