You method is more than just a difference in technique. As you said a couple of posts up, with what you're doing, you get more semantically defined CSS. The HTML of the book is staying pretty generic, but the semantic aspect of the CSS lets the HTML behave differently based on what it is.
What I've been doing has been using a simple set of CSS that I change in the HTML depending on what I want the page to look like. Many of the published books I've been reformatting have HTML/CSS that looks like it was pushed out by and for a program simply because it's in their system and no human will ever see the underlying code. With the above, it looks like the HTML and CSS stays readable and understandable, but can be adapted to behave differently without too much trouble.
I'll have to play with this.
|