View Single Post
Old 04-20-2014, 07:17 AM   #11
mandy314
Connoisseur
mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.
 
Posts: 71
Karma: 200092
Join Date: Mar 2014
Device: kindle pw1
thank you all for your replies

in the end I'm with Hitch: it seems to be a lost cause for KF8 really (and not only for embedded fonts)
IIRC Amazon KF8 guidelines say the 1.2em/120% minimum line-height is set to get good pagination. I can see sense in this one - but perhaps it would have been more elegant to set the minimum for block but not for inline elements.
AFAIK CSS-standard would be inline elements inheriting line-height in absolute computed terms when for the parent the line-height is set in % or em. This doesn't work with KF8 for Kindle own fonts or for embedded fonts. So - one can say - KF8 isn't css-compliant.
As I'm new to ebook-formatting I hoped for some css that work with KF8 when I asked the question. The float- and the svg-things are clever but I don't think it is worth the effort to "out-fox" a restriction apllied by Amazon with intention.

Thank you again!
mandy314 is offline   Reply With Quote