{
    "mode": "info",
    "parameter": "uuencode",
    "section": "",
    "url": "https://www.chedong.com/phpMan.php/info/uuencode/json",
    "generated": "2026-07-31T21:52:35Z",
    "sections": {
        "File: sharutils.info,  Node: uuencode Invocation,  Next: uudecode Invocation,  Prev: unshar Invocation,  Up: Basic": {
            "content": "",
            "subsections": [
                {
                    "name": "2.3 Invoking uuencode",
                    "content": "`uuencode' is used to create an ASCII representation of a file that can\nbe sent over channels that may otherwise corrupt the data."
                }
            ]
        },
        "Specifically, email cannot handle binary data and will often even": {
            "content": "insert a character when the six character sequence \"\\nFrom \" is seen.\n\n`uuencode' will read `in-file' if provided and otherwise read data\nfrom standard in and write the encoded form to standard out.  The\noutput will begin with a header line for use by `uudecode' giving it\nthe resulting suggested file `output-name' and access mode.  If the\n`output-name' is specifically `/dev/stdout', then `uudecode' will emit\nthe decoded file to standard out.\n\n*Note*: `uuencode' uses buffered input and assumes that it is not\nhand typed from a tty.  The consequence is that at a tty, you may need\nto hit Ctl-D several times to terminate input.\n\nThis section was generated by *AutoGen*, using the `agtexi-cmd'\ntemplate and the option descriptions for the `uuencode' program.  This\nsoftware is released under the GNU General Public License, version 3 or\nlater.\n\n* Menu:\n\n* uuencode usage::                  uuencode help/usage (`--help')\n* uuencode base64::                 base64 option (-m)\n* uuencode encode-file-name::       encode-file-name option (-e)\n* uuencode config::                 presetting/configuring uuencode\n* uuencode exit status::            exit status\n* uuencode Bugs::                   Bugs\n* uuencode Standards::              Standards\n* uuencode History::                History\n* uuencode See Also::               See Also\n",
            "subsections": []
        },
        "File: sharutils.info,  Node: uuencode usage,  Next: uuencode base64,  Up: uuencode Invocation": {
            "content": "This is the automatically generated usage text for uuencode.\n\nThe text printed is the same whether selected with the `help' option\n(`--help') or the `more-help' option (`--more-help').  `more-help' will\nprint the usage text by passing it through a pager program.\n`more-help' is disabled on platforms without a working `fork(2)'\nfunction.  The `PAGER' environment variable is used to select the\nprogram, defaulting to `more'.  Both will exit with a status code of 0.\n\nuuencode (GNU sharutils) - encode a file into email friendly text\nUsage:  uuencode [ -<flag> | --<name> ]... [<in-file>] <output-name>\n\n-m, --base64               convert using base64\n-e, --encode-file-name     encode the output file name\n-v, --version[=MODE]       output version information and exit\n-h, --help                 display extended usage information and exit\n-!, --more-help            extended usage information passed thru pager\n-R, --save-opts[=FILE]     save the option state to a config file FILE\n-r, --load-opts=FILE       load options from the config file FILE\n- disabled with '--no-load-opts'\n- may appear multiple times\n",
            "subsections": []
        },
        "Options are specified by doubled hyphens and their name or by a single": {
            "content": "hyphen and the flag character.\n\nThe following option preset mechanisms are supported:\n- reading file $HOME/.sharrc\n\n'uuencode' is used to create an ASCII representation of a file that can be\nsent over channels that may otherwise corrupt the data.  Specifically,\nemail cannot handle binary data and will often even insert a character when\nthe six character sequence \"\\nFrom \" is seen.\n\n'uuencode' will read 'in-file' if provided and otherwise read data from\nstandard in and write the encoded form to standard out.  The output will\nbegin with a header line for use by 'uudecode' giving it the resulting\nsuggested file 'output-name' and access mode.  If the 'output-name' is\nspecifically '/dev/stdout', then 'uudecode' will emit the decoded file to\nstandard out.\n\n'Note': 'uuencode' uses buffered input and assumes that it is not hand\ntyped from a tty.  The consequence is that at a tty, you may need to hit\nCtl-D several times to terminate input.\n\nPlease send bug reports to:  <bug-gnu-utils@gnu.org>\n",
            "subsections": []
        },
        "File: sharutils.info,  Node: uuencode base64,  Next: uuencode encode-file-name,  Prev: uuencode usage,  Up: uuencode Invocation": {
            "content": "This is the \"convert using base64\" option.  By default, `uuencode' will\nencode using the traditional conversion.  It is slower and less compact\nthan base64.  The encoded form of the file is expanded by 37% for UU\nencoding and by 35% for base64 encoding (3 bytes become 4 plus control\ninformation).\n",
            "subsections": []
        },
        "File: sharutils.info,  Node: uuencode encode-file-name,  Next: uuencode config,  Prev: uuencode base64,  Up: uuencode Invocation": {
            "content": "This is the \"encode the output file name\" option.  Since output file\nnames may contain characters that are not handled well by various\ntransmission modes, you may specify that the `output-name' be base64\nencoded as well.  (Traditional uuencoding of the file name is not\nsupported.)\n",
            "subsections": []
        },
        "File: sharutils.info,  Node: uuencode config,  Next: uuencode exit status,  Prev: uuencode encode-file-name,  Up: uuencode Invocation": {
            "content": "",
            "subsections": []
        },
        "Any option that is not marked as not presettable may be preset by": {
            "content": "loading values from configuration (\"rc\" or \"ini\") files.\n\n`libopts' will search in `$HOME' for configuration (option) data.  The\nenvironment variable `HOME, ' is expanded and replaced when the program\nruns If this is a plain file, it is simply processed.  If it is a\ndirectory, then a file named `.sharrc' is searched for within that\ndirectory.\n\nConfiguration files may be in a wide variety of formats.  The basic\nformat is an option name followed by a value (argument) on the same\nline.  Values may be separated from the option name with a colon, equal\nsign or simply white space.  Values may be continued across multiple\nlines by escaping the newline with a backslash.\n\nMultiple programs may also share the same initialization file.",
            "subsections": []
        },
        "Common options are collected at the top, followed by program specific": {
            "content": "segments.  The segments are separated by lines like:\n[UUENCODE]\nor by\n<?program uuencode>\nDo not mix these styles within one configuration file.\n\nCompound values and carefully constructed string values may also be\nspecified using XML syntax:\n<option-name>\n<sub-opt>...&lt;...&gt;...</sub-opt>\n</option-name>\nyielding an `option-name.sub-opt' string value of\n\"...<...>...\"\n`AutoOpts' does not track suboptions.  You simply note that it is a\nhierarchicly valued option.  `AutoOpts' does provide a means for\nsearching the associated name/value pair list (see: optionFindValue).\n\nThe command line options relating to configuration and/or usage help\nare:\n\nversion (-v)\n............\n",
            "subsections": []
        },
        "Print the program version to standard out, optionally with licensing": {
            "content": "information, then exit 0.  The optional argument specifies how much\nlicensing detail to provide.  The default is to print the license name\nwith the version.  The licensing infomation may be selected with an\noption argument.  Only the first letter of the argument is examined:\n\n`version'\nOnly print the version.\n\n`copyright'\nName the copyright usage licensing terms.  This is the default.\n\n`verbose'\nPrint the full copyright usage licensing terms.\n",
            "subsections": []
        },
        "File: sharutils.info,  Node: uuencode exit status,  Next: uuencode Bugs,  Prev: uuencode config,  Up: uuencode Invocation": {
            "content": "One of the following exit values will be returned:\n`0 (EXITSUCCESS)'\nSuccessful program execution.\n\n`1 (EXITFAILURE)'\nThe operation failed or the command syntax was not valid.\n\n`66 (EXNOINPUT)'\nA specified configuration file could not be loaded.\n\n`70 (EXSOFTWARE)'\nlibopts had an internal operational error.  Please report it to\nautogen-users@lists.sourceforge.net.  Thank you.\n",
            "subsections": []
        },
        "File: sharutils.info,  Node: uuencode Bugs,  Next: uuencode Standards,  Prev: uuencode exit status,  Up: uuencode Invocation": {
            "content": "Please put `sharutils' in the subject line for emailed bug reports.  It\nhelps to spot the message.\n",
            "subsections": []
        },
        "File: sharutils.info,  Node: uuencode Standards,  Next: uuencode History,  Prev: uuencode Bugs,  Up: uuencode Invocation": {
            "content": "This implementation is compliant with P1003.2b/D11.\n",
            "subsections": []
        },
        "File: sharutils.info,  Node: uuencode History,  Next: uuencode See Also,  Prev: uuencode Standards,  Up: uuencode Invocation": {
            "content": "The `uuencode' command first appeared in BSD 4.0.\n",
            "subsections": []
        },
        "File: sharutils.info,  Node: uuencode See Also,  Prev: uuencode History,  Up: uuencode Invocation": {
            "content": "uudecode(1), uuencode(5)\n",
            "subsections": []
        }
    },
    "flags": [],
    "examples": [],
    "see_also": []
}