Re: [docbook-apps] Re: Bug #849312 shade.verbatim not working in programlistingco

["Bob Stayton" <bobs at sagehill dot net>]

Norm,
You don't have to say anything, because it *was* a good idea at the time.
We all did what we had to do with HTML, given the limited tools of just a
short while ago.  The point I was trying to make is that the design
principles for HTML have changed, and perhaps this would be a good time to
reexamine how DocBook XSL generates its HTML.

I would like to see some version of the stylesheets generate clean XHTML and
a CSS stylesheet.  The styles in the stylesheet could be mostly
placeholders, but they would make a good starting point for anyone who wants
to customize the format of their XHTML.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net



----- Original Message ----- 
From: "Norman Walsh" <ndw@nwalsh.com>
To: <docbook-apps@lists.oasis-open.org>
Sent: Thursday, October 28, 2004 5:27 PM
Subject: [docbook-apps] Re: Bug #849312 shade.verbatim not working in
programlistingco

/ "Bob Stayton" <bobs@sagehill.net> was heard to say:
| Yes, let's move the DocBook HTML into the modern age and not
| use tables for such formatting hack.  8^)

What can I say? It seemed like a good idea at the time...

| There are some other uses of HTML tables that could use a looking at,

The others have to be explicitly enabled. I suppose we could remove
them too, but getting some aspects of list formatting right with CSS
might be a real challenge.

| as well as the vestiges of formatting elements like <b>.

I think I ripped most of those out the other day when I applied a
patch.