Thread: CSS / dropcaps
View Single Post
Old 09-16-2012, 01:06 PM   #47
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 9,563
Karma: 44355222
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by Oldpilot View Post
You may have noticed, on the KDP forum this morning, that the KF8 update for the Kindle K3 keyboard reader seems to render drop-caps four lines deep, though the cap itself is scarcely three lines high, resulting in a rather silly effect whereby the cap sits to the left of lines 2 and 3 rather than at the top of the paragraph. Of course, this may have been only Punchy Gonzalez's CSS, but it confirms my decision to steer clear of drop-caps for the time being.
It almost certainly was Punchy's Gonzalez's CSS.

Mainly because there is no difference in the way "drop-cap" code is rendered across the various devices that support KF8. In fact, the various renderers have no idea what drop-caps are.

The issue is line-height. And the default line-height is much larger on eInk devices that support KF8 when compared to the line-height on Kindle Fire devices. But there's absolutely no reason why the exact same drop-cap code would render any differently on a updated K3 than it would on a Kindle Touch. And users know (or are learning) that they can easily adjust the line-height when they come upon a KF8 book.

Last edited by DiapDealer; 09-16-2012 at 05:32 PM. Reason: typo
DiapDealer is offline   Reply With Quote