.\" $Id: uudeview.1,v 1.3 2004/04/14 17:49:58 ysato Exp $ "
.\" Translated Sat May  8 17:28:30 JST 1999
.\"	by FUJIWARA Teruyoshi <fujiwara@linux.or.jp>
.\"0 WORD: plain text	ץ졼ƥ
.TH UUDEVIEW 1 "December 1996"
.\"0 .SH NAME
.SH ̾
.\"0 uudeview \- a powerful decoder for binary files
uudeview \- ХʥեѤιǽʥǥ
.\"0 .SH SYNOPSIS
.SH 
.B "uudeview [-i] [-d] [-f] [-o] [-b1] [-t] [(+e|-e) \fIextlist\fP]"
.br
.B "         [-v] [-s] [-m] [-n] [-p \fIpath\fP] [@file] \fIfile(s)\fP"
.br
.\"0 .SH DESCRIPTION
.SH 
.\"0 .I uudeview
.\"0 decodes files that you have received in encoded form via electronic mail
.\"0 or from the usenet, similar to the standard
.\"0 .BR uudecode (1)
.\"0 command, yet with more comfort and flexibility.
.I uudeview
ϡŻҥ᡼ Usenet ä󥳡ɤ줿Υե
ǥɤ롣ɸ°
.BR uudecode (1)
˻Ƥ뤬ŬĽǤ롣
.\"0 .I uudeview
.\"0 supports the
.\"0 .I uuencoding, xxencoding, Base64
.\"0 and
.\"0 .I BinHex
.\"0 encoding methods, and is able to handle split-files (which have been sent
.\"0 in multiple parts) as well as multiple files at once, thus greatly simplifying
.\"0 the decoding process. Usually, you will not have to manually edit files to
.\"0 prepare them for decoding.
.I uudeview
ϥ󥳡ǥˡȤ
.I uuencoding, xxencoding, Base64, BinHex
򥵥ݡȤƤꡢʬե(ʣʬʬ줿)򰷤
ȤǤʣΥեƱ˰ȤǤ롣äơ
ǥɤμ֤礭ʤȤǤ롣桼̡ǥɤν
뤿˥եԽɬפϤʤ
.PP
.\"0 After invoking
.\"0 .I uudeview,
.\"0 it will scan all given files for encoded data, sort them and their parts
.\"0 and then present you with the list of files that seem like they can be
.\"0 decoded properly. You can then pick files individually for decoding.
.I uudeview
ϵưȡͿ줿եƥ󤷤ƥǥɤ٤ǡ
õΥǡȥǡ˴ޤޤѡȤ򥽡Ȥޤǥ
Ǥʥեΰ桼˼桼Ϥΰǥɤ
ե̤֡
.\"0 .SH OPTIONS
.SH ץ
.TP
.B -i
.\"0 Disables interactivity. After scanning the files and sorting everything out,
.\"0 the program will not ask for whether a file shall be decoded or not, but
.\"0 immediately batch-decodes everything possible.
õǽ̵ˤ롣եΥȤη̤ΥȤԤä塢
.I uudeview
ϥեǥɤ뤫ɤ桼䤤碌ǥɲǽ
Τ¨¤˥Хåǥǥɤ롣
.TP
.B -d
.\"0 Sets the program into desperate mode. It will then offer you to decode
.\"0 incomplete files. This is useful if you are missing the last part of a
.\"0 50-parts posting, but in most cases the desperately-decoded files will
.\"0 simply be corrupt and unusable. The degree of usefulness of an incomplete
.\"0 file depends on the file type.
.I uudeview
 desperate ⡼ɤˤ롣Υ⡼ɤǤϡԴʥեǥ
