.\" $Id: uuenview.1,v 1.2 1999/07/29 10:01:34 nakano Exp $ "
.\" Translated Sat May  8 17:29:25 JST 1999
.\"	by FUJIWARA Teruyoshi <fujiwara@linux.or.jp>
.\"0 WORD: backward compatible	ߴǤ
.\"0 WORD: backward compatibility	ߴ
.\"0 WORD: base name	١̾
.TH UUENVIEW 1 "July 1996"
.\"0 .SH NAME
.SH ̾
.\"0 uuenview \- a powerful encoder for binary files
uuenview \- ХʥեѤιǽʥ󥳡
.\"0 .SH SYNOPSIS
.SH 
.B "uuenview [-v] [-a] [-u|-x|-b] [-\fIlines\fP] [-o] [-od \fIpath\fP]"
.br
.B "         [-m \fIemail\fP] [-p \fInewsgroup\fP] [-s \fIsubject\fP]"
.br
.B "         [\fIfile(s)\fP]"
.br
.\"0 .SH DESCRIPTION
.SH 
.\"0 .I uuenview
.\"0 encodes a binary file into ASCII text for sending over non-8-bit
.\"0 electronic data channels, such as email or the usenet.
.\"0 .I uuenview
.\"0 is a superset of and fully backwards compatible with the standard
.\"0 .BR uuencode (1)
.\"0 command, featuring more comfort and more flexibility.
.I uuenview
ϥХʥե ASCII ƥȤ˥󥳡ɤ롣
ˤä 8 ӥåȤǤʤŻҥǡ̿ϩ(Żҥ᡼ usenet )
̤ƥХʥե褦ˤʤ롣
.I uuenview
ɸ
.BR uuencode (1)
εǽƻĴ˸ߴǤ뤬äȻȤ䤹
ǽäƤ롣
.PP
.\"0 Files encoded with
.\"0 .I uuenview
.\"0 are compatible with virtually all decoders, as long as the encoding
.\"0 method (see below) is supported by the remote side. If the remote
.\"0 side uses
.\"0 .BR uudeview (1),
.\"0 there shouldn't be any problems at all.
.I uuenview
ǥ󥳡ɤ줿եϡ󥳡ǥˡ()⡼¦
⥵ݡȤƤ¤ꡢۤܤɤʥǥȤߴǤ롣⡼¦

