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

Julian Reschke julian.reschke at gmx.de
Wed Mar 12 11:08:05 PDT 2014


On 2014-03-12 19:03, Nico Williams wrote:
> On Wed, Mar 12, 2014 at 12:58 PM, Julian Reschke <julian.reschke at gmx.de> wrote:
>> On 2014-03-12 18:12, Nico Williams wrote:
>>>
>>> On Wed, Mar 12, 2014 at 12:04 PM, Julian Reschke <julian.reschke at gmx.de>
>>> wrote:
>>>>
>>>> On 2014-03-12 17:58, Paul Hoffman wrote:
>>>>>
>>>>> So, either fix 3.2 to say "one blank space", or modify Section 1 to say
>>>>> that CMOS isn't always followed when because.
>>>>> ...
>>>>
>>>>
>>>>
>>>> And furthermore, that would be a rule just for plain text output. Right?
>>>
>>>
>>> A resolution that may make the fewest people unhappy might be to say
>>> "two spaces" for the plain text rendering, and "a single wide or
>>> proportional space" in renderings that either use a larger repertoire
>>> of Unicode codepoints proportional-width fonts, respectively.
>>
>>
>> Remember that the tool needs to apply heuristics to detect where a sentence
>> ends. I'd rather get rid of this; if nobody except us is doing it, maybe
>> it's not needed?
>
> Oh, right.  Sorry.  _I_ will use two spaces in my sources then (well,
> I already do).  The RFC-Editor can remove them later, and/or xml2rfc
> can add heuristics to coalesce them into one as needed.

It will anyway, because <t> (and friends) are elements with ignorable 
whitespace.

Best regards, Julian



More information about the rfc-interest mailing list