Getting closer to getting base64 header encoding working.

[nmh] / man / scan.man

diff --git a/man/scan.man b/man/scan.man
index 2d3d43cfacb5158db2341e403a34d70413dce5e7..b9c94f48df0a63ef74c093fa92e4cf2d007221a5 100644 (file)
--- a/man/scan.man
+++ b/man/scan.man
@@ -1,4 +1,4 @@
-.TH SCAN %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
+.TH SCAN %manext1% "November 6, 2012" "%nmhversion%"

 .\"
 .\" %nmhwarning%
 .\"
 .\"
 .\" %nmhwarning%
 .\"


@@ -68,7 +68,7 @@ produced if there are format errors in any of the messages.
 .PP
 By default,
 .B scan
 .PP
 By default,
 .B scan

-will decode RFC-2047 (MIME) encoding in
+will decode RFC 2047 (MIME) encoding in

 these scan listings.
 .B Scan
 will only decode these fields if your
 these scan listings.
 .B Scan
 will only decode these fields if your


@@ -189,6 +189,12 @@ modification of the message file itself.  This feature is handy for
 scanning a draft folder, as message drafts usually aren't allowed
 to have dates in them.
 .PP
 scanning a draft folder, as message drafts usually aren't allowed
 to have dates in them.
 .PP

+The
+.B %etcdir%
+directory contains several format files as examples of customized
+.B scan
+output.
+.PP

 .B scan
 will update the
 .B nmh
 .B scan
 will update the
 .B nmh


@@ -234,14 +240,6 @@ used to generate
 a heading saying what each column in the listing was.  Format strings
 prevent this from happening.
 .SH BUGS
 a heading saying what each column in the listing was.  Format strings
 prevent this from happening.
 .SH BUGS

-The argument to the
-.B \-format
-switch must be interpreted as a single
-token by the shell that invokes
-.BR scan .
-Therefore, one must usually
-place the argument to this switch inside quotes.
-.PP

 The value of each
 .I component
 escape is set by
 The value of each
 .I component
 escape is set by