Timwi-
Re the HTML for the TOC: Why don't you use ol and
li?
Because we need to do manual numbering anyway, to keep the numbers
consistent with those used by the auto-numbering for headers (which is a
user preference). Also, it was easier to get all the margins right and
avoid unnecessary whitespace this way.
Feel free to play around this with Skin.php, but please realize these two
requirements. There should be no indentation on the first level, and no
margin above or below the list items; the numbers must be the same and in
the same format as in the headlines. I think that's a pointless exercise,
because the current solution works fine and probably takes less space.
And why do you need two nested tables?
That's an ugly hack to accomplish a thin border without using CSS. It
works in all browsers I've tested, though, since it relies on very basic
table properties. I've experimented with replacing the whole table with a
<DIV> yesterday, but that didn't work as desired; the border did not auto-
expand. I could either specify a min/max width, or it would take up 100%
of the screen. That's not acceptable. There's a commented version of my
last variant in Skin.php.
I've also played around with floating the table, but that takes a lot of
screen real estate, and will not work well with all but the highest
resolution when there's also an image. Given that not all users will
enable the toc, this would make testing if the image width is too high
quite tricky.
Regards,
Erik