View Single Post
Old 11-19-2015, 05:27 AM   #12
RbnJrg
Wizard
RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.
 
Posts: 1,852
Karma: 8821117
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
Quote:
Originally Posted by dgatwood View Post
This is why you should always provide a custom font for drop cap glyphs. You need to be in control over the descenders to ensure that they don't descend into the next line of text, and the only way to do that is to actually control the font.
Hi dgatwood;

About two years ago I spent a lot of time to find a method that worked with any model of Kindle. Even with a custom font, you can't get the perfect bottom alignment for all models (you can see the raised cap perfectly in e-ink devices but not in Fire models and viceversa ); the only way I found is to use an image. And in this case, the best kind of image is a svg. Of course, if we were working on epub, all this is not necessary since in epub we can control line-height (and as you well know, in Kindle we can't set a line-height lower than 1.2em).

Regards
RbnJrg is offline   Reply With Quote