Re: [xml2rfc-dev] [Ext] xml2rfc: use of <boilerplate> in preptool step

[Henrik Levkowetz <[e-mail]>]

Hi Paul,

On 2019-10-09 18:47, Paul Hoffman wrote:
> On 10/9/19 9:14 AM, Julian Reschke wrote:
>> On 09.10.2019 17:47, Heather Flanagan wrote:
>>> ...
>>> Hi -
>>>
>>> Is there any reason not to create a separate <toc> element that would live in <front>?
>>>
>>> -Heather
>>> ...
>> 
>> That would be better, as it wouldn't conflate things with <boilerplate>.
>> 
>> That said, I still don't get why the Table of Contents needs to be part
>> of the canonical XML. I understand why it's desirable to be present in
>> an intermediate representation before rendering, but that doesn't mean
>> it needs to leak out into the canonical format.
> 
> +1 to Julian's comment. That's one reason why the design team chose
> not to put it in the XML at all. Another reason is that people
> writing XML might think that they can edit the elements of <toc> and
> have those edits remain through the publication cycle.
> 
> The design in the RFCs describing v3 has the tables only being
> created during HTML / text / PDF / whatever output. This means that
> the TOC for HTML doesn't have page numbers, but the TOC for text and
> PDF can have the appropriate page numbers.

The XML currently generated for the ToC is used as-is to generate entries
with page numbers for paginated text, and without them for other formats.
No conflict.


	Henrik