It would be nice to have the option to include bullet points at lower levels of a TableOfContents

At the moment it is only possible to list a TableOfContents as a numbered list. In a document with a number of level two sections, each of which is split into 2 or 3 level three sections, this looks very busy, and in certain contexts IMHO is not particularly natural, given that the level three sections are quite low level headings. It would be very nice to have the possiblility to list the TableOfContents as numbered chapters, subdivided into bullet pointed sub-sections, like this:

1. Firstsection

   • First sub section

   • Second sub section

2. Second section

   • This starting to annoy

   • No more

3. Last Section

   • First and last sub section

A helpful alternative would be to have the subsections at least recognise that they are children of the parent sections, like this:

1. Firstsection

   • 1.1 First sub section

     1.2 Second sub section

2. Second section

   • 2.1 This starting to annoy

     2.2 No more

3. Last Section

   • 3.1 First and last sub section

https://wiki.ubuntu.com/UserDocumentation is the document which I thought this feature would help a lot with, but I believe it would be useful in general.

In my opinion this feature, if implemented, should be able to apply regardless of which levels of headings the author of a page chooses to use. So:

= First Chapter =
== Subheading ==

would have the same table of contents as:

== First Chapter ==
=== Subheading ===

I hope I've made myself clear

thanks for your attention,

Matt

Discussion

The first idea, mix of numbers and bullets, don't convince me. Unless its a convention in publishing, moin should not use this. If its really needed 3rd party can implement it. We have to make sure its easy to replace the toc macro with one that use different rendering. I think this can be done with CSS only.

The second idea, use correct numbers for child elements, make sense, and is a convention, and other people want this also. I vote for it in next release.

The last, I'm not sure. We should not try to be too smart about headings. There is no reason to use == first heading == when you can use = first heading =. If the problem is the design, it should be handled by the site theme. -- NirSoffer 2005-07-18 09:58:55

With regard to the first idea, I wasn't suggesting that moin always use it, but that the possibility be available as well as what currently happens.

Thanks for approval of the second idea.

WRT the last, the reason I use == first heading == and === second heading === a lot on the Ubuntu wiki is that this results in the main sections being divided by lines, where the subsections are not. I don't know if this is to do with the theme of the site, or just the way its done in Moin. -- MatthewEast

I also would appreciate the 2nd idea. The existing counting scheme is awful -- -- PatrickCervicek 2008-04-14 13:56:05

• Any ideas how this wish can be implemented in html? -- ReimarBauer 2008-04-14 19:11:43

  • Yes, with the CSS-Property "counter-increment".

    Have a look to this example and look to the source code.

    • Very nice. At least for sane browsers (works on FF2). On how many browsers is that currently unimplemented or broken? -- ThomasWaldmann 2008-04-14 21:41:16

      • It doesn't work with IE7 Here is an Legend which browser supports 'counter-increment'.

        • So this means, one has to implement it in phyton or javascript...-- PatrickCervicek 2008-04-17 15:31:37

CategoryFeatureRequest