[rfc-i] Making life easy for authors/editors

Andrew G. Malis agmalis at gmail.com
Sun Jul 8 05:26:46 PDT 2012


In fact, I do. I've never had to do any direct changes to the nroff
file, you can just work in the right-hand window. it's true that you
see the nroff, but you don't even need that.

But again, my point is that whatever format ends up being used for
drafts and RFCs, we will need tools so that naive (in this respect)
authors can easily write drafts without a steep learning curve.
Otherwise you'll be turning away potential authors and IETF


On Sun, Jul 8, 2012 at 3:49 AM, Julian Reschke <julian.reschke at gmx.de> wrote:
> On 2012-07-07 23:07, Andrew G. Malis wrote:
>> Tim,
>> The output is a usual Internet-draft text file formatted for nits
>> checking and submitting via the tools page. But reading drafts isn't
>> the focus of the tool, it's easily writing them.
>> The point of my email is that whatever metalanguage is chosen in the
>> future as the internal/normative/canonical format for drafts and RFCs,
>> there needs to be easily obtainable and maintained tools that allow
>> people that have no knowledge of the metalanguage to easily write
>> their documents, preferably via a WSIWYG editor.
>> Cheers,
>> Andy
> And you believe that NRoffEdit works for people with *no* knowledge of
> Nroff?
> Best regards, Julian

More information about the rfc-interest mailing list