θȤʤ롣εǽͭʤΤ 50 ĤΥѡȤʬ줿ƤκǸ
ʬ礱Ƥ褦ʾǤ뤬ξϡ̵˥ǥɤե
ñ˲ƤѤϤǤʤԴʥե뤬ɤ
ٻȤ뤫ϥեμˤ롣
.TP
.B -f
.\"0 Uses fast mode for file scanning. The program assumes that each input file
.\"0 holds at most one part, which is usually true for files in a news spool
.\"0 directory. This option
.\"0 .B breaks decoding
.\"0 of input files with multiple articles. Also, certain sanity checks are
.\"0 disabled, probably causing erroneous files to be presented for decoding.
.\"0 Sometimes you'll get error messages when decoding, sometimes you'll
.\"0 just receive invalid files. Don't use
.\"0 .B -f
.\"0 if you can't live with these problems.
®⡼ɤǥե򥹥󤹤롣
.I uudeview
ϳϥե¿Ȥ 1 ե뤷ޤޤƤʤΤꤹ롣
̡˥塼סˤեˤĤƤΩġΥ
ץꤹȡʣεʬ줿ϥեΥǥɤ
.B Ǥ
ޤǡɤΥå̵ˤʤΤǡ꤬
ե⤪餯ǥɤθȤƼ롣ǥɤλ˥顼
å뤳Ȥ⤢뤷ñʥե뤬Ǥ뤳Ȥ⤢롣
Τ褦ʤʤ
.B -f
ץϻȤʤȡ
.TP
.B -o
.\"0 Gives the OK to overwrite existing files when decoding. The default is
.\"0 to prompt the user whether to overwrite, rename or skip the file.
ǥɻ˴¸Υե񤭤뤳ȤĤ롣ǥեȤǤϡ
񤭤뤫̤̾դ뤫ΥեФ䤤碌
桼ФƹԤ롣
.TP
.B -v
.\"0 .B Disables
.\"0 verbosity. Normally, the program prints some status messages
.\"0 while reading the input files, which can be very helpful if something
.\"0 should go wrong. Use if these messages disturb you.
ܺɽ
.B ̵
롣̾Υץϥեɤ߹ݤ˲餫Υơ
åɽ롣꤬ȤˤΩġ
褦ʥåݵƫˤΥץȤȡ
.TP
.\"0 .B -p path
.B -p ѥ
.\"0 Sets the path where decoded files shall be written to. This must be a valid
.\"0 pathname, or you'll get errors when trying to decode anything. Defaults to
.\"0 the current working directory.
ǥɤե񤭹ǥ쥯ȥꤹ롣ͭʥѥ
̾ǤʤФʤ餺Ǥʤϥեǥɤ褦Ȥ
顼Ȥʤ롣ǥեͤϸߤκȥǥ쥯ȥǤ롣
.TP
.\"0 .B +e exts
.B +e ĥ
.\"0 Selects only the files with the given extensions for decoding, others will
.\"0 be ignored.
.\"0 .B +e .gif.jpg
.\"0 would decode all gif and jpeg files, but not tif or other files. The
.\"0 list of extensions works case-insensitive.
ꤵ줿ĥҤĥե򤷤ƥǥɤ롣¾Υե
̵뤵롣
.B +e .gif.jpg
ꤹȡGIF ե JPG եƥǥɤ뤬TIF
ϥǥɤʤĥҤΥꥹȤǤʸȾʸ϶̤ʤ
.TP
.\"0 .B -e exts
.B -e ĥ
.\"0 The reverse of the above.
嵭ΥץȿФΰ̣ġ
.PP
.\"0 You will experience unwanted results if you try to mix \+e and \-e options
.\"0 on the command line.
ޥɥ饤 \+e  \-e 򺮤ƻȤäƤ⡢˾̤ʤ

