comment on

1. I'm not sure why you have different headings and TOC entries

why not simply

<h3>Chapter 1 - Basics: Para & Code markup</h3> for both?

2. Your anchors are manually designed too, while those generated by my script should be safe.

Whats the issue? Length?

The benefit of long anchors is that they could later be easily expanded to text again.

3. IMHO you should convert sub-headings to <h4> to get proper nesting. (like this )

4. Your example headings like <h6> can be excluded by either

5. See also the way I'm back-linking to the TOC here: Re^2: TOCs and deeplinks for our house rules to facilitate navigation

6. Also switching <ul> to <dl> is an option, if needed.²

I can adapt my script to different needs if the monastery comes to a consensus.

Long time goal could hopefully be to add something like <toc> to our markup toolset to simplify the process.

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)

Je suis Charlie!}

*) this has multiple advantages.

²) IMHO depends on desired CSS features

In reply to Re: TOC draft sample by LanX
in thread TOC draft sample by ww

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks