Andrew,
You don't need an official template. You just need one that works and passes
ID nits. NroffEdit comes with an nroff template that satisfies the ID nits
check.
I have just updated the NroffEdit tool with a new template that incorporates
the December 2009 boilerplate.
Downloads are available from:
http://aaa-sec.com/nroffedit/nroffedit/download.html
Just the empty nroff template is available here:
http://aaa-sec.com/pub/NroffEdit/empty.nroff
/Stefan
On 10-03-21 4:50 AM, "Masataka Ohta"
<mohta(_at_)necom830(_dot_)hpcl(_dot_)titech(_dot_)ac(_dot_)jp>
wrote:
Andrew Sullivan wrote:
I had, in the past year, two different DNSEXT participants send me
frustrated email because of the idnits checks. The people in question
were both long-time contributors to the IETF with perhaps
ideosyncratic toolchains. Neither of them was using xml2rfc, and
neither of them had well-maintained *roff templates that just did the
right thing.
While I recently spent a few extra hour editing nroff source, a
solution for those who are less familiar with nroff is to provide
an official nroff template.
Anyway, it's an issue caused by complex legal requirements and
the fundamental solution is to loosen the requirements at least
for IDs.
With regard to the subject, introduction of non-ASCII characters
will make the matter a lot worse.
Masataka Ohta
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf