[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [docbook-apps] To Rene Hache, Larry Garfield, Bob Stayton, Jirka Kosek - About a former XHTML accessiblity project
Regarding the empty divs, what about a post-processing step (like one pass profiling, but on the other end) that processes the output and turns this:
<div class="titlepage"><div><div><h1 class="title"><a id="d0e45"/>Preface</h1></div></div></div>
<div class="titlepage"><h1 class="title"><a id="d0e45"/>Preface</h1></div>
If you had a div with a class that had a child div with a class and the child div didn't have any following siblings, you could even combine the classes, to <div class="foo bar"> (assuming there were no conflicting attrs that couldn't be combined).
I guess the places where tables are used are easily found. Here are the ones I see just looking around:
variablelist (when list presentation is set to table...since this is an option already I guess the desire would be for a css-based tabular layout).
calloutlist (when callout.list.table is 1. The alternative now is <dl>, but those don't work well with callout graphics apparently)
The headers and footers in chunked output
The viewport in process.image