-.TH MHSHOW %manext1% "April 9, 2013" "%nmhversion%"
+.TH MHSHOW %manext1% "May 4, 2013" "%nmhversion%"
.\"
.\" %nmhwarning%
.\"
.PP
.B mhshow
manipulates multi-media messages as specified in
-RFC\-2045 to RFC\-2049. Currently
+RFC 2045 to RFC 2049. Currently
.B mhshow
only supports
encodings in message bodies, and does not support the encoding of
-message headers as specified in RFC\-2047.
+message headers as specified in RFC 2047.
.PP
By default
.B mhshow
.PP
A content specification consists of a content type and a subtype.
The initial list of \*(lqstandard\*(rq content types and subtypes can
-be found in RFC\-2046.
+be found in RFC 2046.
.PP
A list of commonly used contents is briefly reproduced here:
.PP
.PP
If a display string is not found,
.B mhshow
-has several default values:
+behaves as if these profile entries were supplied and supported:
.PP
.RS 5
.nf
.fi
.RE
.PP
+Note that \*(lqmoreproc\*(rq is not supported in user profile display
+strings.
+.PP
If a subtype of type text doesn't have a profile entry, it will be
treated as text/plain.
.PP
The program should terminate with an exit status of zero if the
retrieval is successful, and a non-zero exit status otherwise.
.PP
-For the \*(lqurl\*(rq access\-type,
+For the \*(lqurl\*(rq access\-type,
.B mhshow
will look for the \*(lqnmh-access-url\*(rq
profile entry. See