Quote:
Originally Posted by Turtle91
Your device is either broken... or the dropcap in the book isn't coded properly...
I'm not arguing that there aren't people who dislike that styling - don't care - and that you prefer something different wasn't the point... the point was that you can style the entire paragraph to overcome some of the issues people were having with dropcaps.
I wasn't trying to tell them what app/device to use - I just don't like limiting my creativity because someone out there uses an outdated device with broken functionality... If they get to the point where they are tired of their books looking like crap then they can get a standards compliant device (or put enough pressure on their device/app manufacturers to put out an update).
|
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