View Single Post
Old 07-17-2013, 01:08 AM   #9
GeoffR
Wizard
GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.
 
GeoffR's Avatar
 
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
This is my guess about what is going on with the font size and line spacing:

As tshering noted above, the Kobo readingLineHeight set by the slider is in units of em. But it does this based only on the font size at body level, and does not scale the value properly properly at lower levels.

For example if the CSS font-size at body level is the default 1.0em and readingLineHeight is at its minimum setting of 1.3, then the line-height at paragraph level is the inherited value 1.0em*1.3 = 1.3em instead of the unitless value 1.3, which I think is a Kobo bug.

Thus if font-size is set at paragraph level to a value different to the body level, then the inherited line-height is incorrect. For example if font-size is 1.0em at body level and 1.2em at paragraph level then the inherited line-height should be 1.3*1.2em = 1.56em, but because of the bug it is actually just 1.3em. This is the bug we can exploit to reduce the minimum line spacing without resorting to setting line-height expliitly in CSS (which would make it non-adjustable).
GeoffR is offline   Reply With Quote