Quote:
Originally Posted by Turtle91
Other than what one person just doesn’t like as visually unappealing… most of these points are assuming that you have one, and only one, book file for ALL the different devices/apps out there….
It is just as simple to have a different css file for each market you wish to serve. Put the right css in the file you submit to kindle, put a different css file in one meant to serve kobo, yadda yadda. You can sometimes even include a JS that will link the correct css at runtime to serve those ePub3 devices/apps.
I completely agree that it is difficult to make one ring ePub to rule them all, but it is getting easier every day to compensate. Don’t give up trying!
FWIW - Personally, I just use ::first-letter and ::first-line. I get them to look good to me and provide for a basic fallback for those older devices that can’t understand current coding. It isn’t as pretty for those types, but those with newer devices can experience the better styling. I don’t punish those with newer devices by forcing them to the capabilities of the old devices.
|
Lets say you have a ePub for Kobo and you get you dropcaps to look perfect on your Kobo. What's to say it will look perfect on my Kobo with a different fint and different line height? That's the problem. You cannot make sure a dropcap works in all situations even if you have a different CSS as you've suggested.
So you deliver an ePub for Kobo and I buy from eBooks.com. How can you make sure that the ePub from eBooks.com looks good on my Kobo or someone else's Pocketbook? You can't. So why bother when it doesn't work?