|
InDesign embeds fonts when you don't actually need them. Looking at mazdaspeed's code, it's awful. It can be made a lot neater when edited by hand.
Most of those spans and the CSS code can go away. Just use the appropriate <i> and <b>. Also, the font references can go as those are not fonts that work well on eInk screens. When you want to use a sans-serif font, use font-family: sans-serif; and let the reading program use it's default sans-serif font.
With not much time, I can take most of those spans and get rid of them and keep all the bold/italics in the HTML. I've edited a lot of eBooks made with InDesign and when I am done, they are so much better. The code is better, the formatting is better, the embedded fonts are gone (in most cases and even if not, only one or two fonts are left). Don't assume the fonts you use for print work for eBooks. These are two different formats and what works for one may not work for the other.
For example, pBooks do need some L/R margins because of the spine of the book. But an eBook does not need L/R margins. An eBook does not need a line height. An eBook does not need 1/3rd or 1/4th of the screen taken up with the chapter header. An eBook does not need *** for a section break to say you are at or near the end of the printed page. An eBook does not need a disclaimer that it's illegal to sell without the cover. An eBook needs larger (subset is too small) characters for footnote markers.
So learn to code so you can fix the mess left behind by InDesign. It's not difficult to do.
But with spans, please don't do use them for bold and/or italics. Just no.
|