This one is difficult, because it is not part of html, however I'll request it anyway. Suppose I have a numbered list.

1. item
   1. subitem
   2. subitem
2. item
   1. subitem
   2. subitem
3. item
4. item
   1. subitem
      1. subsubitem

Now, that's typical html.. all lists are unrelated, no subsection numbering. Ideally, there would be a way to subsection number, like this (done manually):

   1. item
      1.1. subitem
      1.2. subitem
   2. item
      2.1. subitem
      2.2. subitem
   3. item
   4. item
      4.1. subitem
         4.1.1. subsubitem

Note that, not only would subsection numbering be performed within a single list like the above, but also when spread throughout a document, where the next subsection enumeration would be used when at the same indent (outline) level (just like a normal word processor).

The reason I am requesting this is that I have been successful recently in online development/requirement document collaboration, where the resultant document ends up in ms-word, and the final result is distilled to *.pdf for internal publication. This sub-numbering is one of the only features I find missing to being able to genhtml directly to the *.pdf (also cross-references, but that's a whole 'nother story..). Currently I create the final ms-word doc by cutting & pasting the twiki topic text together; which is unfortunate, because it makes the online content stale (modifications to the word doc are not mirrored to the web & visa-versa).

Yes, there are ways to emulate this, by using seperate topics, and percent-include-percent.. but it is not the same.

-- TWikiGuest - 07 Jul 2002 (jcline at ieee.org)

Would you need that just as a TOC? In which case you will get it once NumberedHeadersAndLists is in the release.

-- PeterThoeny - 07 Jul 2002

This is desired as normal document markup.. not just for a TOC. One of the differentiators is resuming the prior numbering when the list has begun again:

   1. something
   
  a paragraph here.

      1.1 sub-something

  a paragraph here.

      1.2 sub-something

  'nother paragraph.

   2. something else

  a paragraph here.

      2.1 sub-something else

  paragraph here.

The numbers would be automatic, of course, but also these are used like headings, where ---++ and ---+++ would normally be used, as in the ---## examples. Basically I'm explaining a standard word processing 'outline' or 'section' feature.

Cross-reference implementation to a specific subsection might be some percent-CROSSREF('sub-something title')-percent feature, such that a paragraph can contain a crossreference (using the title as a key?):

   4.2
    a paragraph, to see the other paragraph like this one, see _Section 2.2_.

...where the 'Section 2.2' text is inserted (and hyperlinked) to the anchor of that bullet number..

Yes, this is related to AutomaticallyNumberedHeadings and NumberedHeadersAndLists but not exactly the same?

Now, with all of that, if there were the ability to enumerate different types of things, i.e.:

• headings
• images
• tables
• links

for example,

 1. heading (in h1)

  paragraph here

 1.1 sub heading (in h2)

  paragraph here

 1.2 sub heading (in h2)

  paragraph here

   (image here)
   figure 1.2-1: "caption" (in some style)

  paragraph here

   (image here)
   figure 1.2-2: "caption" (in some style)

   (table here)
   table 1.2-1: "caption" (in some style)

  paragraph here, with crossrefs to both figures and tables and heading-sections

 2 major heading (in h1 style)

  (table here)
   table 2-1: "caption" (in some style)

  paragraph here, i.e. "as shown in CROSSREF('mytable2') blah, 
and in CROSSREF('myfigure2') blah" is rendered as: "as shown in 
table 2-1 blah, and in figure 1.2-2 blah", with links 
appropriately anchored.

then you have just nearly replaced wysywig editors completely.. and everything is wiki..

Thanks,

-- TWikiGuest - 07 Jul 2002 (jcline at ieee.org)

Just a comment on the cross-referencing thing. I would highly recommend not using the actual numbers in cross references. Too often the section numbering will change, which would corrupt the cross references. Much better to use #SectionName then use [[#SectionName][Section Title]] for the link.

But it would be nice for a variable to automatically generate the nearest heading and generate a more descriptive link. Something like %SECTIONLINK{"SectionName" format="See section %o, \"%t\"."}%.

-- GladeDiviney - 08 Jul 2002