Removed hyphen from all occurrences of RFC-*.

diff --git a/man/anno.man b/man/anno.man
index d96620dc0d17d1fe23e715e65ccc3776835dc930..311e109075851f6130a0c77367548d0942370825 100644 (file)
--- a/man/anno.man
+++ b/man/anno.man
@@ -32,7 +32,7 @@ manipulates header fields or
 .I annotations
 in messages.
 Header fields consist of a field name and an optional field body
 .I annotations
 in messages.
 Header fields consist of a field name and an optional field body

-as defined by RFC-2822.
+as defined by RFC 2822.

 The
 .B -component
 option specifies the field name, and the
 The
 .B -component
 option specifies the field name, and the

diff --git a/man/ap.man b/man/ap.man
index b72878991e7eecac570a3e9a6ae1d9be21b9fd39..cc5575c815db452c1f7cfdabd330fd56907f1409 100644 (file)
--- a/man/ap.man
+++ b/man/ap.man
@@ -93,7 +93,7 @@ None
 .PP
 .I
 Standard for the Format of ARPA Internet Text Messages
 .PP
 .I
 Standard for the Format of ARPA Internet Text Messages

-(RFC\-822)
+(RFC 822)

 .SH DEFAULTS
 .PD 0
 .TP 20
 .SH DEFAULTS
 .PD 0
 .TP 20

diff --git a/man/burst.man b/man/burst.man
index 2ef0975c44f6d81acacb508752f20ab5487b7e37..3f14bdc47ffb97c26d99d69ca36eb1dd999e2c52 100644 (file)
--- a/man/burst.man
+++ b/man/burst.man
@@ -50,7 +50,7 @@ switch can be used to enforce the use of MIME formatting. The
 .B \-nomime
 switch will force
 .B burst
 .B \-nomime
 switch will force
 .B burst

-to use RFC-934 rules.
+to use RFC 934 rules.

 .PP
 The
 .B \-quiet
 .PP
 The
 .B \-quiet


@@ -97,7 +97,7 @@ To set mode when creating a new message.
 .PP
 .I
 Proposed Standard for Message Encapsulation
 .PP
 .I
 Proposed Standard for Message Encapsulation

-(RFC\-934)
+(RFC 934)

 .SH DEFAULTS
 .PD 0
 .TP 20
 .SH DEFAULTS
 .PD 0
 .TP 20

