|> 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
- include the missing intermediate levels
A warning should be emitted anyway.
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.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||