Quote:
Originally Posted by JSWolf
When I am editing the eBook, I remove all that same rubbish. I also delete any internal. I dump any unused graphics. As long as I'm in the CSS dumping line-height, margins, excessive space for chapter headers, normalizing font sizes, fixing any graphics that need fixing, and other things that make reading better for me, I find that by the time I'm done with what I want, there's not much left (if anything) that could be cleaned up. Sometimes when dumping unused CSS, hundreds of CSS classes get dropped. The last time it as 299 CSS classes that got dropped.
|
I've seen some CSS files contain over 2,000 classes. It's unreal how dumb some of the publishers are when it comes to creating digital files.
Even though I always open each file in the editor to run Check Book, having the delete-unused-CSS function run during the conversion saves time, even though it doesn't take long to delete them manually. When working with dozens of files at a time, it saves time, and I will always automate anything that saves time.