View Single Post
Old 05-03-2013, 05:56 PM   #49
dgatwood
Curmudgeon
dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.
 
dgatwood's Avatar
 
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
Quote:
Originally Posted by JSWolf View Post
We are going backwards here. We have Kindles with 1.2 and Kobos with 1.3. Both which are too large. The Kobo can be fixed via CSS and the only way Kindles can be fixed is to edit the metrics of the font so it has a smaller line height. I've done that for the Kindle (for KF8) using Charis SIL and it worked very well.

It's disgraceful when a Reader and/or app has defaults that cannot easily be overridden and those defaults are obnoxious.
Indeed. Lots of things the Kindle KF8 readers do are obnoxious. That particular one, though, is so badly done that fonts whose metrics specify a smaller-than-1.2 line height actually get forced up to a 1.2 line height, resulting in the layout of the content changing. To get a line height less than 1.2, AFAIK, the only thing you can really do is lie in your metrics and extend the ascenders and descenders past the specified limits.

So yes, no disagreement here. What Amazon has done with KF8 is broken. Badly. Embarrassingly.
dgatwood is offline   Reply With Quote