[docbook-css] [ANN] Docbook CSS 0.3 Released

[David Holroyd]

On Mon, Oct 18, 2004 at 09:14:48PM +0100, martin.gautier@myrnham.co.uk wrote:
> Testing the <important>s on my Windows box throws up an issue for me.
> 
> important:before {
> /* way too dark to read text with purple background */
> /*      background-color: purple;                     */
> /* plum seems to work better                        */
>         background-color: plum;
> }

You're right.  I've changed the stylesheet.


> I like the enhancements to <keycap>. I think the colours work quite well 
> to give that "keyboard" look. The only issue for me is the fact that my 
> customisation layer specifies "font-family=verdana" for the <book> element 
> which seems to reduce the line spacing such that the bottom of the keycap 
> interferes with the top of the text in the next line. Setting "
> border-bottom-width: 3px;" and "font-size:smaller;" for keycap in my 
> customisation layer fixes this though. I guess this comment would be a FAQ 
> rather than a bug issue ;o) BTW. I've used "font-size:smaller;" for my 
> guibutton too.

I've added font-size:smaller, and, splitting the difference, reduced the
bottom border of keycap 4px.


> I noticed the website mentions that CSS can't do TOCs. Having a TOC has 
> been an issue for me and I've done some work on it recently. I can get a 
> pop-up TOC to appear in Mozilla quite nicely. Unfortunately, at this 
> stage, it interferes with the main text (ie. it pops up down the left hand 
> side of the page) and needs code in the XML doc which works for the 
> browser but makes the XML invalid. I have some ideas on fixing this and 
> I'll get back to the list when I start looking at the problem again...

I recall seeing an 'Outline' mozilla extension for HTML pages (I assume
that this wouldn't require changes to the document to make it work).

Maybe I'll have a poke at that, to see how it does its magic.


dave