View Single Post
Old 08-05-2017, 11:11 PM   #18
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
Quote:
Originally Posted by DiapDealer View Post
line-height: 0; seems to work just fine for me for subscript/superscript/raised caps. I don't care how KF8 works.
Doug:

If you are dealing with an environment in which you have one font for the drop, and another for the body--which, in turn, can be changed--there's really no good way to address this in eBooks. Every different font has different line heights, x-heights, ascenders, descenders and so forth. Thus, whilst in print you can adapt the two, to get a perfect drop, in eBooks, you're screwed.

I would add that whilst you can go bonkers and write a BOATLOAD of media queries for KF8 and KF7, to work around this SOMEWHAT competently, it taks hours to do for each book, if you're using different drop and body fonts, or a different font for the drop, yadda, yadda, yadda.

Offered solely FWIW.

Hitch
Hitch is offline   Reply With Quote