View Single Post
Old 03-16-2015, 04:30 PM   #109
arspr
Dead account. Bye
arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.
 
Posts: 587
Karma: 668244
Join Date: Mar 2011
Device: none
Quote:
Originally Posted by GeoffR View Post
I think the solution for this problem is the same as the solution to the side bearing cut-off problem: Make sure you are using the latest KoboTouchExtended driver to create your KePubs, and add
Code:
div#book-columns {padding: 0.2em !important;}
to the book's stylesheet (or to kobo_extra.css if using that driver option)

For Kobo-synced KePubs the `Fix KePub side bearing font cut-off bug` patch is needed to add that to the device's built-in stylesheet. (see the "Instructions for patching firmware ..." threads in the developer's forum.)
Thank you GeoffR.

Although I wouldn't call that a solution but a workaround...

Another "easier" solution (for people who just don't know/care about coding and/or HTML) is just:
  • Don't use fullscreen. (Well, you won't be probably using it...). It's still a "hidden" and not officially supported feature, so it's not expected to work flawlessly.
  • Use the smallest margin setting in GUI bigger than 0, even if you actually wanted to use 0. 0 is buggy...

Of course, 0.2em is probably smaller than the GUI smallest possible value, but you will be masking the error / possible solution forever.

Your choice, guys.
arspr is offline   Reply With Quote