View Single Post
Old 08-09-2013, 01:59 AM   #5
MacEachaidh
Browser
MacEachaidh ought to be getting tired of karma fortunes by now.MacEachaidh ought to be getting tired of karma fortunes by now.MacEachaidh ought to be getting tired of karma fortunes by now.MacEachaidh ought to be getting tired of karma fortunes by now.MacEachaidh ought to be getting tired of karma fortunes by now.MacEachaidh ought to be getting tired of karma fortunes by now.MacEachaidh ought to be getting tired of karma fortunes by now.MacEachaidh ought to be getting tired of karma fortunes by now.MacEachaidh ought to be getting tired of karma fortunes by now.MacEachaidh ought to be getting tired of karma fortunes by now.MacEachaidh ought to be getting tired of karma fortunes by now.
 
MacEachaidh's Avatar
 
Posts: 745
Karma: 578294
Join Date: Apr 2010
Location: Australia
Device: Kobo Touch, Kobo Aura HD
Thanks for the replies, folks.

Jackie_w, yeah, the Palatino is embedded. I currently like to embed a chosen font for headings, and let the device choose the font for body text. I decided to use the headings font for the drop cap as well. That bit all works fine. Otherwise, I think our codes are essentially the same? Difference of bottom margin (which I added so the text wraps at the bottom of the drop as well) and the "hidden" code. I still don't understand why the code works on ADE and Sigil but not Kobo.

David, thanks for your stuff. I considered embedding graphics for the dropped caps, but it does swell the filesize of the book considerably, and of course it's not subject to changes in font size at the device level. May be the only way to do it reliably, I guess.

Geoff, thanks for the suggestion, mate. I'll check out a Feedbook or two, though if I remember correctly, the last time I looked at one of those the CSS made my head swim.
MacEachaidh is offline   Reply With Quote