.IR content ]
\&...
.RB [ \-verbose " | " \-noverbose ]
-.RB [ \-version ]
+.RB [ \-Version ]
.RB [ \-help ]
.ad
.SH DESCRIPTION
.PP
A one-line banner is displayed above the listing.
The size of the
-\*(lqnative\*(rq (decoded) format of each content is evaluated.
+`native' (decoded) format of each content is evaluated.
This provides an accurate count at the expense of a small delay.
If the
.B \-verbose
switch is present, then the listing will show
-any \*(lqextra\*(rq information that is present in the message,
-such as comments in the \*(lqContent-Type\*(rq header.
+any `extra' information that is present in the message,
+such as comments in the `Content-Type' header.
.PP
The option
.B \-file
.B mhlist
to use the specified
file as the source message, rather than a message from a folder.
-If you specify this file as \*(lq-\*(rq, then
+If you specify this file as `-', then
.B mhlist
will
accept the source message on the standard input. Note that the
switch will not prevent the content from being acted upon.
.PP
A content specification consists of a content type and a subtype.
-The initial list of \*(lqstandard\*(rq content types and subtypes can
+The initial list of `standard' content types and subtypes can
be found in RFC\-2046.
.PP
A list of commonly used contents is briefly reproduced here:
A legal MIME message must contain a subtype specification.
.PP
To specify a content, regardless of its subtype, just use the
-name of the content, e.g., \*(lqaudio\*(rq. To specify a specific
-subtype, separate the two with a slash, e.g., \*(lqaudio/basic\*(rq.
+name of the content, e.g., `audio'. To specify a specific
+subtype, separate the two with a slash, e.g., `audio/basic'.
Note that regardless of the values given to the
.B \-type
switch, a
.SH DEFAULTS
.nf
.RB ` +folder "' defaults to the current folder"
-.RB ` msgs "' defaults to cur"
+.RB ` msgs "' defaults to the current message"
.RB ` \-noverbose '
.fi