Re: Space after colon - text requested

"Charles Lindsey" <[email protected]>
Newsgroups gmane.ietf.rfc822
Message-ID <[email protected]>
In <[email protected]> Mark Martinec <[email protected]> writes:

>Here is my attempt:

A bit wordy, and not quite correct, so some emendations below:

>> 3.6.  Field definitions
>>
>>  The header fields of a message are defined here.  All header fields
>>  have the same general syntactic structure: A field name, followed by
>>  a colon, followed by the field body.  The specific syntax for each
>>  header field is defined in the subsequent sections.
>>
>>     Note: In the ABNF syntax for each field in subsequent sections,
>>     each field name is followed by the required colon.  However, for
>>     brevity sometimes the colon is not referred to in the textual
>>     description of the syntax.  It is, nonetheless, required.

>      Note: all structured and unstructured header field bodies defined
>      in this document allow an optional WSP as their first character.
>      It became a customary practice to place one SP there. Some other
>      protocols such as Netnews require such a SP, ...
                                ^
               [USEFOR (or RFC1036 at a pinch)], including NNTP [RFC3977],

>      ........ so a gateway needs
>      to modify header fields which do not conform to that stricter
>      specification. ..........
                  ^^^^^^^^^^^^^^^^^^^^^^^^^
       ... and gateways cannot be relied upon to insert it .....

>      ....... Moreover, some popular electronic mail message
>      transportation programs like to modify header fields to conform to
>      their idea of a pretty header field. Such necessary or frivolous
>      transformations can be detected by recipients and may rise suspicion
>      about message integrity or authenticity. ......
                  ^^^^^^^^^^^^^^^^^^^^^^^^^
       [I would be happy to omit that bit, but it does no harm]

>      ...... Continuance of the practice
>      by implementors to place one SP at the beginning of newly generated
>      header field bodies is encouraged in order to facilitate
>      interoperability.
+1

>>  It is important to note that the header fields are not guaranteed to
>>  be in a particular order.  ...

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133   Web: http://www.cs.man.ac.uk/~chl
Email: [email protected]      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.