Eric Rescorla <e...@rtfm.com> wrote:
>> I think it would be helpful for the authors, though, for the RPC to make
>> the formatting updates in the markdown (e.g., changing a bulleted list
>> to a definition list) after the copy edits so that the authors can keep
>> their markdown aligned, then the RPC creates the RFCXML file at the end
>> of the process.
> FWIW, I would call this specific example a copy-edit, and argue
> that it should go in the first pass, and I definitely agree it should
> go in the markdown.
What would also help would be if everyone started every new sentence on a
newline. It doesn't matter if they wrap the sentence into multiple lines,
but having a new sentence on a newline simplies git diff.
I wonder how to socialize this wider. Maybe it's worth a three minute
plenary talk, but my guess is that the people we want to reach don't come to
the plenary.
Were it me, I'd do a commit where I *just* wrapped things.
> Obviously, these lines are going to be a bit blurry, but I think if
> we can agree on the general concept, we'll be in a much better
> place.
Agreed.
I'm really excited by this change.
--
Michael Richardson <mcr+i...@sandelman.ca> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ rfc-interest mailing list -- rfc-interest@rfc-editor.org To unsubscribe send an email to rfc-interest-le...@rfc-editor.org
