[rfc-i] Call for Review of draft-iab-styleguide-01.txt, "RFC Style Guide"

George, Wes wesley.george at twcable.com
Tue Mar 18 11:48:32 PDT 2014

I’ve noted this issue several times, and suggested that perhaps this is
another of the areas where we agree that there is no consensus on which is
“correct", and instead agree that both forms are acceptable as long as the
source document is internally consistent, similar to the guidance we give
on American vs UK English spelling. If the RSE chooses to standardize
(standardise?) on one format in document production of canonical or
derivative forms, that’s a completely separate discussion.

Wes George

On 3/12/14, 12:58 PM, "Paul Hoffman" <paul.hoffman at vpnc.org> wrote:

>I wrote that last message while not in my office, so I could not get to
>my copy of the CMOS. Now that I'm here, I'll throw in one more desired
>change. And, yes: http://xkcd.com/1285/
>Section 1 says:
>   The RFC Editor generally follows these accepted
>   rules as defined by the Chicago Manual of Style (CMOS) [CMOS], with a
>   few important exceptions to avoid ambiguity in complex technical
>   prose and to handle mixtures of text and computer languages.
>Section 3.2 says:
>   *  When a sentence ended by a period is immediately followed by
>      another sentence, there should be two blank spaces after the
>      period.
>And yet the CMOS (rule 2.12) says:
>   A single character space, not two spaces, should be left after periods
>   the ends of sentences (both in manuscripts and in final, published
>   and after colons.
>So, either fix 3.2 to say "one blank space", or modify Section 1 to say
>that CMOS isn't always followed when because.
>--Paul Hoffman
>rfc-interest mailing list
>rfc-interest at rfc-editor.org

This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.

More information about the rfc-interest mailing list