Quote:
Originally Posted by Hitch
Sez you. We've done many books in which we have hierarchal headers.
What? That's a ridiculous "solution." How about using CSS, as it was intended? Using Div instead of p? So, what, use the wrong coding, because somebody doesn't know the right coding? Hell, why not just use /b between paragraphs--hey, that works TOO! 
Oh, yeah, that's a great solution. /sarcasm.
Hitch |
What I want to know is why so many publishers have no idea how to properly use <p> and have to stick in a class for the most use paragraph style instead of just coding for <p> in CSS?
As for <div> where <p> should be, I find that very sloppy and that does get fixed. There's a lot of things that could be done, but a lot of it is sloppy have violates the keep it simple rule.
When I fix up a sloppy ePub, it's a lot neater. It may not be perfect as there could be excess lines in the CSS and I don't change <p> in chapter headers for h?, but when I am done, the code can be much neater.
The other thing I find atrocious is when there are hundreds of extra classes that never get used in the CSS/HTML.