Re: [new exporter] [html] Tables of Contents

[Jambunathan K <kjambunathan@gmail.com>]

Jambunathan K <kjambunathan@gmail.com> writes:

>>> This gives a significant advantage in that authors can link to the
>>> various instances just by knowing their own usage.  For instance, if
>>> they provided a top-level toc at the beginning of their book, and a
>>> deeper-level toc later on, they could link to each separately by id by
>>> knowing this plan.
>>
>> This seems like a valid use-case.  
>
> Brainstorimg here: Why not export a subtree (with displaced section
> numbers) and splice the exported strings together to produce the
> compelete document.
>
> Subtree export of headline 1, but with section numbers starting at 1.
> Subtree export of headline 2, but with section numbers starting at 2.
> Splice them together.

Considering that HTML exporter can export a subtree, I believe you can
do some XSLT magic so that the individual HTML generated by Org is
transformed before being spliced.

Do you really want this to be supported within the scope of the Org
exporter?  Are you sure you have explored all the tricks in your bag
before raising this request.  Just wanted to confirm, because you seem
to be the HTML expert among the three of us...

> ----------------------------------------------------------------
>
> There are books where each chapter could be written by different
> authors.  The chapters are later spliced together to produce the master
> document.  In case of OpenDocument, such files have *.odm extension.  I
> can look up what the OpenDocument spec says or LibreOffice does.
>
> ----------------------------------------------------------------

Or

Allow a subtree to take EXPORT_TOC property.  (There should be a way to
specifiy where this TOC will end up in - beginning of that chapter or
end of the chapter)

Similarly, one could introduce EXPORT_ENDNOTES property whereby each
chapter can have it's own self-contained "End Notes section".