OK, I understand what you say now.
All they have to do is to run it through NroffEdit once more after they
are done with their nroff editing.
They don't use NroffEdit as their main tool for nroff editing, but they do
have it and use it (at least last time I talked to them).
But agreed, NroffEdit can not maintain the ToC while the document is being
changed in another editor. That would be a tough one :)
/Stefan
On 11-03-17 4:42 PM, "Julian Reschke" <julian(_dot_)reschke(_at_)gmx(_dot_)de>
wrote:
On 17.03.2011 16:36, Martin Rex wrote:
Julian Reschke wrote:
the context of this was a discussion how to generate a ToC using NROFF.
My comment was regarding the claim that NRoffEdit somehow achieves
this;
it does not. It just does exactly what xml2rfc does: it paginates
itself
and adjusts the ToC accordingly. Once you feed the nroff output, be it
from NRoffEdit or xml2rfc, into a standard nroff process, it'll get
incorrect as soon as page breaks change.
The page break will NOT change. NRoffEdit produces the exact same
page breaks as "the standard nroff process".
Yes.
But it can only maintain the ToC as long as it is used.
The RFC Production Center, according to the xml2rfc SoW, does *not* use
NRoffEdit, but a standard nroff installation.
Once you export from NRoffEdit, and start changing page breaks, the ToC
will become incorrect.
If you say *inside* the tools (be it NRoffEdit or xml2rfc), there is no
such problem.
Best regards, Julian
_______________________________________________
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