|
There is no reason for the publisher to dump a catch-all CSS in the eBook. In looking at an ePub from Project Gutenberg for someone on MR, there was some class there that was causing a problem. The class wasn't needed. So having all of these extra classes could mean if there's something not quite right in one of the unused classes, it could cause a problem in the eBook.
I cannot stand eBooks made with Vellum, InDesign, or from Smashwords (having been typed into Word). The code in these eBooks can be rather nasty at times.
|