View Single Post
Old 02-05-2024, 03:31 PM   #81
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,060
Karma: 147977995
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by Quoth View Post
On physical epub readers with user line-height, like a Kobo, it's fixed if it's set in the ebook. If there is no setting, then the user can change it easily from no spacing to more than double spaced. The font metrics set larger relative spacing for larger fonts.
Also you see the absolute space is different on different fonts of the same size.
There is less control on a Kindle, but none if the line-height is set.
I forget what the iRiver, Sony, Nook etc do.
Different Andriod apps behave differently.
KOReader can override CSS like line-height. Many apps won't.

I don't like naked tags. I think it's less error prone that at least <p> and <hx> have classes in the CSS.
This is a good point:

You want to be able to change the tag (semantics if you like) without unexpectedly changing the visual rendering.
Any Reader that has RMSDK will allow a line height such that the first line will not be off. Sony & nook use RMSDK. I would expect any Reader where the software used that allows a line height to be used should work.
JSWolf is offline   Reply With Quote