Re: allowing CSS styling on most DocBook inline elements

[Norman Walsh <ndw@xxxxxxxxxx>]

| untagged character sequence, but I found that it was simple to change
| that to generate a SPAN element to wrap each such DocBook element,
| with a CLASS attribute identifying the gi of that latter element.

Sounds like a good idea to me ;-)

| In fact, and I admit that I'm a novice and don't understand the
| ramifications, it seems preferable to map *all* inline elements to
| SPAN elements and use CSS to apply the desired style, rather than to
| wire in generation of B, I, and TT elements.  Is it unfair to expect
| CSS to be available in most browsers?  Is it too awkward to have to
| pass a CSS stylesheet file along with the generated HTML file?

CSS support isn't quite ubiquitous yet.  And the implementations
aren't entirely compatible.  So I'm inclined to leave the obvious
ones hard coded, but there's no reason not to wrap all the others
in SPANs.

                                        Cheers,
                                          norm
-- 
Norman Walsh <ndw@xxxxxxxxxx>      | "Bother", said Pooh, as he deleted
http://nwalsh.com/                 | his root directory.


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist