|The stupid question is the question not asked|
> FWIW, I didn't try dealing with header nesting because a lot of the HTML to be processed was very poorly written. If I had, the TOC would have looked haphazard.
actually I don't know yet how to deal best with wrong nesting.
E.g a h6 following a h4 would be ignored now (or added to the last h5 which is nonsense*)
I don't know if it's better to
Another nice to have would be to parse already available anchors, to allow multiple runs.
Again the problem arises if a new anchor should be generated or the last one taken.
I think all of this should be configurable, but so many options make this already a candidate for a proper module. ...
*) actually this explains weird problems I saw with latex beamer and wrong nesting. .. cool insight into alien code.