.BR uudeview (1)
ȤäƤ硢ʤϤǤ롣
.PP
.\"0 If properly configured,
.\"0 .I uuenview
.\"0 can directly send the encoded data by email or to the usenet. These
.\"0 messages are wrapped into a proper MIME envelope, which is handy if
.\"0 the recipient uses MIME-compliant mail or news software.
Ŭڤ򤹤С
.I uuenview
ϥ󥳡ɤǡľŻҥ᡼ usenet Ƥ
ȤǤ롣Τ褦ʥåˤŬڤ MIME ٥פդ
ΤǡԤ MIME Υ᡼˥塼꡼ȤäƤдñ
˰ȤǤ롣
.\"0 .SH OPTIONS
.SH ץ
.TP
.B -v
.\"0 Verbosely prints everything the program's trying to do.
ץब¹Ԥ褦ȤƤ뤳ȤܤϤ롣
.TP
.B -u
.\"0 Chooses the
.\"0 .I uuencoding
.\"0 method. This is the default for compatibility with
.\"0 .I uuencode (1).
.\"0 This encoding scheme is to date widely accepted as being the standard.
󥳡ˡȤ
.I uuencode
򤹤롣
.I uuencode (1)
ȤθߴΤ˥ǥեͤȤʤäƤ롣Υ󥳡ǥˡϡ
ߤǤɸȤƹƤ롣
.TP
.B -b
.\"0 Chooses the
.\"0 .I Base64
.\"0 encoding method as specified by the
.\"0 .I MIME
.\"0 standard. This scheme is expected to become the future standard.
.\"0 Use if the recipient uses MIME-compliant software (see note below).
󥳡ǥˡȤ
.I MIME
ʤǷƤ
.I Base64
򤹤롣ϤˡɸˤʤȻפ롣Ԥ MIME 
եȥȤäƤ()ˤϤΥץȤȡ
.TP
.B -x
.\"0 Chooses the now obsolete
.\"0 .I xxencoding
.\"0 method.
Ť󥳡ǥˡǤ
.I xxencoding
򤹤롣
.PP
.\"0 The -u, -b, -x options are mutually exclusive.
-u, -b, -x ץϤɤ줫 1 ĤǤ롣
.TP
.\"0 .B -lines
.B -Կ
.\"0 Substituting
.\"0 .I lines
.\"0 with a number,
.\"0 sets the maximum number of encoded lines per part. The encoded data
.\"0 is automatically split into as many parts as required. Line counts
.\"0 less than 200 are ignored. The uuencoding and xxencoding methods
.\"0 encode 45k, and Base64 encodes 57k of data in 1000 lines. If this
.\"0 option is not specified, the default is unlimited lines per part,
.\"0 resulting in exactly one part.
.I Կ
ʬˤϿ񤯡Υץϥ󥳡ɤƤԤΥѡȤ
Ȥκꤹ롣󥳡ɤ줿ǡϡưŪɬפʿʬ
롣Կ 200 꾮̵뤵롣󥳡ɤ 1000 ԤȤ
ǡ uuencode  xxencoding Ǥ 45kB ǤꡢBase64 Ǥ 57kB 
Ǥ롣Υץ󤬻ꤵƤʤϥѡȤȤιԿ¤
줺ѡȤ 1 ĤȤʤ롣
.TP
.B -o
.\"0 Specifies that output shall be written into files. These files will
.\"0 have the same base name as the source file and an extension of
.\"0 .B .001, .002
.\"0 etc, depending on the number of parts required by the
.\"0 .B \-lines
.\"0 option. The encoded files are written to the current directory.
Ϥե˽񤭹ळȤꤹ롣Υեϥե
Ʊ١̾ĥ
.B .001, .002, ...
ġĥҤ
.B \-Կ
ץˤäɬפȤѡȿˤäƷޤ롣󥳡ɤ줿
եϥȥǥ쥯ȥ˽񤭹ޤ롣
.TP
.\"0 .B -od path
.B -od ѥ
.\"0 Same as '-o', but the encoded files are written to the given
.\"0 directory instead.
`-o' ƱǤ뤬󥳡ɤ줿եϥȥǥ쥯ȥ
Ϥʤꤵ줿ǥ쥯ȥ˽񤭹ޤ롣
.TP
.\"0 .B -m email
.B -m Żҥ᡼륢ɥ쥹
.\"0 Mails the encoded file(s), each one probably split into multiple parts,
.\"0 to the given email address. Multiple recipients can be given as a 
.\"0 quoted, comma-separated list.
󥳡ɤե(ʣ)Ϳ줿Żҥ᡼륢ɥ쥹롣
줾ΥեʣΥѡȤʬ䤵뤳Ȥ⤢롣Ȥ
޶ڤΥꥹȤȤơʣΰꤹ뤳ȤǤ롣
.TP
.\"0 .B -p newsgroup
.B -p ˥塼롼
.\"0 Posts the encoded file(s), each one probably split into multiple parts,
.\"0 to the given newsgroup. Multiple newsgroups can be given as a quoted,
.\"0 comma-separated list. The
.\"0 .I inews(1)
.\"0 program is invoked for posting. You may have to set the
.\"0 .I NNTPSERVER
.\"0 enviroment variable to your news server.
󥳡ɤե(ʣ)Ϳ줿˥塼롼פƤ롣
줾ΥեʣΥѡȤʬ䤵뤳Ȥ⤢롣Ȥ
޶ڤΥꥹȤȤơʣΥ˥塼롼פꤹ뤳ȤǤ롣
ݥȤκݤˤ
.I inews(1)
ץबư롣Ѥ˥塼ФĶѿ
.I NNTPSERVER
ꤹɬפ뤫⤷ʤ
.TP
.\"0 .B -s subject
.B -s ֥
.\"0 This subject will be used when mailing or posting the file. Be careful
.\"0 to quote subjects of more than one word. The file name and part number
.\"0 is automatically appended to the subject line.
եΥ᡼˥塼ƤκݤˡΥ֥ȤѤ롣
ʣθ줫ʤ륵֥ȤɬȤ뤳ȡե̾ȥѡ
ֹ椬ưŪ˥֥ȹԤɲä롣
.TP
.B -a
.\"0 Attaches files. This feature is expected to be used from shell scripts
.\"0 and the like. It causes an email message (or usenet posting) to be read
.\"0 from standard input. The files given on the command line are then
.\"0 "attached" to the message, which is converted to proper MIME multipart
.\"0 format. The result is written to the standard output except if either
.\"0 the \-m or \-p parameter is used (potentially overriding the Newsgroup
.\"0 or To selection from the message headers). Use Base64 when encoding
.\"0 attachments.
ե(ʣ)źդ롣εǽϥ륹ץȤ뤳
ȤꤷƤ롣ΥץꤹŻҥ᡼Υå(
 usenet ؤ)ɸϤɤ߹ޤ롣θ塢ޥɥ饤
Ϳ줿ե뤬åˡźաפ롣Ŭڤ MIME 
ޥѡȷѴ롣\-m ޤ \-p ѥ᡼ꤷ
(λϥåإå Newsgroup  To λ񤭤ǽ
)̤ɸϤ˽񤭽Ф롣źեե򥨥󥳡
ˤ Base64 Ȥȡ
.TP
.\"0 .B file(s)
.B ե(ʣ)
.\"0 One or more filenames to be processed. Each file is encoded and then
.\"0 stored in a file, mailed and/or posted according to the \-o, \-m and
.\"0 \-p options. If none of these options is given, the encoded file is
.\"0 sent to standard output. To encode a file from the standard input, use
.\"0 a single hyphen '\-' and give a filename to be used by the
.\"0 encoded file as the next parameter.
ե 1 İʾꤹ롣줾Υեϥ󥳡ɤ
줿塢ץ˽äƥե˳Ǽ줿(\-o ץ)᡼
줿(\-m ץ)˥塼롼פƤ(\-p 
ץ)Υץꤵʤäˤϡ󥳡ɤ
줿եɸϤ롣ɸϤɤ߹ǥե򥨥
ɤˤϥϥե 1 ('\-')ѤΥѥ᡼Ȥƥ󥳡
ɤ줿ե뤬Ȥե̾Ϳ뤳ȡ
.\"0 .SH NOTES
.SH 
.\"0 Reading from standard input and writing to standard output enforces
.\"0 certain limitations.
ɸϤɤ߹ߤɸϤؤν񤭽Фκݤˤ¤ä롣
.TP
.B 1.
.\"0 Files read from standard input can only be used once, meaning that
.\"0 either none or exactly one of the \-o, \-m, \-p options may be given.
ɸϤɤ߹ե 1 ٤ȤʤĤޤꡢ\-o, \-m,
\-p ץȤʤ 1 ĤȤʤΤɤ餫Ǥ롣
.TP
.B 2.
.\"0 Output written to standard output cannot be split into multiple parts.
.\"0 In this case, the
.\"0 .B -lines
.\"0 option is ignored.
ɸϤؤν񤭽ФǤϡʣѡȤؤʬϹԤʤޤξ
ˤ
.B -Կ
ץ̵뤵롣
.PP
.\"0 .I uuenview
.\"0 must be correctly configured at compile time in order to make automated
.\"0 mailing and posting work. If it doesn't, consult your system administrator.
.\"0 The program used for posting a file can be set at runtime using the
.\"0 .I INEWS
.\"0 environment variable. This setting overrides the compile-time configuration.
᡼˥塼ƤưŪ˹Ԥ碌ˤϡ
.I uuenview
򥳥ѥꤷʤФʤʤޤưʤˤϡ
ƥԤ̤뤳ȡ˥塼Ƥ˻Ȥץϡ
ѿ
.I INEWS
ȤäƼ¹Իꤹ뤳ȤǤ롣ϥѥ
ͥ褵롣
.PP
.\"0 Base64 is not MIME. Base64 is the encoding specified by the MIME standard,
.\"0 but in order for a message to become a proper MIME message, a number of
.\"0 headers are required.
Base64  MIME ǤϤʤBase64  MIME ʤǷƤ륨󥳡ǥ
󥰤Ǥ뤬å MIME åˤ뤿ˤϥإ
򤿤դɬפ롣
.\"0 .I uuenview
.\"0 produces these headers when mailing or posting, but not when writing to
.\"0 a local file, since in this case, the program does not have the necessary
.\"0 control over the headers. If you plainly include Base64 output into your
.\"0 messages, they are
.\"0 .B not
.\"0 MIME-compliant! Therefore, use uuencoding in this case. 
Τ褦ʥإåϥ᡼˥塼Ƥκݤ
.I uuenview
뤬եؤν񤭹ߤλˤϹԤʤ
Τ⡢ξˤϥإå椹ɬפʤǤ롣Base64 
Ϥ򤽤Τޤޤηǥå줿硢Υå MIME 
Ǥ
.B ʤ
! äơΤ褦ʾˤ uuencode Ȥȡ
.PP
.\"0 If you rename, copy or link the program to
.\"0 .BR uuencode ,
.\"0 it may act as a smart replacement for the standard, accepting the same
.\"0 command-line syntax. This has not been well-tested yet.
Υץ̾Ѥꡢԡꡢ󥯤򤹤뤳Ȥˤä
.BR uuencode
ˤ硢Υץɸ
.BR uuencode
ιǽѥץȤưƱޥɥ饤󥪥ץ
դ롣ƥȤϤޤʬǤʤ
.\"0 .SH EXAMPLES
.SH 
.TP
uuenview -m 'root,fred@somewhere.com' uudeview.tgz
.\"0 Encodes the file
.\"0 .I uudeview.tgz
.\"0 and mails it to both your local system administrator and to your friend
.\"0 Fred at the Somewhere company.
ե
.I uudeview.tgz
򥨥󥳡ɤΥƥԤȤɤβҤˤͧ 
Fred ξ˥᡼롣
.PP
.\"0 If you give more than one filename on the command line, each file is
.\"0 usually handled separately. A workaround is to send them all as
.\"0 attachment to a single (or empty) mail:
ʣΥե̾򥳥ޥɥ饤Ϳ硢줾Υե̾
̡˽롣򤹤ˤϡƤΥե 1 (뤤϶
)᡼źդ뤳ȡ
.TP
uuenview -m root -b -a file1 file2 < /dev/null
.\"0 Creates an empty mail and attaches the two given files, encoded in
.\"0 Base64 format, and mails the result to your system administrator.
Υ᡼˻ꤵ줿ե 2 Ĥź(Base64 
󥳡)ˤη̤򥷥ƥԤ˥᡼롣
.\"0 .SH "SEE ALSO"
.SH Ϣ
.BR uudeview (1),
.BR uuencode (1),
.BR uudecode (1),
.BR mail (1),
.BR inews (1),
.PD 0
.PP
.\"0 The
.\"0 .I uudeview
.\"0 homepage on the Web, 
־
.I uudeview
Υۡڡ:
.PD 0
.PP
http://www.uni-frankfurt.de/~fp/uudeview/
.PD
.\"0 .SH BUGS
.SH Х
.PP
.\"0 The program cannot detect error conditions when mailing or posting.
᡼˥塼Ƥκݤ˥顼֤򸡽Ф뤳ȤǤʤ
.PP
.\"0 Attaching only works reliably if certain headers of the input message
.\"0 (for example
.\"0 .I Content-Type
.\"0 )
.\"0 are not folded and shorter than 1024 characters.
źդǤư򤹤ΤϡϥåΥإå(㤨
.I Content-Type
)ޤ֤Ƥ餺 1024 ʸ̤ξǤ롣
.PP
.\"0 It is not yet possible to encode into BinHex.
ޤ BinHex 򥨥󥳡ɤ뤳ȤǤʤ