View Single Post
Old 01-18-2015, 10:13 AM   #9
icallaci
Guru
icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.
 
Posts: 819
Karma: 6528026
Join Date: Sep 2012
Device: Kobo Elipsa
I also like the summary nature of the reports in Sigil. The one I use most is Style Classes in HTML Files. If I'm fixing a series of books by the same publisher, often the CSS is a standard house stylesheet. But unused classes clutter it up. So I fix the first book and remove the unused classes, then copy that stylesheet to the next book, run Sigil's reports, and see which classes are in the HTML but not in the pared-down stylesheet. I can then go to the (separately saved) CSS file that contains ALL of the classes and copy the missing classes back into the stylesheet. I know this sounds convoluted (why don't I just leave all the unused classes in the stylesheet until I'm finished?) but a lot of my fixing involves looking for all instances of "text-indent: [^0]" or "margin-left: [^0]" and I don't want to look at each one individually when there are 187 of them. Plus, copying the entire stylesheet (minus unused classes) saves me from copying the altered classes one by one to the next book. I can do it with Calibre's editor too, but it's just easier when I can see them all in a list together.
icallaci is online now   Reply With Quote