.TP
.B -b1
.\"0 This changes
.\"0 .I uudeview's
.\"0 policy of finding a part number on a subject line and may only be needed
.\"0 in some rare cases when part numbers are found in () parentheses as well
.\"0 as in [] brackets, for example in a series of multi-part postings. By
.\"0 default,
.\"0 .I uudeview
.\"0 uses the numbers found in () parentheses first. But if this number indicates
.\"0 the file's number in the series and the part number is given in [] brackets,
.\"0 use this parameters to make the program read the other number first. This
.\"0 does not affect decoding of files with only one or neither type of brackets.
.\"0 If you prefer, you can also use the option as
.\"0 .B -b[]
Υץϡ֥ȤѡֹФȤ
.I uudeview
Υݥꥷѹ롣ΥץɬפȤʤΤϵǤ뤬
㤨ʣʬ䤷ƤԤ줿Τ褦ˡѡֹ椬  () 
֥饱å [] ˽񤫤ƤɬפȤʤ롣ǥեȤǤϡ
.I uudeview
Ϥޤ  () ˤȤֹ椬ΤΥե
򼨤Ƥꡢѡֹϥ֥饱å [] ˽񤫤ƤˤϡΥ
᡼Ȥä
.I uudeview
¾οǽɤ߹ޤ褦ˤ뤳ȡΥץϡ1 
Υ֥饱åȤޤޤʤե䡢ɤμΥ֥饱åȤޤޤʤ
եŸˤϱƶͿʤɬפʤСΥץ
.B -b[]
Τ褦˻ȤȤǤ롣
.TP
.B -s
.\"0 Read "minus smartness". This option turns off automatic part number
.\"0 detection from the subject line. Try this option if
.\"0 .I uudeview
.\"0 fails to parse the subject line correctly and makes errors at guessing
.\"0 part numbers, resulting in incorrect ordering of the parts. With this
.\"0 option, parts are always put together sequentially (so the parts must
.\"0 be correctly ordered in the input file). Also, with this option, the
.\"0 program cannot detect that parts are missing.
ָʤ(minus smartness)פɤळȡΥץϡ֥
ȹԤѡֹưФ뵡ǽ̵ˤ롣
.I uudeview
֥ȹԤŸ˼Ԥƥѡֹο˥顼
ѡȤν֤ˤϤΥץȤ褤Υץ
ȤȡѡȤɬ̤˷Ҥ(äơϥե
ǤϥѡȤ¤٤ʤФʤʤ)ޤΥץ
ȡץϷ礱ƤѡȤ򸡽Ф뤳ȤϤǤʤ
.\"0 .B Note:
.\"0 The correct part number found in proper
.\"0 .I MIME
.\"0 files is still evaluated.
.\"0 If this option is given twice, the subject itself is ignored, too, and
.\"0 won't be used to group parts. Use if the messages that the parts come
.\"0 delivered in have different subject lines.
.B :
ξǤ⡢Ȥ
.I MIME
ե˴ޤޤƤѡֹɾ롣Υץ
2 ꤹȡ֥ȤΤΤ̵뤵졢ѡȤΥ롼դ
ϻȤʤѡȤϢΥåΥ֥ȹԤ줾
ۤʤˤϡΥץѤ뤳ȡ
.TP
.B -m
.\"0 Ignore file mode. uuencoded and xxencoded files have the original file
.\"0 permissions stored on the begin line. If this option is not given, the
.\"0 decoder tries to restore them. With this option, the resulting permissions
.\"0 will always be 0666 minus your umask.
եΥ⡼ɤ̵뤹롣uuencode  xxencode 줿ե
begin ԤˤϡΥեΥѡߥå󤬽񤫤Ƥ롣Υץ
ͿʤСǥϸΥѡߥå褦Ȥ롣
ΥץͿȡѡߥå 0666 桼
umask ͤȤʤ롣
.TP
.B -n
.\"0 No progress bars. Normally, UUDeview prints ASCII bars crawling up
.\"0 to 100 percent, but does not check if your terminal is capable of
.\"0 displaying them. Use this switch if your terminal isn't, or if you
.\"0 find the bars annoying.
ץ쥹Сɽʤuudeview ̾ʹԾ˹碌 100%
ޤǿӤƤ椯 ASCII ʸɽ뤬üɽǤ뤫
ɤΥåϹԤʤüɽǤʤ䡢ץ쥹С
ܾȴˤϤΥץȤȡ
.TP
.B -t
.\"0 Use plaintext messages. Usually, uudeview only presents encoded data
.\"0 for decoding. With this option set, text parts from
.\"0 .I MIME
.\"0 messages and non-encoded messages are also offered. Plaintext messages
.\"0 frequently don't have an associated filename, so they're assigned a
.\"0 unique name from a sequential four-digit number.
ץ졼ƥȤΥåȤ̾uudeview ϥǥɤκݤˤ
󥳡ɤ줿ǡɽ롣Υץꤹȡ
.I MIME
åäƤƥȥѡȤ䥨󥳡ɤƤʤǡ
оݤȤƼ롣ץ졼ƥȤΥåˤϥե̾
դƤʤȤ¿Τǡˤ 4 ֹ̤Ȥäˡ
̾դ롣
.TP
.\"0 .B file(s)
.B ե(ʣ)
.\"0 The files to be scanned for encoded files. You can also give a single hyphen
.\"0 \'\-\' to read from standard input. Any number of files may be given, but
.\"0 there is usually a limitation of 128 options imposed by the shell. If you are
.\"0 composing the list of files with wildcards, make sure you don't accidentally
.\"0 feed the program with binary files. This will result in undefined behaviour.
󥳡ɤ줿եõ˥󤹤ե롣ϥե
(\'\-\')ꤹСɸϤɤ߹ळȤǤ롣ꤹե
οϤĤǤɤ̾ϥ뤬ץο 128 ĤޤǤ
¤Ƥ롣磻ɥɤȤäƥեΥꥹȤäˤϡ
ְäƥХʥեץϤʤȡʤä
ư̤Ǥ롣
.TP
.\"0 .B @file
.B @ե
.\"0 Makes
.\"0 .I uudeview
.\"0 read further options from the file. Each line of the file must hold exactly
.\"0 one option. The file 
.\"0 .B is erased 
.\"0 after the program finishes. This feature may be used to specify an unlimited
.\"0 number of files to be scanned. Combined with the powers of
.\"0 .BR find (1),
.\"0 entire directory trees (like the news spool directory) can be processed.
ɲäΥץե뤫
.I uudeview
ɤ߹ޤ롣ΥեǤ 1 Ԥ 1 Ĥץ񤫤ʤ
ФʤʤΥեϥץνλ
.B 
εǽȤȥե򲿸ĤǤꤹ뤳ȤǤ롣
.BR find (1)
εǽȤ߹碌Сǥ쥯ȥĥ꡼(˥塼סΥǥ
쥯ȥ)뤳ȤǤ롣
.PP
.\"0 Options may also be set in the $UUDEVIEW environment variable, which is
.\"0 read before processing the options on the command line.
Ķѿ $UUDEVIEW ˥ץꤹ뤳ȤǤ롣ͤϥޥ
ɥ饤Υץɤ߹ޤ롣
.\"0 .SH DECODING
.SH ǥ
.\"0 After all input files have been scanned, you are asked for each file what
.\"0 do do with it. Of course, the usual answer is to decode it, but there are
.\"0 other possibilities. You can use the following commands (each command is
.\"0 a single letter):
ϥեƥ󤷤塢줾ΥեΰˤĤƥ桼
䤤碌Ԥ롣ʤ̤ϥǥɤμ¹ԤΤ
¾ˤ⤢롣ʲΥޥɤѤ뤳ȤǤ(ƥޥɤ 
1 ʸǤ):
.TP
.B d
.\"0 (D)ecode the file and write the decoded file to disk, with the given name.
եǥɤǥɤեꤵ줿̾ǥǥ
񤭹ࡣ
.TP
.B y
.\"0 (Y)es does the same as (d).
(d) ƱưǤ롣
.TP
.B x
.\"0 E(x)tract also decodes the file.
Υޥɤեǥɤ롣
.TP
.B n
.\"0 Skips this file without decoding it.
ΥեǥɤʤФ
.TP
.B b
.\"0 Steps back to the previous file.
Υե롣
.TP
.B i
.\"0 Displays info about the file, if present. If a multipart posting had a
.\"0 zeroeth part, it is printed, otherwise the first part up to the encoded
.\"0 data is printed.
ե˴ؤ󤬤Сɽ롣ޥѡȤƤ 0
ܤΥѡȤФɽ롣0 ܤΥѡȤʤС󥳡
ɤƤǡޤǤˤǽΥѡȤɽ롣
.TP
.B e
.\"0 Execute a command. You can enter any arbitrary command, possibly using the
.\"0 current file as an argument. All dollar signs '$' in this command line are
.\"0 replaced with the filename of the current file (speaking correctly, the name
.\"0 of a temporary file). You should not background processes using this
.\"0 temporary file, as programs might get confused if their input file suddenly
.\"0 disappears.
ޥɤ¹Ԥ롣ɤʥޥɤǤϤ뤳ȤǤ뤬κݤ
¿ʬߤΥե뤬ȤƻȤޥɥ饤
ɥ뵭 '$' ơߤΥեΥե֤̾(Τ
ϰե̾)ΰեȤäƥХå饦ɥץ
¹ԤƤϤʤʤʤʤ顢ϥե뤬ä˥ץ
ν𤹤뤫Ǥ롣
.TP
.B l
.\"0 List a file. Use this command only if you know that the file in question is
.\"0 a textfile, otherwise, you'll get a load of junk.
եꥹɽ롣ΥޥɤȤΤϡ䤤碌оݤΥե
뤬ƥȥեξˤ뤳ȡǤʤˤϥߤ
̤ˤǤǤ롣
.TP
.B r
.\"0 Rename. You can choose a different name for the file in order to save it
.\"0 under this new name.
̾Ѥ롣̤̾ǡΥե򿷤̾¸뤳
Ǥ롣
.TP
.B p
.\"0 Set the path where decoded files shall be written to. This path can also
.\"0 be set with the -p command line option.
ǥɤե񤭹ѥꤹ롣Υѥϡޥɥ饤
󥪥ץ -p ޥɤꤹ뤳ȤǤ롣
.TP
.B q
.\"0 Quits the program immediately.
¨¤˥ץλ롣
.TP
.B ?
.\"0 Prints a short description of all these commands.
ʾΥޥƤδñɽ롣
.PP
.\"0 If you don't enter a command and simply hit return at the prompt, the
.\"0 default command, decoding the file, is used.
ޥɤϤʤǡץץȤǥ꥿󥭡áˤϡ
ǥեȤΥޥɤǤեΥǥɤ¹Ԥ롣
.\"0 .SH RUNTIME MESSGAGES
.SH ¹ԻΥå
.\"0 In verbose mode (that is, if you didn't disable verbosity with the
.\"0 -v option), progress messages will appear.
.\"0 They are extremely helpful in tracing what the program does, and can
.\"0 be used to figure out the reason why files cannot be decoded, if you
.\"0 understand them. This section explains how to interpret them.
.\"0 Understanding this section is not essential to operate the program.
ܺɽ⡼(Ĥޤꡢ-v ץǾܺɽ̵ˤƤʤ)
ǤϡʹԾåϤ롣Υåϥץμ¹
פΤǤꡢǤХեΥǥɤ
Ԥɵ˻ȤȤǤ롣ΥǤϥåβ
λ롣ץʤСΥ
򤹤뤳ȤϤޤפǤʤ
.PP
.\"0 First, there are "Loading" messages, which begin with the string
.\"0 "Loaded". Each line should feature the following items:
ǽϡ֥פΥåǤ롣ʸ "Loaded" ǻϤޤ롣
줾ιԤϰʲǤ򼨤ʤƤϤʤʤ:
.TP
.\"0 .B Source File
.B ϥե
.\"0 The first item is the source file from which a part was loaded. Many
.\"0 parts can be detected within a single file.
ǽǤϥեǤꡢѡȤɤ롣
1 ĤΥե뤫¿ΥѡȤФ뤳Ȥ⤢롣
.TP
.\"0 .B Subject Line
.B ֥ȹ
.\"0 The complete subject is reproduced in single quotes.
ʥ֥Ȥ󥰥륯Ȥdz줿ǺƸ롣
.TP
.\"0 .B Identifier
.B ̻
.\"0 The program derives a unique identification for this thread from the
.\"0 subject line, for grouping articles that look like they belong to the
.\"0 same file. The result of this algorithm is presented in braces.
ΥץϡƱե°ƤȻפ뵭ޤȤ뤿ᡢ
֥ȹԤѤƤΥåɤˡ˼̤롣Υ르
η̤ϥ֥졼dzäɽ롣
.TP
.\"0 .B Filename
.B ե̾
.\"0 If a filename was detected on the subject line or within the data (for
.\"0 example, on a begin line, or as part of the Content-Type information).
֥ȹԤǡǥե̾Ф줿ɤ(㤨Сbegin
Ԥ Content-Type ΰȤƸФ)
.TP
.\"0 .B Part Number
.B ѡֹ
.\"0 The part number derived from the subject line, or, in the case of
.\"0 properly MIME-formatted messages, from the "part" information.
ѡֹɽ֥ȹԤФ줿ꡢȤ MIME
Υåξˤϡ֥ѡȡ׾󤫤Ф줿ꤹ롣
.TP
.B Begin/End
.\"0 If a "begin" or "end" token was detected, it is printed here.
"begin" ȡ "end" ȡ󤬸Ф줿硢줬ǽϤ
롣
.TP
.\"0 .B Encoding Type
.B 󥳡ǥ󥰷
.\"0 If encoded data was detected within this part, either "UUdata",
.\"0 "Base64", "XXdata" or "Binhex" is printed here.
Υѡǥ󥳡ɤ줿ǡФ줿硢"UUdata",
"Base64", "XXdata", "Binhex" Τ줫Ϥ롣
.PP
.\"0 More messages are printed after scanning has completed. A single line
.\"0 will be printed for each group of articles. The contents of this line
.\"0 are best understood by looking at an example. Here is one:
󤬽äˤϤʳΥåϤ롣Υ롼
פ줾Ф 1 ĤιԤϤ롣ιԤƤǸʬ
䤹ʲ򼨤:
.PP
.B Found 'mailfile.gz' State 16 UUData Parts begin 1 2 3 4 5 end 6 OK
.PP
.\"0 This indicates that the file
.\"0 .I mailfile.gz
.\"0 has been found. The file was uuencoded ("UUData") and consists of
.\"0 6 parts. The "begin" token was found in the first part, and the
.\"0 "end" token was found in the sixth part. Because it looks like
.\"0 everything's there, this file is tagged as being "OK". The
.\"0 .I State
.\"0 is a set of bits, where the following values may be or'ed:
ιԤϥե
.I mailfile.gz
ĤäȤ򼨤ե uuencode Ƥ("UUData")6 
ΥѡȤʤ롣ޤ"begin" ȡ󤬺ǽΥѡȤǸĤꡢ
"end" ȡ 6 ܤΥѡȤǸĤä·äƤ褦˸
ΤǡΥեˤ "OK" Υդ롣
.I State
ˤϰʲ˼ƼӥåȤꤵ롣ӥåȤͤ OR 뤳Ȥ⤢
.TP
.B 1
.\"0 Missing Part
礱ƤѡȤ
.TP
.B 2
.\"0 No Begin
Begin ̵
.TP
.B 4
.\"0 No End
End ̵
.TP
.B 8
.\"0 No encoded data found.
󥳡ɤƤǡĤʤ
.TP
.B 16
.\"0 File looks Ok
եʤȻפ
.TP
.B 32
.\"0 An error occured during decoding of the file.
եΥǥɻ˥顼
.TP
.B 64
.\"0 File was successfully decoded.
ե뤬ޤǥɤǤ
.\"0 .SH NOTES
.SH 
.\"0 Because the program cannot receive terminal input when reading from standard
.\"0 input, the interactivity is automatically disabled in this case.
ΥץϡɸϤɤ߹ߤԤȤˤüϤ
뤳ȤǤʤΤǡξˤõǽϼưŪ̵ˤ롣
.PP
.\"0 When MIME-style message headers are detected, the program behaves nearly
.\"0 MIME-compliant.
MIME ΥåإåФ줿ȤϡΥץϤۤ
MIME ưԤ
.\"0 .I Nearly,
.\"0 because the standard does not allow a file to hold more than one messages,
.\"0 but
.\"0 .I uudeview
.\"0 works without this restrictions. Actually, if you guarantee this condition
.\"0 using the 
.\"0 .B -f
.\"0 command line switch, the program fully complies to RFC1521.

.I ۤ
פȤΤϡǤϥե뤬ʣΥåޤळȤǧ
ʤɡ
.I uudeview
Ϥ¤ʤư뤫Ǥ롣ºݤˤϡޥɥ饤󥪥ץ
.B -f
Ѥɬξ֤ˤʤ褦ˤСΥץ RFC1521 ˴
˽򤹤롣
.\"0 (Even with this switch set, all parts of a proper MIME multipart message
.\"0 are handled.)
(ΥץꤵƤƤ⡢ MIME ޥѡȥå
˴ޤޤѡȤƽ롣)
.PP
.\"0 The scanner tends to ignore short Base64 data (less than four lines)
.\"0 outside of MIME messages. Some checks for this condition are used in
.\"0 desperate mode, but they may cause misdetection of encoded data,
.\"0 resulting in some invalid files.
νʬϡMIME åγˤû Base64 ǡ(4
԰ʲ)̵뤹뤳Ȥ褯롣ξ֤ФåĤ
desperate ⡼ɤǹԤ뤬Ԥȥ󥳡ɤ줿ǡ
ƸФʥե뤬Ǥ뤳Ȥ롣
.PP
.\"0 Files are always decoded into a temporary file first, then this file is copied
.\"0 to the final location. This is to prevent accidentally overwriting existing
.\"0 files with data that turns out too late to be undecodeable. Thus be careful
.\"0 to have twice the necessary space available. Also, when reading from
.\"0 standard input, all the data is dumped to a temporary file before
.\"0 starting the usual scanning process on that file.
եϺǽɬե˥ǥɤ졢θ˺ǽŪʾ
ԡ롣ϡˤʤäƤǥɤǤʤȤʬ褦
ǡǴ¸Υեäƾ񤭤뤳ȤɤǤ롣
ơɬפʥ 2 ܤζڡͽݤ뤳ȡޤɸ
Ϥɤ߹ߤԤˤϡƤΥǡϰե˽񤭹ޤ졢
θˤΥեФ̾ΥϤ롣
.PP
.\"0 .I uudeview
.\"0 tries to derive all necessary information from the Subject: line if present.
.\"0 If it holds garbage, or if the program fails to find a unique identification
.\"0 and the part number there, 
.\"0 .I uudeview
.\"0 might still be able to decode the file using other heuristics, but you'll
.\"0 need major luck then.
Subject ԤС
.I uudeview
ɬפʾƤ򤳤ιԤФȤ롣Subject Ԥ˥ߤ
Ƥ䡢ץबˡʼ̾ȥѡֹ Subject 
鸫ĤʤäǤ⡢
.I uudeview
̤Υҥ塼ꥹƥѤƥեǥɤ뤳ȤǤ뤬
ξη̤ϱǤǤ롣
.PD 0
.PP
.\"0 Yet this is only a concern with split-files. If all encoded files only consist
.\"0 of single parts, don't worry.
줬طΤϥե뤬ʬ䤵ƤǤ롣
ɤ줿ե뤬 1 ĤΥѡȤʤˤϲ⿴ۤ
ɬפϤʤ
.PD
.PP
.\"0 If you rename, copy or link the program to
.\"0 .BR uudecode ,
.\"0 it may act as a smart replacement for the standard, accepting the same
.\"0 command-line options. This has not been well-tested yet.
Υץ̾Ѥꡢԡꡢ󥯤򤹤뤳Ȥˤä
.BR uudecode
ˤ硢Υץɸ
.BR uudecode
ιǽѥץȤưƱޥɥ饤󥪥ץ
դ롣ƥȤϤޤʬǤʤ
.\"0 .SH "SEE ALSO"
.SH Ϣ
.BR uuenview (1),
.BR uudecode (1),
.BR uuencode (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 Х
.\"0 To read a file whose name starts with a hyphen '-', prepend a path
.\"0 name, for example './'.
̾ϥե('-')ǻϤޤեɤ߹ˤϡѥ̾(㤨 './')
դ뤳ȡ
.PP
.\"0 Before reporting a bug, make sure the file can be decoded by other means. I
.\"0 hate to receive bug-reports where it turns out that
.\"0 .I uudeview
.\"0 just failed to decode complete garbage.
ХȤ𤹤ˤϡΥե뤬¾μʤǥǥɤǤ뤳Ȥ
Τ뤳ȡԤϡΥߤΥǥɤ˼ԤȸǤ狼褦
Хϼꤿʤ
.PP
.\"0 If you think you've found a bug, email the source file (at best,
.\"0 compress and encode the original file, don't just include it) and
.\"0 a listing of the program's messages (from verbose mode) to
.\"0 .I fp@informatik.uni-frankfurt.de.
Х򸫤ĤȻפä顢ϥե(ǤñǤʤ
Υե˰̤ȥ󥳡ɤܤ)ȥץΥåΥ
(ܺɽ⡼)
.I fp@informatik.uni-frankfurt.de
뤳ȡ
.PP
.\"0 The checksums found in
.\"0 .I BinHex
.\"0 data are currently ignored.
ߤ
.I BinHex
ǡäƤå̵뤵롣
.PP
.\"0 The program cannot fully handle partial multipart messages (MIME-style
.\"0 multipart messages split over several mail messages). The individual
.\"0 parts are recognized and concatenated, and the embedded multipart
.\"0 message is "decoded" into a plain-text file, which must then be fed
.\"0 again to
.\"0 .I uudeview.
.\"0 Don't worry, these kinds of messages are rare.
Υץϡʬ䤵줿ޥѡȥå(ʣΥ᡼ʬ
줿 MIME Υޥѡȥå)˽뤳ȤǤ
ƥѡȤ̤ 1 ĤˤޤȤ졢˴ޤޤƤޥѡ
ȥåץ졼ƥȥեˡ֥ǥɡפ뤬Υե
Ƥ
.I uudeview
ϤʤФʤʤΤ褦ʥå¿ˤʤΤ
ۤɬפϤʤ