Re: [Docstring-develop] Contents problems

[David G. <go...@us...>]

Richard Jones wrote:
> I've just snapped four screenshots of the latest table of contents efforts. I
> believe this is a simple stylesheet issue. These shots may be viewed at
> http://mechanicalcat.net/temp/.

> Yep, it's the::
> 
>   div.contents li {
>     margin-top: -20px }
> 
> that's doing it.

Yes, I suspected it would break. I was trying to get "compact" list behavior
using CSS, but it seems difficult. Unless I'm missing something obvious? I
tried using "margin-top: -2em", which should be proportional to the text
size, but when I changed text sizes in IE, it screwed up. IE seems to add a
fixed amount of margin per list item. But Netscape is different. And the
other examples bear this out.

Easy to see why people use tables for layout. Or graphics.

CSS level 1 and HTML 4.01 "strict" are not sufficiently flexible; CSS1
doesn't provide what the "strict.dtd" takes away. But CSS level 2 is not
supported well enough yet. We'll have to use "loose" HTML with more
hard-coded attributes. Unfortunate. Any other options? I'm no HTML expert;
advice welcome.

As for the "links" output, it seems to be broken ("<P>" inside "<LI>" forces
a newline perhaps?). The "lynx" contents output looks good though (but the
docinfo table is screwed up).

> If I render the page with the stylesheet from about two weeks ago (attached)
> it's OK...
> 
> - shot_konqi_ok.png

At that time, there was no specific support for contents at all. It seems
Konqueror doesn't add much margin/padding to list items at all.

All this browser-fiddling is outside my expertise and interest. Anybody want
to take it on?

-- 
David Goodger    go...@us...    Open-source projects:
 - Python Docstring Processing System: http://docstring.sourceforge.net
 - reStructuredText: http://structuredtext.sourceforge.net
 - The Go Tools Project: http://gotools.sourceforge.net