Quote:
Originally Posted by NiLuJe
@davidfor/@GeoffR: Speaking of, I actually appear to have vanilla kepubs *without* those specific divs (and style-hacks, except for the .koboSpan thingy) [at least according to the liberated Kobo Desktop version of the file. The one on my H2O looks the same, but with it being encrypted, who knows]. Yet the book-inner/book-columns stuff is still mentioned in the js :?.
One common trait to those books is that they *already* wrap the full body in a single div (although not book-inner and/or book-columns). And I could swear those don't suffer from the cutoff bug.
Since I basically just threw myself in the deep-end of Kobo arcane stuff here, I'd be glad for some more feedback on that point  . |
All I can think is to check that it really is a kepub, some books synced from the Kobo server are actually epubs, and get opened with the epub reader, although I've only ever seen that with free books. The margins in your screenshot make it look like this is being viewed in the epub reader, the kepub reader has larger margns, unless you are using the `Custom kepub default margins` patch?
Also the screenshot doesn't show any f characters at the right of the screen, f is the only character I usually see cut off. Can you check to see if an f gets cut off at the right?