Thread: CSS solution for words cut-off in kepub full screen reading
View Single Post
Old 12-17-2014, 05:40 PM   #32
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
Note that kepub-book.css stopped working after firmware 3.2.0. This is why it is necessary to patch the built-in stylesheet in libnickel.


(I think there are enough smacks)



(Some more were needed).

I was wrong with one of my first posts. Font-trimming issue is fully dependant on Fullscreen mode. As I thought it wasn't (maybe in the past it wasn't) I've been turning it on/off all the time and therefore I was making mistake after mistake.

I *think* I get it right now:
  • Show header and footer ON (default supported feature):
    • GUI margin at 0 AND body padding in ebook at 0: Trimmed fonts even when the screen has some room. ACCESS doesn't really have a true 0 margin...
    • GUI margin in any other position OR body padding in ebook at any other value: OK, no issues.
  • Show header and footer OFF (aka fullscreen mode, undocumented and unofficial feature):
    • body margin AND padding in ebook at 0: No word trimming bug but you have font trimming bug no matter what you do with the GUI margins.
    • body margin OR padding in ebook at any other value: Word trimming bug. Because of the word trimming bug I cannot evaluate the font trimming bug in the right margin, but looking at what happens in the left:
      • body margin is set at any value, padding in 0:
        • GUI margin in 0: Font trimming bug.
        • GUI margin at any other value: No font trimming bug.
      • body padding is set at whatever value: Font trimming is fixed even with GUI margin = 0.

(Of course when I say "whatever value", it really means "whatever value which gives enough room to the negative side bearing, aka the 'protrusion'")

So as a brief summary (not exhaustive):
  • body padding different than 0 always fixes the font trimming issue.
  • GUI margin different than 0 fixes the font trimming BUT in fullscreen mode.
  • Right now either body margin or padding different than 0 cause the word trimming issue in fullscreen mode.
  • I cannot edit/see the internal code of my "official" DRM kepubs, but the behaviour seems to be exactly the same as in sideloaded ones.
  • Yes, kepub-book.css doesn't seem to work.

GeoffR, could you confirm if you can replicate these, I hope, final scenarios...?
Last edited by arspr; 12-17-2014 at 05:51 PM.
arspr is offline   Reply With Quote