Thread: CSS / dropcaps
View Single Post
Old 09-17-2012, 09:44 AM   #50
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: 8,657
Karma: 38766103
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by JSWolf View Post
But, the KF8 code in the eink Kindles ignores Line-height and has a larger then standard line-height.
No. The eInk Kindle reader does not ignore the line-height attribute... it just doesn't honor line-height values less than 1.2em or 120%. Nor does the Kindle Fire's reader, for that matter (section 3.1.7 of the Amazon Publishing Guidelines).

Yes, there is a fundamental discrepancy in the default, user-adjustable, line-spacing setting on eink Kindles compared to the Kindle Fire's reading app, but that doesn't have anything to do with the internal CSS line-height attribute specified in the ebook. It's an issue of scale. And it can be overcome by the user simply choosing a smaller line-spacing setting.

Last edited by DiapDealer; 09-17-2012 at 09:50 AM.
DiapDealer is offline   Reply With Quote