[rfc-i] Pagination requirements

Joe Touch touch at isi.edu
Wed May 23 17:36:01 PDT 2012

On 5/23/2012 4:43 PM, Martin Rex wrote:
> Currently, if you want to start authoring I-Ds with NO prior
> knowledge, there is the option of using NRoffEdit.  It understands
> a dozen very simple nroff commands that are sufficiently explained
> in the 2 page built-in help page.  And the NRoffEdit import function
> allows you to pick up an existing RFC txt or abandoned I-D txt file
> and convert it back into nroff authoring format.

You can also use the Word template and the on-line post-processor. That 
has IMO and even lower learning curve.

> Writing a tools backend that reflows existing rfcXXXX.txt and allows
> variable with fonts (something like a beefed-up rfcmarkup) should not
> be that hard.  Falling back to preformatted output for lines where it
> is unsure about reflowing should work with a lot of existing RFCs.

That's an interesting point - i.e., can the desired features of the HTML 
versions be gleaned from the .txt versions - which are dominant anyway 
(esp. for legacy).

> If this discussion is really about the consumers of the documents,
> then it would focus on making the _existing_ documents more "consumable"
> rather than on the desire of a handful of authors to support their
> rampant creativity with bleeding-edge complex technologies and a requirement
> for everybody else that they must follow suit.


More information about the rfc-interest mailing list