[docbook-css] [ANN] Docbook CSS 0.3 Released
martin.gautier@myrnham.co.uk
martin.gautier at myrnham.co.uk
Mon, 18 Oct 2004 21:14:48 +0100
0.3 looks good.
The ulink stuff will be really helpful. Haven't got around to testing it
yet...
Getting <itemizedlist>s to work with proper numbering is a major tick off
the to-do list too. Excellent work.
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;
}
I pulled "plum" the table listed here:
http://www.webcolors.freeserve.co.uk/names140.htm
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 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...
Cheers
Mart