View Single Post
Old 09-14-2026, 08:43 PM   #79
MrSilverstrike
Connoisseur
MrSilverstrike ought to be getting tired of karma fortunes by now.MrSilverstrike ought to be getting tired of karma fortunes by now.MrSilverstrike ought to be getting tired of karma fortunes by now.MrSilverstrike ought to be getting tired of karma fortunes by now.MrSilverstrike ought to be getting tired of karma fortunes by now.MrSilverstrike ought to be getting tired of karma fortunes by now.MrSilverstrike ought to be getting tired of karma fortunes by now.MrSilverstrike ought to be getting tired of karma fortunes by now.MrSilverstrike ought to be getting tired of karma fortunes by now.MrSilverstrike ought to be getting tired of karma fortunes by now.MrSilverstrike ought to be getting tired of karma fortunes by now.
 
MrSilverstrike's Avatar
 
Posts: 91
Karma: 969306
Join Date: Apr 2024
Location: Belgium
Device: Kobo Libra Color, Kobo Clara Color
Quote:
Originally Posted by jackie_w View Post
If you're a Kobopatch user, one of the oldest patches for libnickel.so.1.0.0, Un-Force user text-align in div,p tags in KePubs, lets you change the override to:
Code:
body { text-align: %1 !important; }
i.e. a less severe override. This matches what default Nickel does for standard epubs in the Adobe renderer.
Right, I should probably apply that as part of the mod for 4.x too. From a CSS perspective that's indeed a less invasive style to apply, and likely results in more "correct" rendering.

Although one has to wonder if that'll make a big difference in purchased books, which likely are already "optimized" for the kepub renderer (unsure, I haven't looked at any markup since these are encrypted). Sideloaded kepubs are a different story, of course.

(This rule for fw 5.x is different and simply forces text-alignment for everything, including headers etc. I'm unsure about the actual CSS rule off the top of my head, but it works differently.)
MrSilverstrike is offline   Reply With Quote