Improve these comments a bit.

[nmh] / man / mhbuild.man

diff --git a/man/mhbuild.man b/man/mhbuild.man
index 3d2fbbaf1ef1c762329a1acb468dd10b28ba1957..b95c79482c3df93441c004b5165c9c656551c7de 100644 (file)
--- a/man/mhbuild.man
+++ b/man/mhbuild.man
@@ -1,4 +1,4 @@
-.TH MHBUILD %manext1% "December 14, 2014" "%nmhversion%"
+.TH MHBUILD %manext1% "September 23, 2016" "%nmhversion%"

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


@@ -765,14 +765,19 @@ switch will indicate which algorithm to use when encoding any message headers
 that contain 8\-bit characters.
 The valid arguments are
 .I base64
 that contain 8\-bit characters.
 The valid arguments are
 .I base64

-for based\-64 encoding and
+for base\-64 encoding,

 .I quoted
 .I quoted

-for quoted\-printable encoding.
+for quoted\-printable encoding, and
+.I utf\-8
+which requires that all 8\-bit header field bodies be encoded as UTF\-8
+(RFC 6530) and that the message be sent to a SMTP server that supports
+SMTPUTF8 (RFC 6531).

 The
 .B \-autoheaderencoding
 The
 .B \-autoheaderencoding

-switch will instruct
+switch instructs

 .B mhbuild
 .B mhbuild

-to automatically pick the algorithm that results in a shorter encoded string.
+to automatically pick the encoding, either base64 or quoted\-printable,
+that results in a shorter encoded string.

 .PP
 Putting this all together,
 here is an example of a more complicated message draft.
 .PP
 Putting this all together,
 here is an example of a more complicated message draft.


@@ -826,7 +831,7 @@ the
 switch, then
 .B mhbuild
 will encode each content with
 switch, then
 .B mhbuild
 will encode each content with

-a transfer encoding, even it the content contains only 7\-bit data.
+a transfer encoding, even if the content contains only 7\-bit data.

 This
 is to increase the likelihood that the content is not changed while in
 transport.
 This
 is to increase the likelihood that the content is not changed while in
 transport.


@@ -1038,25 +1043,31 @@ Template for composing contents.
 .IR mhstore (1)
 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"
 .IR mhstore (1)
 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"

-(RFC 2045),
+(RFC 2045)

 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types"
 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types"

-(RFC 2046),
+(RFC 2046)

 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part Three: Message Header Extensions for Non-ASCII Text"
 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part Three: Message Header Extensions for Non-ASCII Text"

-(RFC 2047),
+(RFC 2047)

 .PP
 .I "MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations"
 (RFC 2231)
 .PP
 .I "Proposed Standard for Message Encapsulation"
 .PP
 .I "MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations"
 (RFC 2231)
 .PP
 .I "Proposed Standard for Message Encapsulation"

-(RFC 934),
+(RFC 934)

 .PP
 .I "The Content-MD5 Header Field"
 .PP
 .I "The Content-MD5 Header Field"

-(RFC 1864),
+(RFC 1864)

 .PP
 .I "Definition of the URL MIME External-Body Access-Type"
 .PP
 .I "Definition of the URL MIME External-Body Access-Type"

-(RFC 2017),
+(RFC 2017)
+.PP
+.I "Overview and Framework for Internationalized Email"
+(RFC 6530)
+.PP
+.I "SMTP Extension for Internationalized Email"
+(RFC 6531)

 .SH DEFAULTS
 .nf
 \-autoheaderencoding
 .SH DEFAULTS
 .nf
 \-autoheaderencoding