SAGE: No line spacing change in epub?

[Uncle Robin]

I removed the Store-bought kepub version of a book and sideloaded an epub instead, the same one I've been reading on my Libra using KOReader. It's a largish file, the retail kepub was 24MB, the epub 22, so in KOReader, there is a visible delay while changes to font size, weight, margins and/or line spacing take effect. But they all DO take effect. I've discovered that on my Sage, the same file accepts changes to margins, font and font size, but not line spacing, as the attached screenshot shows. The same is true on my Libra using the Kobo stock reader - font, font size and margins all respond to changes, but line spacing does not. What would cause this?

[Sirtel]

Hard-coded line-height in the css? Have you looked at it in Sigil or the calibre editor?

There's a patch for overriding line-spacing in the css.

[Uncle Robin]

Originally Posted by Sirtel

Hard-coded line-height in the css? Have you looked at it in Sigil or the calibre editor?

There's a patch for overriding line-spacing in the css.

Thanks, I might try that. If it is hard-coded, I wonder why it responds to line spacing changes when opened in KOReader?

[NiLuJe]

You might have enabled the style tweak that bypasses line-spacing, or it might just be an odd CSS quirk (this is not my forte). The two (three if you count RMSDK) renderers work *very* differently, and they all have a different set of stock CSS and CSS bypasses, so, any "why does it work in X and not Y" question will always be answered by: "because X is not Y" ^^.

[Uncle Robin]

Originally Posted by NiLuJe

any "why does it work in X and not Y" question will always be answered by: "because X is not Y" ^^.

Fair enough, thanks

[JSWolf]

Take the ePub and go into the Calibre editor and remove all line-height lines from CSS. Then reload it and try again.Being abe to change the line spacing will work after this.

[Uncle Robin]

Originally Posted by JSWolf

Take the ePub and go into the Calibre editor and remove all line-height lines from CSS. Then reload it and try again.Being abe to change the line spacing will work after this.

I'm running KOReader on my Sage now, the epub is responding as it should to all adjustments.

[JSWolf]

Originally Posted by Uncle Robin

I'm running KOReader on my Sage now, the epub is responding as it should to all adjustments.

KOReader overrides where RMSDK and Access do not.

[Uncle Robin]

Originally Posted by JSWolf

KOReader overrides where RMSDK and Access do not.

You must have mistaken me for someone who cares I works for me, that's what I care about.

[Pajamaman]

Originally Posted by Uncle Robin

Thanks, I might try that. If it is hard-coded, I wonder why it responds to line spacing changes when opened in KOReader?

Koreader kills all known css formatting dead. Beautiful. Css is nice when it does what you want. For those cases when it doesn't, there is koreader/alreaderx. I much prefer to have full control via the menu system in the reader app.

[NiLuJe]

Originally Posted by Pajamaman

Koreader kills all known css formatting dead.

That's a bit heavy handed. And not necessarily true .

It *allows* you to (fairly) easily override what you want. (Or *all* of it at once, as we do have a "murder embedded style" button, after all ^^).
The defaults are still to honor embedded styling (to the best of CRe's ability), with a fairly small set of non-moronic base styling.

[Sirtel]

Originally Posted by Pajamaman

Koreader kills all known css formatting dead. Beautiful. Css is nice when it does what you want. For those cases when it doesn't, there is koreader/alreaderx. I much prefer to have full control via the menu system in the reader app.

CSS does what I want in all my ebooks. I don't allow any book on any of my readers which doesn't have nicely behaving css.

And that's why I don't like the apps that kill css.

[DNSB]

Originally Posted by Sirtel

And that's why I don't like the apps that kill css.

I don't mind the apps that can kill CSS so much as the ones where overriding that "murder' is either not possible, buried 4 menus down and/or still override 90% of the CSS even when you have enabled honouring the CSS styles.

[NiLuJe]

Originally Posted by DNSB

I don't mind the apps that can kill CSS so much as the ones where overriding that "murder' is either not possible, buried 4 menus down and/or still override 90% of the CSS even when you have enabled honouring the CSS styles.

*cough* Moon Reader *cough*

.

Snark aside, it might be the only app in the world with more insane and confusing menu & settings design than us ;p.

(Full disclosure: I haven't used it in years, and even then, not for long, because of the aforementioned rage-inducing behavior ).

[Semwize]

@Uncle Robin

You can use the patch: Force user line spacing in ePubs

This patch prevents any line-height style set in the book's stylesheet from being recognised.