diff --git a/man/dist.man b/man/dist.man
index e217f418e3854202242129ddea4fbbd2cd025444..4675b2c5e4872ca4e1e4945d7094b28bd5ae3d13 100644 (file)
--- a/man/dist.man
+++ b/man/dist.man
@@ -253,7 +253,7 @@ originally used headers of the form
 .RI \*(lq Distribute\-xxx: \*(rq
 instead of
 .RI \*(lq Resent\-xxx: \*(rq.
 .RI \*(lq Distribute\-xxx: \*(rq
 instead of
 .RI \*(lq Resent\-xxx: \*(rq.

-In order to conform with the ARPA Internet standard, RFC\-822, the
+In order to conform with the ARPA Internet standard, RFC 822, the

 .RI \*(lq Resent\-xxx: \*(rq
 form is now used.
 .B Dist
 .RI \*(lq Resent\-xxx: \*(rq
 form is now used.
 .B Dist

diff --git a/man/dp.man b/man/dp.man
index 7a319ecc05fc1bc48382a5ee68a15bf4257ee052..9a3bfb2a27016f8566d7622dcd2737942dd3ae28 100644 (file)
--- a/man/dp.man
+++ b/man/dp.man
@@ -71,7 +71,7 @@ None
 .IR ap (8),
 .PP
 .I "Standard for the Format of ARPA Internet Text Messages"
 .IR ap (8),
 .PP
 .I "Standard for the Format of ARPA Internet Text Messages"

-(RFC\-822)
+(RFC 822)

 .SH DEFAULTS
 .PD 0
 .TP 20
 .SH DEFAULTS
 .PD 0
 .TP 20

diff --git a/man/fmttest.man b/man/fmttest.man
index 5265f0473dc8ded116733e79c038e8708ad04bbb..59626da3ef1361e269ba7219139bb855e421c67e 100644 (file)
--- a/man/fmttest.man
+++ b/man/fmttest.man
@@ -297,8 +297,8 @@ STRLITZ     Like \fBSTRLIT\fR, but not counted against width
 LS_COMP        Write component to \fIstr\fR register
 LS_LIT Write literal to \fIstr\fR register
 LS_GETENV      Write environment var to \fIstr\fR register
 LS_COMP        Write component to \fIstr\fR register
 LS_LIT Write literal to \fIstr\fR register
 LS_GETENV      Write environment var to \fIstr\fR register

-LS_DECODECOMP  Decode RFC-2047 encoded component to \fIstr\fR register
-LS_DECODE      Decode RFC-2047 encoded string to \fIstr\fR register
+LS_DECODECOMP  Decode RFC 2047 encoded component to \fIstr\fR register
+LS_DECODE      Decode RFC 2047 encoded string to \fIstr\fR register

 LS_TRIM                Trim trailing whitespace from \fIstr\fR register
 LV_COMP                Convert component to integer, store in \fInum\fR register
 LV_COMPFLAG    Set \fInum\fR to 1 if \fBTRUE\fR set in component
 LS_TRIM                Trim trailing whitespace from \fIstr\fR register
 LV_COMP                Convert component to integer, store in \fInum\fR register
 LV_COMPFLAG    Set \fInum\fR to 1 if \fBTRUE\fR set in component


@@ -315,7 +315,7 @@ LS_LMONTH   Write long name of month to \fIstr\fR from date component
 LS_ZONE                Write time zone offset to \fIstr\fR from date component
 LS_DAY         Write short name of day of week to \fIstr\fR from date component
 LS_WEEKDAY     Write long name of day of week to \fIstr\fR from date component
 LS_ZONE                Write time zone offset to \fIstr\fR from date component
 LS_DAY         Write short name of day of week to \fIstr\fR from date component
 LS_WEEKDAY     Write long name of day of week to \fIstr\fR from date component

-LS_822DATE     Write RFC-822 compatible date to \fIstr\fR from date component
+LS_822DATE     Write RFC 822 compatible date to \fIstr\fR from date component

 LS_PRETTY      Write date with \*(lqpretty\*(rq timezone to \fIstr\fR
 LV_SEC Write date component seconds to \fInum\fR
 LV_MIN Write date component minutes to \fInum\fR
 LS_PRETTY      Write date with \*(lqpretty\*(rq timezone to \fIstr\fR
 LV_SEC Write date component seconds to \fInum\fR
 LV_MIN Write date component minutes to \fInum\fR


@@ -337,9 +337,9 @@ LS_HOST     Write host of addr component to \fIstr\fR
 LS_PATH        Write host route of addr component to \fIstr\fR
 LS_GNAME       Write group name of addr component to \fIstr\fR
 LS_NOTE        Write note portion of addr component to \fIstr\fR
 LS_PATH        Write host route of addr component to \fIstr\fR
 LS_GNAME       Write group name of addr component to \fIstr\fR
 LS_NOTE        Write note portion of addr component to \fIstr\fR

-LS_822ADDR     Write \*(lqproper\*(rq RFC-822 version of addr component to \fIstr\fR
+LS_822ADDR     Write \*(lqproper\*(rq RFC 822 version of addr component to \fIstr\fR

 LS_FRIENDLY    Write friendly (name or note) of address component to \fIstr\fR
 LS_FRIENDLY    Write friendly (name or note) of address component to \fIstr\fR

-LS_UNQUOTE     Remove RFC-2822 quotes from string
+LS_UNQUOTE     Remove RFC 2822 quotes from string

 LV_HOSTTYPE    Set \fInum\fR to type of host (0=local, 1=network)
 LV_INGRPF      Set \fInum\fR to 1 if address was inside of group
 LV_NOHOSTF     Set \fInum\fR to 1 of no host was present in address component
 LV_HOSTTYPE    Set \fInum\fR to type of host (0=local, 1=network)
 LV_INGRPF      Set \fInum\fR to 1 if address was inside of group
 LV_NOHOSTF     Set \fInum\fR to 1 of no host was present in address component

diff --git a/man/forw.man b/man/forw.man
index bf172f67c9a7c9f872fc88d193361794f79cad16..2b73408a5a542745064494a3c234bdd606fe9f87 100644 (file)
--- a/man/forw.man
+++ b/man/forw.man
@@ -250,7 +250,7 @@ By default, any dashes in the first column of the forwarded messages
 will be prepended with `\-\ ' so that when received, the message is
 suitable for bursting by
 .BR burst .
 will be prepended with `\-\ ' so that when received, the message is
 suitable for bursting by
 .BR burst .

-This follows the Internet RFC\-934 guidelines.  You may use the flag
+This follows the Internet RFC 934 guidelines.  You may use the flag

 .B \-nodashstuffing
 in order
 to suppress this form of quoting to the forwarded messages.
 .B \-nodashstuffing
 in order
 to suppress this form of quoting to the forwarded messages.


@@ -466,7 +466,7 @@ Program to ask the \*(lqWhat now?\*(rq questions.
 .PP
 .I
 Proposed Standard for Message Encapsulation
 .PP
 .I
 Proposed Standard for Message Encapsulation

-(RFC\-934)
+(RFC 934)

 .SH DEFAULTS
 .PD 0
 .TP 25
 .SH DEFAULTS
 .PD 0
 .TP 25

diff --git a/man/mh-folders.man b/man/mh-folders.man
index e6b1d442b3804a9e46e197f45292c76e238bc1a4..4b560e473c2f9adbf0ff57f3c897fc16002e810e 100644 (file)
--- a/man/mh-folders.man
+++ b/man/mh-folders.man
@@ -99,7 +99,7 @@ numbers in each sequence.  The
 sequence has at most just a single message number, not a range.
 .PP
 Sequence names have a maximum size of 998 characters.  Each line is also
 sequence has at most just a single message number, not a range.
 .PP
 Sequence names have a maximum size of 998 characters.  Each line is also

-limited to a maximum of 998 characters, but RFC\-822 continuation rules
+limited to a maximum of 998 characters, but RFC 822 continuation rules

 apply; sequences can be continued across multiple lines by prefixing
 continuation lines with a whitespace character.
 .PP
 apply; sequences can be continued across multiple lines by prefixing
 continuation lines with a whitespace character.
 .PP

diff --git a/man/mh-format.man b/man/mh-format.man
index 8dc7f169e5e9fbb96aa606619166faa3e2255d2c..83de220b0e3e63519e70ab72649959974768e229 100644 (file)
--- a/man/mh-format.man
+++ b/man/mh-format.man
@@ -285,10 +285,10 @@ void      expr            Set \fIstr\fR or \fInum\fR
 comp   comp    string  Set \fIstr\fR to component text
 compval        comp    integer Set \fInum\fR to \*(lq\fBatoi\fR(\fIcomp\fR\^)\*(rq
 .\" compflag   comp    integer Set \fInum\fR to component flags bits (internal)
 comp   comp    string  Set \fIstr\fR to component text
 compval        comp    integer Set \fInum\fR to \*(lq\fBatoi\fR(\fIcomp\fR\^)\*(rq
 .\" compflag   comp    integer Set \fInum\fR to component flags bits (internal)

-.\" decodecomp comp    string  Set \fIstr\fR to RFC-2047 decoded component text
-decode expr    string  decode \fIstr\fR as RFC-2047 (MIME-encoded) 
+.\" decodecomp comp    string  Set \fIstr\fR to RFC 2047 decoded component text
+decode expr    string  decode \fIstr\fR as RFC 2047 (MIME-encoded) 

                        component
                        component

-unquote        expr    string  remove RFC-2822 quotes from \fIstr\fR
+unquote        expr    string  remove RFC 2822 quotes from \fIstr\fR

 trim   expr            trim trailing whitespace from \fIstr\fR
 putstr expr            print \fIstr\fR
 putstrf        expr            print \fIstr\fR in a fixed width
 trim   expr            trim trailing whitespace from \fIstr\fR
 putstr expr            print \fIstr\fR
 putstrf        expr            print \fIstr\fR in a fixed width

diff --git a/man/mh-mail.man b/man/mh-mail.man
index b2a430cb4d8efa2c06e1cc0d5aeec7077a3f773d..d425fff508e45543be52d5585c24440405c27bf6 100644 (file)
--- a/man/mh-mail.man
+++ b/man/mh-mail.man
@@ -28,7 +28,7 @@ Messages are expected to consist of lines of text.  Graphics and binary
 data are not handled.  No data compression is accepted.  All text is
 clear ASCII 7-bit data.
 .PP
 data are not handled.  No data compression is accepted.  All text is
 clear ASCII 7-bit data.
 .PP

-The general \*(lqmemo\*(rq framework of RFC\-822 is used.  A message
+The general \*(lqmemo\*(rq framework of RFC 822 is used.  A message

 consists of a block of information in a rigid format, followed by
 general text with no specified format.  The rigidly formatted first
 part of a message is called the header, and the free-format portion is
 consists of a block of information in a rigid format, followed by
 general text with no specified format.  The rigidly formatted first
 part of a message is called the header, and the free-format portion is


@@ -56,7 +56,7 @@ are indicated by leading spaces or tabs.
 Each header item is called a component and is composed of a keyword or
 name, along with associated text.  The keyword begins at the left margin,
 may NOT contain spaces or tabs, may not exceed 63 characters (as specified
 Each header item is called a component and is composed of a keyword or
 name, along with associated text.  The keyword begins at the left margin,
 may NOT contain spaces or tabs, may not exceed 63 characters (as specified

-by RFC\-822), and is terminated by a colon (`:').  Certain components
+by RFC 822), and is terminated by a colon (`:').  Certain components

 (as identified by their keywords) must follow rigidly defined formats
 in their text portions.
 .PP
 (as identified by their keywords) must follow rigidly defined formats
 in their text portions.
 .PP


@@ -291,6 +291,6 @@ option.
 .SH "SEE ALSO"
 .I
 Standard for the Format of ARPA Internet Text Messages
 .SH "SEE ALSO"
 .I
 Standard for the Format of ARPA Internet Text Messages

-(RFC\-822)
+(RFC 822)

 .SH CONTEXT
 None
 .SH CONTEXT
 None

diff --git a/man/mh-profile.man b/man/mh-profile.man
index 4f3743c677c83a88802dfac9ebd631679d2f8d47..9f0190f56d89b06adbc64a90da324d6c5e214eb9 100644 (file)
--- a/man/mh-profile.man
+++ b/man/mh-profile.man
@@ -260,7 +260,7 @@ by the default component files by tools like
 and
 .B repl
 to construct your default \*(lqFrom\*(rq header.  The text used here will
 and
 .B repl
 to construct your default \*(lqFrom\*(rq header.  The text used here will

-be copied exactly to your From: header, so it should already be RFC-822
+be copied exactly to your From: header, so it should already be RFC 822

 compliant.  If this is set, the
 .B Signature
 profile entry is NOT used, so it should include a signature as well.  (profile,
 compliant.  If this is set, the
 .B Signature
 profile entry is NOT used, so it should include a signature as well.  (profile,


@@ -789,7 +789,7 @@ With this environment variable, you can specify
 the native character set you are using.  You must be able to display
 this character set on your terminal.
 .PP
 the native character set you are using.  You must be able to display
 this character set on your terminal.
 .PP

-This variable is checked to see if a RFC-2047 header field should be
+This variable is checked to see if a RFC 2047 header field should be

 decoded (in
 .BR inc ,
 .BR scan ,
 decoded (in
 .BR inc ,
 .BR scan ,

diff --git a/man/mh-tailor.man b/man/mh-tailor.man
index bf90eb21322c2695006e54654f24647657c292e1..af3076eaae91865656a9c6ee683ad98b8951733e 100644 (file)
--- a/man/mh-tailor.man
+++ b/man/mh-tailor.man
@@ -127,7 +127,7 @@ command will be given.
 .PP
 Although the
 .B HELO
 .PP
 Although the
 .B HELO

-command is required by RFC\-821, many SMTP servers
+command is required by RFC 821, many SMTP servers

 do not require it.  Early versions of
 .I SendMail
 will fail if the hostname
 do not require it.  Early versions of
 .I SendMail
 will fail if the hostname

diff --git a/man/mhbuild.man b/man/mhbuild.man
index 6510b12b545dcbdfa7a3680d856325737a9b37fc..ab757d3465dfff12089a562958e523aff01d202e 100644 (file)
--- a/man/mhbuild.man
+++ b/man/mhbuild.man
@@ -27,12 +27,12 @@ command will translate a MIME composition draft into
 a valid MIME message.
 .PP
 .B mhbuild
 a valid MIME message.
 .PP
 .B mhbuild

-creates multi-media messages as specified in RFC\-2045
-to RFC\-2049.  Currently
+creates multi-media messages as specified in RFC 2045
+to RFC 2049.  Currently

 .B mhbuild
 only supports encodings in
 message bodies, and does not support the encoding of message headers as
 .B mhbuild
 only supports encodings in
 message bodies, and does not support the encoding of message headers as

-specified in RFC\-2047.
+specified in RFC 2047.

 .PP
 If you specify the name of the composition file as \*(lq-\*(rq,
 then
 .PP
 If you specify the name of the composition file as \*(lq-\*(rq,
 then


@@ -281,7 +281,7 @@ would be as follows:
 .fi
 .RE
 .PP
 .fi
 .RE
 .PP

-Any long URLs will be wrapped according to RFC\-2017 rules.
+Any long URLs will be wrapped according to RFC 2017 rules.

 .PP
 The \*(lqmessage\*(rq directive (#forw) is used to specify a message or
 group of messages to include.  You may optionally specify the name of
 .PP
 The \*(lqmessage\*(rq directive (#forw) is used to specify a message or
 group of messages to include.  You may optionally specify the name of


@@ -291,7 +291,7 @@ given, it defaults to the current message.  Hence, the message directive
 is similar to the
 .B forw
 command, except that the former uses
 is similar to the
 .B forw
 command, except that the former uses

-the MIME rules for encapsulation rather than those specified in RFC\-934.
+the MIME rules for encapsulation rather than those specified in RFC 934.

 For example,
 .PP
 .RS 5
 For example,
 .PP
 .RS 5


@@ -314,8 +314,8 @@ switch.  This switch will indicate that
 .B mhbuild
 should attempt to utilize the MIME encapsulation rules
 in such a way that the \*(lqmultipart/digest\*(rq that is created
 .B mhbuild
 should attempt to utilize the MIME encapsulation rules
 in such a way that the \*(lqmultipart/digest\*(rq that is created

-is (mostly) compatible with the encapsulation specified in RFC\-934.
-If given, then RFC\-934 compliant user-agents should be able to burst the
+is (mostly) compatible with the encapsulation specified in RFC 934.
+If given, then RFC 934 compliant user-agents should be able to burst the

 message on reception\0--\0providing that the messages being encapsulated
 do not contain encapsulated messages themselves.  The drawback of this
 approach is that the encapsulations are generated by placing an extra
 message on reception\0--\0providing that the messages being encapsulated
 do not contain encapsulated messages themselves.  The drawback of this
 approach is that the encapsulations are generated by placing an extra


@@ -685,27 +685,27 @@ is checked.
 .IR mhstore (1)
 .PP
 .I "Proposed Standard for Message Encapsulation"
 .IR mhstore (1)
 .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 "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"
 .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 "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures"
 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures"

-(RFC\-2048),
+(RFC 2048),

 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples"
 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples"

-(RFC\-2049)
+(RFC 2049)

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

-(RRC\-2017)
+(RFC 2017)

 .SH DEFAULTS
 .nf
 .RB ` \-headers '
 .SH DEFAULTS
 .nf
 .RB ` \-headers '

diff --git a/man/mhfixmsg.man b/man/mhfixmsg.man
index 58f44e5ed71b2cd3c8a3a5f20b9c9a273b529d1e..629014d6c68470a6c5de46e0e0689e9766a45bf4 100644 (file)
--- a/man/mhfixmsg.man
+++ b/man/mhfixmsg.man
@@ -36,7 +36,7 @@ rewrites MIME messages, applying specific transformations such as
 decoding of MIME-encoded message parts and repairing invalid MIME
 headers.
 .PP
 decoding of MIME-encoded message parts and repairing invalid MIME
 headers.
 .PP

-MIME messages are specified in RFC\-2045 to RFC\-2049
+MIME messages are specified in RFC 2045 to RFC 2049

 (see
 .IR mhbuild (1)).
 The
 (see
 .IR mhbuild (1)).
 The


@@ -53,7 +53,7 @@ The
 switch enables a transformation to decode each base64 and
 quoted-printable text message part to the selected 8bit or 7bit
 encoding.  If 7bit is selected for a base64 part but it will only fit
 switch enables a transformation to decode each base64 and
 quoted-printable text message part to the selected 8bit or 7bit
 encoding.  If 7bit is selected for a base64 part but it will only fit

-8bit, as defined by RFC-2045, then it will be decoded to 8bit
+8bit, as defined by RFC 2045, then it will be decoded to 8bit

 quoted-printable.  Otherwise, if the decoded text would not fit the
 selected encoding, the part is not decoded (and a message will be
 displayed if
 quoted-printable.  Otherwise, if the decoded text would not fit the
 selected encoding, the part is not decoded (and a message will be
 displayed if

diff --git a/man/mhl.man b/man/mhl.man
index afa68bdb3af26959305674b2dbef9a0a14bf241d..824faddf679a9ae1c0e948032254409eab4e3e0b 100644 (file)
--- a/man/mhl.man
+++ b/man/mhl.man
@@ -249,7 +249,7 @@ newline     flag    print newline at end of components
 nonewline      flag    don't print newline at end of components
 formatfield    string  format string for this component
                (see below)
 nonewline      flag    don't print newline at end of components
 formatfield    string  format string for this component
                (see below)

-decode flag    decode text as RFC-2047 encoded
+decode flag    decode text as RFC 2047 encoded

                header field
 addrfield      flag    field contains addresses
 datefield      flag    field contains dates
                header field
 addrfield      flag    field contains addresses
 datefield      flag    field contains dates

diff --git a/man/mhlist.man b/man/mhlist.man
index d8241ae2997d351c65df57bdf26c816d7a8ee260..bd8f080207822fa0f326431f444f1c9b464a9bf0 100644 (file)
--- a/man/mhlist.man
+++ b/man/mhlist.man
@@ -38,7 +38,7 @@ MIME (multi-media) messages.
 .PP
 .B mhlist
 manipulates MIME (multi-media messages) as specified
 .PP
 .B mhlist
 manipulates MIME (multi-media messages) as specified

-in RFC\-2045 to RFC\-2049 (See
+in RFC 2045 to RFC 2049 (See

 .IR mhbuild (1)).
 .PP
 The
 .IR mhbuild (1)).
 .PP
 The


@@ -106,7 +106,7 @@ 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
 .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
 A list of commonly used contents is briefly reproduced here:
 .PP

diff --git a/man/mhshow.man b/man/mhshow.man
index 712d0a30cbffd46cb8fb0ea52b261a9c8418b720..f55fbfe6a4bf71ae2981df5ba049186b6bdb0d23 100644 (file)
--- a/man/mhshow.man
+++ b/man/mhshow.man
@@ -38,11 +38,11 @@ message or collection of messages.
 .PP
 .B mhshow
 manipulates multi-media messages as specified in
 .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
 .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
 By default
 .B mhshow


@@ -92,7 +92,7 @@ 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
 .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
 A list of commonly used contents is briefly reproduced here:
 .PP

diff --git a/man/mhstore.man b/man/mhstore.man
index f205482a7ade0fc3ccef5c6919fa596405cc2674..7e6f850651460577b33b368f5f12f10b4edf5124 100644 (file)
--- a/man/mhstore.man
+++ b/man/mhstore.man
@@ -40,7 +40,7 @@ messages.
 .PP
 .B mhstore
 manipulates multi-media messages as specified in
 .PP
 .B mhstore
 manipulates multi-media messages as specified in

-RFC\-2045 to RFC\-2049.
+RFC 2045 to RFC 2049.

 .PP
 By default,
 .B mhstore
 .PP
 By default,
 .B mhstore


@@ -93,7 +93,7 @@ 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
 .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.
+can be found in RFC 2046.

 .PP
 A list of commonly used contents is briefly reproduced here:
 .PP
 .PP
 A list of commonly used contents is briefly reproduced here:
 .PP

diff --git a/man/post.man b/man/post.man
index 24b63be9445654dc165fc3a13f269ce18f37b9ad..4d64300cc75ae57148faa3ecf48f1ec1ffb26558 100644 (file)
--- a/man/post.man
+++ b/man/post.man
@@ -273,7 +273,7 @@ consult the user's
 .IR mh\-tailor (5)
 .PP
 .I "Standard for the Format of ARPA Internet Text Messages"
 .IR mh\-tailor (5)
 .PP
 .I "Standard for the Format of ARPA Internet Text Messages"

-(RFC\-822)
+(RFC 822)

 .SH DEFAULTS
 .nf
 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
 .SH DEFAULTS
 .nf
 .RB ` \-alias "' defaults to %etcdir%/MailAliases"

diff --git a/man/prompter.man b/man/prompter.man
index 3796a29c3d603517beda091d1fabe0a6ef9b2c7a..9e3263ad7385caa9c1de037f8fc0d1fd1f69a866 100644 (file)
--- a/man/prompter.man
+++ b/man/prompter.man
@@ -26,7 +26,7 @@ is an editor front\-end for
 which allows rapid
 composition of messages.  This program is not normally invoked directly by
 users but takes the place of an editor and acts as an editor front\-end.
 which allows rapid
 composition of messages.  This program is not normally invoked directly by
 users but takes the place of an editor and acts as an editor front\-end.

-It operates on an RFC\-822 style message draft skeleton specified by
+It operates on an RFC 822 style message draft skeleton specified by

 .IR file ,
 normally provided by the
 .B nmh
 .IR file ,
 normally provided by the
 .B nmh

diff --git a/man/scan.man b/man/scan.man
index 7510505cdf7e07aef87d801eb2e81d6401c963d8..b9c94f48df0a63ef74c093fa92e4cf2d007221a5 100644 (file)
--- a/man/scan.man
+++ b/man/scan.man
@@ -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

diff --git a/man/sendfiles.man b/man/sendfiles.man
index d63234ea22dac14c30337ff8f6ec1034376c02d4..ba1fef0037266d2a2a1423008a92531663c95452 100644 (file)
--- a/man/sendfiles.man
+++ b/man/sendfiles.man
@@ -195,7 +195,7 @@ to perform the extraction.
 .IR mh-format (5)
 .PP
 .I "Proposed Standard for Message Encapsulation"
 .IR mh-format (5)
 .PP
 .I "Proposed Standard for Message Encapsulation"

-(RFC\-934)
+(RFC 934)

 .SH DEFAULTS
 .nf
 .RB ` "\-delay\ 0" '
 .SH DEFAULTS
 .nf
 .RB ` "\-delay\ 0" '