Quote:
Originally Posted by Hitch
Dion:
Now, before I say anything, a) you know that I love ya, right? and b) that I have mad respect for your eBook-fu, yes? Okay, having said that:
That's not necessarily true, Dion. I can break almost anybody's coding--even my own!--using nothing more lethal than a Paperwhite, Voyage or Oasis. Why? Because the Paperwhite family of devices will override font calls, to the Dropcap span. Utterly and totally. So, if you code (let's say) for an Adobe Garamond Drop, with AG body font, and Jane buys the book and reads it on, say, Bookerly or worse, Helvetica (please, Helvetica fans, don't leap in here, eh?), the drop cap is NOT going to work. Why? Because all the relative sizes will have now changed.
We've invested, at my place, a fair amount of time in developing One Drop To Rule Them All markup. And it wasn't quick or easy.
I'm not arguing with you, D. I love a good drop myself, just like I adore a good or elegant fleuron or graphic that I haven't seen before, (5,000x....) and all that. But, his Dropcap coding doesn't have to be broken, nor his device, for the dreaded:
T
his is the story of Jacob....
to occur.
Hitch
|
Another thing I find a real issue on a Kindle is when the publisher makes the first letter say 2em in size. That makes the first line height too large and there is nothing you can do to fix this. You can fix this on ePub but a lot of publishers don't bother.
I bet I could break your One Drop To Rule Them All markup with my normal settings. What size line height to do you need for your One Drop to work?