Quote:
Originally Posted by arspr
Nope, if you apply apply margin to body inside the epub/kepub then trimming letters issue is gone. No need to apply it to an inner div or p. I've just re-tested.
|
Well I have tested it and it doesn't work. Adding padding or margin to body results in the problem that the OP describes.
Quote:
|
(But when using a 0 margin in GUI, although the device actually has a minimum available margin. I mean that RMSDK (epubs) does actually have a 0 margin so, of course, you get trimmed characters because they are partially outside the screen. But ACCESS (kepubs) always has a small margin even at the minimum value in GUI. But even with this available space, you get trimmed fonts when the slider is at it's minimum value).
|
This is exactly the opposite of what I have found. The font cut-off doesn't happen at all in the epub reader, even with a zero margin. The kepub reader has a zero CSS body margin at the smallest slider setting, but has an extra margin created by resizing the viewport or some other means.
Quote:
|
But if you use padding in-book instead of margin, then even with a 0 margin slider in GUI the problem is gone.
|
No, adding padding to body results in the same problem described in the OP. I have just tested it.
I've posted a new patch for firmware 3.12.0 that adds padding to the div and p elements immediately below body, this should work for sideloaded kepubs.