Quote:
Originally Posted by cybmole
well - testing needed - but where I have left this calibre code in a book at the end of each chapter , by your logic I should be seeing a new screen generated by the code followed by another new screen generated by start of next chapter. i.e. a double page turn at the end of every chapter. ditto if such code is left in at start of each html.
I don't see that, so unless renderers are smart enough to suppress that redundancy....
|
Some are, some aren't. I was checking a book a few months back that generated extra pages in one of my readers but not the other. Same file, but one detected the extra skip and suppressed it while the other faithfully rendered the blank pages. (I'm thinking iBooks rendered and ADE suppressed, but I may have that backwards. Like I said, it's been a while.)
There's one feature I'd like to see, but there's too much involved for me to add it myself. iBooks requires that a certain XML file be present before it will honor certain font changes, and while I can manually add it easily enough, it'd be nice to autodetect the presence of embedded fonts and add it on the fly. Similarly, the ability to automagically run the "remove unused CSS rules and classes" during a cleanup would be useful.
But then, while I'm wishing, I might as well wish for a magical module that analyzes the CSS, rescales the font sizes so that the main text is "medium", and performs other such optimizations. I guess I'll have to keep doing it myself, though; it's delicate work that requires skull sweat to handle correctly. At least I've got the indie author I'm doing formatting/editing work for set up with a proper template that spits out decent code when saved as HTML. It still needs some manual tweaking, but not a lot.