-.TH MH\-MIME %manext7% "March 16, 2014" "%nmhversion%"
-.\"
+.TH MH\-MIME %manext7% 2014-12-15 "%nmhversion%"
+.
.\" %nmhwarning%
-.\"
+.
.SH NAME
-mh\-mime \- Overview of
-.IR nmh (7)
-MIME message composition and display
+mh\-mime \- overview of nmh MIME message composition and display
.\"
.SH DESCRIPTION
The acronym MIME stands for Multipurpose Internet Mail Extensions, the
-format of Internet messages used to send multi\-media content.
+format of Internet messages used to send multi-media content.
The
.B nmh
command suite has support for the display and composition of MIME messages, but
Local Character Set Conversion
All of the
.B nmh
-commands convert non\-native character sets to the local character set,
+commands convert non-native character sets to the local character set,
as specified by the operating system locale settings. See
.IR locale (1)
for more details on the environment variables used to set the
.B nmh
was built with
.IR iconv (3)
-support. See the
+support. See
.IR mhparam (1)
-man page for how determine whether your
+for how to determine whether your
.B nmh
installation includes
.IR iconv (3)
support.
.PP
Depending on the source and target character set, it may not be possible
-to convert all characters to the local character set. In this case a
+to convert all characters to the local character set. In this case a
substitution character will be used for the characters that cannot be
converted.
.SS
.RI \*(lq %nmhetcdir% \*(rq
directory) and
.IR mh\-format (5)
-for details on how to make sure your MIME headers are properly
-decoded.
+for details on how to make sure your MIME headers are properly decoded.
.PP
By default, if
.B show
before being passed to
.IR post (1)
for message submission.
-.B Mhbuild
+.B mhbuild
will use the locale settings to mark text content with the appropriate
character set and apply any necessary encoding. If you wish to include
text in your message using a character set that does not match your
-locale, you will need to specify the character set using a
+locale, you will need to specify the character set using an
.B mhbuild
directive; see
.IR mhbuild (1)
for more information.
.PP
-For attaching files or composing other non-text content, there are two options: the attach system and
+For attaching files or composing other non-text content, there are two options:
+the attach system and
.B mhbuild
directives.
.PP
.B attach
command at the \*(lqWhat now?\*(rq prompt, or by inserting an \*(lqAttach:\*(rq
header in the message draft containing the name of the file you wish to
-attach to the message (it should be noted all that the
+attach to the message (note that all the
.B attach
-command does is place an \*(lqAttach\*(rq header in the message draft).
-.B Mhbuild
+command does is place an \*(lqAttach:\*(rq header in the message draft).
+.B mhbuild
will then automatically include the specified file(s) in the outgoing
message. See
.IR send (1)
When replying to messages using
.IR repl (1)
the traditional MH method of including the original text in the reply does
-not interoperate with MIME messages. As of this writing there is no
-native solution for addressing this issue, but the contrib directory
+not interoperate with MIME messages. The
+.B \-convertargs
+switch to
+.IR repl (1)
+provides one solution. Another solution: the contrib directory
.RI ( %docdir%/contrib )
contains a Perl program called
.B replyfilter
.SH "SEE ALSO"
.IR comp (1),
.IR iconv (3),
-.IR mh\-format (5)
+.IR mh\-format (5),
.IR mhbuild (1),
.IR mhfixmsg (1),
.IR mhparam (1),
.IR nmh (7),
.IR repl (1),
.IR whatnow (1),
-.PP
-.I %docdir%/contrib/replyfilter
+.br
+.IR %docdir%/contrib/replyfilter ,
+.br
+.I %docdir%/contrib/replaliases
.SH BUGS
MIME support should be more integrated into all of the
.B nmh