Why do different books render differently in the viewer?

[deback]

Originally Posted by deback
The way to fix the line-height is to open the book in the Editor, double-click on the stylesheet.css file (at the left below the *.html files), and then change the lines that start with line-height to 1.2 (1.2em will work, too, but you only need 1.2).

This is just wrong. To fix the line-height is to remove it. There should be no line-height unless it;s an ePub anf you need a line-height of 0 for those pesky large first letters of a chapter/section break. Kindles don't respect line heights less then 1.2em and on Kobo Readers, you can set the line height so you don't want any so you can set what the reader wants for a line height.

It's not wrong; it's just one possible quick solution. Maybe I didn't word my comment (in the quote above) good enough.

Actually, what I do is have rules in the Transform section to change any line-heights greater than 1.2 or less than 1.2 to 1.2. Most ePub files have several line-height lines in the *.css file, and many have the line-heights set to more than 1.2, which is very annoying when reading. I could remove them all, sure, but I just change them all to 1.2. Having those lines in the *.css file will work, whether they should be there or not, but only the body class really needs to have the "line height: 1.2" line.

[GarryB123]

Originally Posted by theducks

Both editors have their power. I use both (I started with Sigil). I LOVE they have differences. I use them both because of what they do DIFFERENTLY.

Yes! I'm learning their strengths. So far calibre is meeting my needs. What a cool program.

[JSWolf]

Originally Posted by deback

It's not wrong; it's just one possible quick solution. Maybe I didn't word my comment (in the quote above) good enough.

Actually, what I do is have rules in the Transform section to change any line-heights greater than 1.2 or less than 1.2 to 1.2. Most ePub files have several line-height lines in the *.css file, and many have the line-heights set to more than 1.2, which is very annoying when reading. I could remove them all, sure, but I just change them all to 1.2. Having those lines in the *.css file will work, whether they should be there or not, but only the body class really needs to have the "line height: 1.2" line.

But doing this will create problems for some people. Take a Kobo user. There is an option to set the line height. If you've set it, it cannot be made smaller if that's what's wanted. When I read ePub, I read with a line height smaller then 1.2em. So because you think it's correct to have a 1.2em line height, everyone who does not strip DRM or edit eBooks has to put up with it.m.

The way to make eBooks is to do so using less is more. Don't set L/R margins. Don't set line hight. Don't use left justification. Use the default font size where possible. Don't use classes for your most used p settings. Don't embed fonts just because. Keep it simple. In those cases where the user can adust some settings, let all of that work. Don't put in what you think is best if it's going to cause a problem for others.

[ps67]

Originally Posted by JSWolf

The way to make eBooks is to do so using less is more. Don't set L/R margins. Don't set line hight. Don't use left justification. Use the default font size where possible. Don't use classes for your most used p settings. Don't embed fonts just because. Keep it simple. In those cases where the user can adust some settings, let all of that work. Don't put in what you think is best if it's going to cause a problem for others.

I agree with You, most times css are uselessly complicated. When I buy a book I like when that principles are used (almost never).

But if someone is modifying a book for his personal use also quick and dirty solutions can be used.