Thread: More Margin Questions
View Single Post
Old 09-01-2022, 01:30 PM   #32
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: 79,935
Karma: 146918083
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
Well formatted ebooks do not have a line-height property at all. The default is set by font metrics of selected font and if you set it in CSS, then it breaks almost all ereaders.

Only PDFs (and thus for POD or other publishing, or fixed layout for tablets) should have a line-height. Leave it undefined in Wordprocessor style and then conversion from docx to epub has no line-height in CSS. Amazon uses epub source to make mobi, azw3 and kfx.

The CSS line-height and many other valid CSS only make sense on web pages, not ebooks!
Do you also agree that there should be no margins set and let the program/device being used handle them?
JSWolf is offline   Reply With Quote